OpenSocial and the Facebook Platform: Interview with Peter Chane, Group Product Manager at Google
November 2nd, 2007
| By Justin Smith | 11 Comments » |
The landscape for social network application developers has changed drastically with the anouncement of OpenSocial this week.
Google’s Orkut and a cadre of partners including behemoth MySpace, LinkedIn, Hi5, Bebo, Friendster, Six Apart, Ning, and Plaxo, have announced common support for what has already become in the eyes in developers the second major “platform.”
I spoke with Peter Chane, the Group Product Manager at Google who is helping to lead the OpenSocial effort, about OpenSocial and how it compares to the Facebook Platform.
IF: At a high level, how do the real estate and functionality that OpenSocial affords developers compare to the Facebook Platform?
PC: With OpenSocial, there are many “container” sites that can host developers’ social applications. Together, these sites have over 200 million users.
There will be a lot of commonality between container sites in terms of the profile page and canvas page real estate developers have to work with. However, some sites will offer additional features that they’d like developers to plug into; many are extending the API.
One example is the Flixster app on MySpace. When the Flixster app is added, it reads in a user’s favorite movies into the app. MySpace added the “movies” field to the API…there’s not a fixed list of profile fields that will be available to developers on every container.
IF: Facebook offers features that help applications spread “virally” to their friends. Will OpenSocial support features like Facebook’s invitations, notifications, and feed items?
PC: There isn’t a feature like invitations in the OpenSocial API at this point. It’s something we’re considering — a lot of sites and developers have expressed interest in this, and we’ll be having conversations with them.
OpenSocial container sites will have activity streams that show activity from the user and their friends. Just like on Facebook, applications can publish stories to it. This is one channel that will really help applications spread.
IF: Facebook has fairly strict limitations on what profile data applications can retain. What about OpenSocial?
PC: We haven’t included any rules about this in the API yet. OpenSocial is still very much a work in progress, and we’ll have more to say soon.
This will be addressed between now and when the first site goes live that allows apps to be used by consumers. But our general philosophy on this is to allow these sites to make decisions for themselves.
IF: Unlike Facebook, OpenSocial doesn’t require apps to be marked up in a proprietary language. Will developers be able to reuse substantial amount of code from their Facebook apps in their OpenSocial apps?
PC: I’ve heard both models from developers. Some say, “I have already built some infrastructure, and it’s great that OpenSocial can take advantage of it.” Other developers say that they want to write client side JavaScript. The API allows for both types of apps to exist–those in IFrames, and those in AJAX.
IF: OpenSocial is being touted as write-once, run-anywhere. Do you think that the same applications will work on different container sites, given the different types of users and behaviors on each one?
PC: I think some might and some might not. Some applications, like iLike, will run untouched in a number of containers. In other cases, developers will need to change their applications according to the features of the new container and the usage patterns that happen in that container.
Some applications are more focused on communication, others more on personal expression. Some are domestically focused, some are international. Even if a given application needs to be changed, there should be an enormous amount of code reuse possible.
IF: When the Facebook Platform launched, several “launch partners” were briefed ahead of time, and arguably gained a leg up on other developers. Will the same thing happen with OpenSocial sites?
PC: None of the container partners have launched consumer apps yet. All developers have access to the same information.
As for Orkut, signups to gain access to the Orkut Sandbox are now open. We will be very quick in approving developer access–we want to add people to the sandbox at a fast rate. I don’t know of other containers that are accepting developer applications as early and quickly as Orkut is right now.
Developers: check out the OpenSocial API at http://code.google.com/apis/opensocial/.
[tags]facebook,opensocial,platform,api[/tags]

Twitter
Facebook









Strategic Facebook Platform Ecosystem Overview and Guide For Agencies & Brands
French / Français
Spanish / Español
Italian / Italiano
Track Facebook's International Growth in 95 Global Markets with our Monthly Reports and Analysis


November 2nd, 2007 at 11:12 pm
[...] Original post by Inside Facebook – Tracking the latest Facebook news and apps [...]
November 3rd, 2007 at 2:35 am
Great interview.
Personally I’m curious about two things: security and servers.
::Security::
Techcrunch already put up an article about an openSocial app getting hacked. Facebook has gone through their own security issues but delt with them fairly well. Does the new API have security rules enforced or will that be up to the social container?
::Servers::
I’m wondering if all these social sites are ready for the insane amount of server hits they will soon get. What have they done to prepare?
Did Mr. Chane by any chance discuss stuff like this?
November 3rd, 2007 at 3:48 am
So, the biggest advantage to developers is that code will work across all platforms and thus you can reach more users (I think ‘accounts’ is a more accurate term since many users have accounts on multiple sites). Yet, some applications will need to change to fit the needs of each site.
Chane says that most of the code can be reused, but I think the same argument applies to code on the Facebook Platform.
I guess we’ll see how this develops.
November 3rd, 2007 at 12:14 pm
nice interview justin.
i’ve met him chane once; seems like a pretty sharp guy.
November 4th, 2007 at 3:00 pm
[...] OpenSocial Interview Posted on November 4, 2007 by faceweek Great Google OpenSocial Interview from InsideFacebook.com Came across this excellent interview from InsideFacebook.com. Be sure to check it out – they do a [...]
November 6th, 2007 at 5:44 pm
[...] Inside Facebook – OpenSocial and the Facebook Platform: Interview with Peter Chane, Google Peter Chane, Google: “OpenSocial container sites will have activity streams that show activity from the user and their friends. Just like on Facebook, applications can publish stories to it. This is one channel that will really help applications spread.” (tags: facebook google opensocial socialgraph news) [...]
November 7th, 2007 at 2:07 am
[...] Chane, the Group Product Manager at Google for OpenSocial, has stated that OpenSocial will have some components of Facebook’s distribution system (newsfeed/mini-feed) [...]
November 7th, 2007 at 2:10 am
[...] to activate that userbase.Peter Chane, the Group Product Manager at Google for OpenSocial, has stated that OpenSocial will have some components of Facebook’s distribution system [...]
November 23rd, 2007 at 12:35 pm
How will secured be dealt?
December 18th, 2007 at 12:02 am
[...] failing in its bid to partner with or invest in Facebook, Google announced the OpenSocial API, an open API that would allow application developers to build apps to run on multiple social [...]
May 22nd, 2008 at 8:01 am
[...] As the Facebook Platform nears its one year anniversary – making it the “elder” amongst social networking platforms – the OpenSocial initiative continues to move forward. While the OpenSocial spec is still in version 0.7 and key containers like MySpace are rolling out full OpenSocial support very slowly, OpenSocial has come a long way since it was announced six months ago. [...]