
OpenSocial Launched by Google
By Graham Massey
November 10, 2007
Google has launched OpenSocial, an Application Programming Interface (API) to help and make it easy for software developers to write applications to run on websites that support the application development format. It is essentially a set of programming tools based on JavaScript and HTML and is being developed by Google in collaboration with other online web application developers.
It is anticipated that Engage.com, Friendster, hi5, Hyves, imeem, LinkedIn, MySpace, Ning, Oracle, orkut, Plaxo, Salesforce.com, Six Apart, Tianji, Viadeo, and XING will implement OpenSocial.
Orkut.com is hosting a "limited sandbox" that can be used by developers to start building applications using the OpenSocial APIs.
OpenSocial is an extension of Google Gadget technology. Using the Google Gadget Editor and basic key/value API, it is possible to develop a complete social application.
As pointed out by
Joe Kraus, Director of Product Management at Google, the real value of OpenSocial is that it makes it possible for common tools to be used by multiple social networking sites. He says, "A tremendous amount of activity is occurring on social networks these days. Hundreds of millions of people share photos, rate movies, and throw virtual sheep at one another. All these social networks are looking to give their communities more and more things to do -- and they realize they can't do it on their own. They need to open up and become platforms for developers to extend. So, many social networks have looked at, or launched, their own APIs that typically do the same kinds of things: give access to user profiles and friend networks, and allow an application to post activities so that everyone's circle of friends knows what the others are doing. All of this has been good news, because developers could get their applications onto a social network.
But there's a problem: it wasn't one or two social networks doing this, but ten or fifteen. Now, to get on all the social networks a developer has had to customize their application for each one. When your 'development team' is just one or two people, the proliferation of APIs forces you to make tough choices, because you can't do that much one-off work. Not only is this situation bad for developers, it's bad for consumers too: When developers can't afford to do the work to make their applications work on a certain social network, the people using those networks lose out."
OpenSocial steps in here and allows a software developer to write an application that will run on any social website where it is supported. Multiple rewrites to adapt the application to different "environments" is no longer necessary.
One cannot but admire the innovation of Google and the almost uncanny frequency with which they are able to not only identify needs but also come up with a workable and widely accepted solution.

In-House