Blake Schwendiman's Blog and Blook

This is day 3 in my series: New ways of driving traffic to your site or blog. [Read Day 1]

The reason I placed Windows Live at the bottom of my homepage overviews is that it's the one site I know the least about. I haven't build a gadget for Windows Live yet, but they do have an API like everyone else. The site is still in beta (like the others), but it seems to be a little more beta than the others. Ironically when I went to take a screen shot of Windows Live this morning, the only browser that it worked in was Firefox. I suppose that means it's time for a Firefox plug:

The reason that you should consider Windows Live with the others is simply because this is a Microsoft site. Eventually it will generate an enormous amount of traffic (if it isn't already). From what I can tell Windows Live is looking like it could be the next standard portal or start page for Microsoft. Getting your gadget there early couldn't be a bad thing.

As I mentioned with Pageflakes, a good strategy for developing any new module would be to take a close look at each of the APIs before you start coding. That way you'll have a better chance of developing a module, flake and gadget from essentially the same code without a lot of redundancy. I'm doing that now with an update to my Netflix module ... I'll let you know how it goes.