Welcome “Windows Live for Developers”

Angus Logan has his first post up on a new Windows Team blog, “Windows Live for Developers”.  Angus is the Senior Technical Product Manager for Messenger Connect (and before that, the same title for Windows Live Platform), which itself is an upcoming single API promising “a new way for partners and developers to connect with Messenger”.

Ori Amiga posted on the Inside Windows Live blog back in April about Messenger Connect, as John Richards and Angus were announcing Messenger Connect at The Next Web Conference in Amsterdam.  Ori explained the basics:

Messenger Connect brings the individual APIs we’ve had for a long time (Windows Live ID, Contacts API, Messenger Web Toolkit, etc.) together in a single API that’s based on industry standards and specifications (OAuth WRAP, ActivityStrea.ms, PortableContacts, OData) and adds a number of new scenarios.

The new Messenger Connect provides our developer partners with three big things:

  • Instantly create a user profile and social graph: Messenger user profile and social graph information allows our shared customers to easily sign in and access their friends list and profile information. This allows our partners to more rapidly personalize their experiences, provides a ready-made social graph for customers to interact with, and provides a channel to easily invite additional friends to join in.
  • Drive engagement directly through chat indirectly through social distribution: By enabling both real-time instant messaging conversations (chat) and feed-based sharing options for customers on their site, developers can drive additional engagement and usage of their experiences by connecting to the over 320 million Messenger customers worldwide.
  • Designing for easy integration in your technical environment: We are delivering an API service that will expose a RESTful interface, and we’ll wrap those in a range of libraries (including JavaScript, .NET, and others). Websites and apps will be able to choose the right integration type for their specific scenario. Some websites prefer to keep everything at the presentation tier, and use JavaScript libraries when the user is present. Others may prefer to do server-side integration, so they can call the RESTful endpoints from back-end processes. We’re aiming to provide the same set of capabilities across the API service and the libraries that we offer.

Looks like we’re about to hear a lot more about Messenger Connect soon.  We added Windows Live for Developers to our “Blogs We Like” section, and you can subscribe via rss.