So as I sit in the airport, hoping that one of the beyond-overbooked flights has an opening so I can get home early and not have to go through Vegas, I thought I'd share my thoughts about the Windows Live platform that we picked up during partner training here in Redmond.
Without a doubt, the coolest feature enabled by the platform is single sign-on. And, while we're at it, the way it's implemented is really cool.
When a user goes to a site that uses the single-sign-on feature (that is, Windows Live ID integration), the user is presented with a user login screen that is typically fairly consistent across sites. I've seen two user experience-style screens that present it: www.zune.net has a themed version of the older, Passport-style login screen, while others (particularly those that host Live Controls) display a more Windows Vista-style login screen.
When a user needs to login, they are redirected to login.live.com to provide the authentication credentials via HTTPS. Once authentication is complete, they are redirected to the original website with a login token which provides information about that user. The cool thing is that the login token is the same for that user on that site across sessions, but not the same across sites, so you're able to identify the same user during multiple visits. This makes integration with the profiling API fairly straightforward.
Unfortunately, I can see issues with it; signing up or signing in can make it unclear to the users that they're still logging into the site, and people who are not Live ID users might be hesitant to sign up for a service that might not be directly related to the site they're working on. The sites aren't particularly customizable right now, either, so they might not really get the user to trust that they're still working with your site.
Contacts and Contacts Control
The Control may or may not be appropriate for a given site, but fortunately, you can also simply query the data via a REST interface. Very slick, and definitely usable. A good example in which this was appropriate was Buxfer - a site that helps you track your money. You might notice along the top of the page:
Clicking on the Windows icon pops up a dialog asking you to enter your Windows Live ID credentials. Very slick! I believe that, using this information, you're able to invite other friends (maybe the site was an example of single sign-on - it's starting to blur together).
Also cool (but in this case, probably more for the "cool to nerd developers" factor) is the ability to include a fully functional Windows Live Messenger client in your website. Want to sign in? No problem! Just pop open a new window with your account information and new windows for your conversations, just like the Windows client.
I don't really see the value in this for most websites, but there are a couple great exceptions:
- A site that wants to support Live Chat support can use this service to allow even anonymous guests to present the user with a chat window to the support person who is signed into Messenger. There are scalability concerns for this, but all told, it's a pretty neat way to do it.
- Message board or other community software might allow users to allow access to the user's Live Messenger account so that users can contact them through the web. The actual Live ID is shielded and not presented; an obfuscated, site-specific ID is used in its place.
I was a bit unsure about using Live Spaces, but the way it's discussed for example sites makes it sound like a bit of an easy storage solution similar to SharePoint. It might be worthwhile, especially for our clients who want to focus on virality.
We got some cool info that we can't talk about (nor can the Microsoft guys in charge), but it's really exciting nonetheless.
I'm not sure that Terralever can use the platform effectively, but it depends on seeing what kinds of technologies our clients can leverage, and how much Microsoft is willing to work with us.
Another one of the attendees voiced this concern, and it was something I'd thought about before we even got here - a lot of this technology is too late-to-market (my thoughts were "too little, too late"). People are sharing their thoughts on Digg, their photos and profiles on Facebook, photos on Flickr, documents on Google, and a lot of other stuff is already done. Single sign-on is GREAT - but I'm not sure that it's enough to make people buy-in to Live. Still, maybe it's a moot point; with 400MM monthly Live ID users and 100MM monthly Live Spaces users, perhaps greater propagation doesn't matter.
For more information about the Windows Live development platform, check out their website!
Tomorrow after I present at the Arizona .NET Users Group, I'm getting on a plane to head to Redmond, WA for some first-party training on the Windows Live platform. I'm not particularly certain what to expect; I think by and large, most of us are a bit ignorant about what the platform has to offer, and while some of the components are incredibly cool (the Virtual Earth API, for example), others seem... not so cool (such as the web-based gadget hosting platform).
One thing is certain - with the Windows Live platform, Microsoft is making a huge effort at hitting web-connected technologies. Sometimes I wonder if it isn't too little, too late (Blogger, Facebook, Google Maps, and Flickr come to mind as functional precursors for the corresponding Windows Live services), but at the same time, the ability to have everything integrated into one service could be advantageous. To that end, we'll need to see how things play out.
Stay tuned for new information about the Windows Live platform, direct from Redmond.