ReadWriteWeb

OpenSocial's Failed Promise: Only 0.7% of Apps Have Crossed Networks (Updated)

Written by Marshall Kirkpatrick / May 27, 2009 2:03 PM / 41 Comments

When the Google-led OpenSocial campaign launched in October 2007 it aimed to give developers a common environment that application publishers could publish widgets to with one set of code, deployable across Google sites, MySpace, Hi5 and numerous other social networks.

A directory of OpenSocial Apps launched today and the reality is even further from that goal than we expected. Out of 12,456 apps listed, only 83 are running on two or more "containers." That's 0.7% or one out of every 1500. Update: See this reply below from Google's Kevin Marks. Marks says that cross-network presence was counted manually and is actually larger than it appears in the directory.

opensocialdirector.jpg

OpenSocial was intended to help everyone else keep up with the huge success of the Facebook platform. If there's one clear market leader, everyone else has a common interest in creating a standard that will help scale the market opportunity on their platforms vs. what Facebook can offer. It hasn't worked out that way, though.

Outside observers hoped that OpenSocial would allow for user data to be transmitted from one site to another. People thought this was the coming of Data Portability, though OpenSocial advocates quickly said that wasn't the intent. It was just for apps to port, not user data. There is a lot of innovation going on in OpenSocial - it's a shame the platform isn't better appreciated.

Below: I discuss OpenSocial in March of last year on G4TV, forced to break the host's heart about data portability!

Why hasn't cross-network development happened though? There are a few theories. The most common is that though there is a common bed of code across all the different social network containers, each of them is also tweaked just enough that it's not that easy to "write once." When that became apparent, OpenSocial advocates started saying that the standard still made it a lot easier to develop for multiple networks. So if not "write once, deploy everywhere" then perhaps it was "write once and then take a lot less time to write for elsewhere than you'd have to otherwise."

Clearly developers haven't taken advantage of that opportunity.

Google's Kevin Marks, one of the leading public faces for OpenSocial, told us today that there are serious cultural differences between the networks and that this could help explain why there hasn't been more cross pollination. One look through the directory makes it clear though that while the countless "hot bikini girl" apps may not translate from MySpace to LinkedIn well, all the other networks have their own isolated versions of many of the same insipid apps.

The most viable explanation could be that Facebook is in fact the only game in town for the most sophisticated developers. That's a real shame, because it's never good for innovation for there to be only one game in town.


Comments

Subscribe to comments for this post OR Subscribe to comments for all ReadWriteWeb posts

  1. Hi Marshall, I spoke to the developer behind this directory, and he said that at the moment the apps that are labelled as multi-container have been correlated by hand, so the number of multi-container apps has certainly been undercounted. As the FAQ says:
    http://wiki.opensocial.org/index.php?title=OpenSocial_Directory

    My app is live on more containers than the directory gives me credit for. What's up with that?
    We don't have data from all containers yet. Even when we do, it can be difficult to map several gadget XML files to the same logical app running on multiple containers. We are planning to add functionality to give app developers more control over how their gadget XML files are grouped into applications running on multiple containers.

    The goal of this directory is to help app developers and container developers to find each other and enable more applications to move between containers, to help address the cultural and linguistic barriers between porting applications.

    As for your 'Data Portability' point, with OpenSocial REST APIs, and their compatibility with OAuth and PortableContacts, we are seeing a sea change in how people can move their data across the web - in particular the OpenID + OAuth +PoCo hybrid login has been adopted by Friendfeed and Facebook recently, joining Plaxo in providing a much smoother sign-up process for new users and friend-finding for existing users.
    In addition, Google Friend Connect is building on these same open standards to enable any web site to become a social site and support delegated login, friend and activity connections, and embedding gadgets on the page.

    Posted by: Kevin Marks | May 27, 2009 3:39 PM



  2. Thanks for the comment Kevin. Will update post with a note referencing your reply .

     Posted by: Marshall Kirkpatrick Author Profile Page | May 27, 2009 3:43 PM



  3. I think the problem is people just don't really care if they run an app inside a social network or on an external domain. So rather than work around all the differences between each OpenSocial container developers are simply building stand-alone websites to interface with Google Friend Connect and Facebook Connect. I was really excited about OpenSocial when it was introduced, but now my excitement has diminished and I'd almost rather open up a plain vanilla OAuth API than an OpenSocial container. I don't need apps running within the confines of my website, they can run anywhere.

     Posted by: Scott Author Profile Page | May 27, 2009 3:43 PM



  4. Marshall,

    There is another benefit of opensocial apps that you have to consider. Say, I learn the opensocial way of building apps.

    One benefit, is of course, to be able to port the same app to multiple platforms/containers, which as you pointed is not happening a lot.

    The other benefit (although comparatively smaller) is that I can use my opensocial skills that I just learned for my one-container app to make another one-container app in the future for any of the other opensocial-participating platforms. So, my skills become portable.

    This second benefit I am sure helps in the way of increasing the total number of apps built via Opensocial for their target platforms.

    Posted by: Manpreet | May 27, 2009 4:09 PM



  5. There are many shades to open social implementations. Twitter's OAuth requires the third-party applications to sit on their server. We do not want the over-capacity complication and decide on the say-hi-and-bye method to let Twitter users sign into isayusay.net as guests, create live social mail in a snap, and post them to Twitter with custom messages.

    Posted by: isayusaymax | May 27, 2009 4:43 PM



  6. Opensocial still has great promise for building social networking apps, but it just can't seem to reach that critical mass.

    Posted by: Free People Search | May 27, 2009 4:47 PM



  7. I like your point about the cultural differences between networks and how apps that appeal to members of one social network won't necessarily be as popular in another.

    The best apps meet the needs of a specific market. Different networks attract different "markets" of people so this will be a huge factor in what catches on and what doesn't, regardless of the technology.

    Posted by: Christen Posted on FriendFeed   | May 27, 2009 5:04 PM



  8. @Scott:

    You can still be excited about OpenSocial, and build apps targeted at any website via Google Friend Connect. There are 5 million 30-day active Google Friend Connect enabled sites and blogs out there.. and they all have the capability to host any OpenSocial application. However, keep in mind that the types of applications which work well embedded on a variety of websites are different than those which work well on traditional social networks. :)

    Posted by: Ryan Boyd | May 28, 2009 7:05 AM



  9. Well I can simply explain why we haven't embraced it...

    Because it does not support being present at the 'content creation page' along the editor.

    As OpenSocial is currently structured it is more or less advanced widget with insight into the network, but not actually plugged into parts of the platform developers would like to be plugged in...

    This is very similar to what Ryan Boyd says: "keep in mind that the types of applications which work well embedded on a variety of websites are different than those which work well on traditional social networks."

    I hope this will change soon! :)

    bye
    Andraz Tori, Zemanta

     Posted by: Andraž Author Profile Page | May 28, 2009 10:28 AM



  10. @Ryan Boyd I'm more interested in OpenSocial from a container standpoint. I run a social network that focuses on developers, so it seems like a logical fit. What I'm considering now is using it more as an OAuth API interface to open up my data.

    Posted by: Scott Aikin | May 28, 2009 11:02 AM



  11. I wonder whether Google Wave will breath new life into OpenSocial? If the environment Google is building enables network site owners to build an app which runs inside Wave and enables the user to see activity relating to their account and contacts, then should Wave revolutionise e-mail, IM and socnet participation an OpenSocial involvement may become mandatory.

    As a network owner I'll be watching this side of things closely.

    Ian Hendry
    CEO, WeCanDo.BIZ
    http://www.wecando.biz

     Posted by: Ian Author Profile Page | June 1, 2009 12:18 AM



  12. OpenSocial's Failed Promise: Only 0.7% of Apps Have Crossed Networks http://bit.ly/ltZJw :( sad [from http://twitter.com/marshallk/statuses/1940079370]

    Posted by: Marshall Kirkpatrick Posted on FriendFeed   | June 10, 2009 8:57 AM



  13. There are many shades to open social implementations.

    Posted by: Water meter | June 18, 2009 7:55 PM



  14. wonder whether Google Wave will breath new life into OpenSocial? If the environment Google is building enables baless

    Posted by: hikayeler | June 30, 2009 11:47 PM



  15. Jerry, What a small world! That's incredible. Hopefully our paths will cross again (and more explicitly) one day... Best wishes yerss

    Posted by: netlog | July 1, 2009 8:51 AM



  16. Jerry, What a small world! That's incredible. Hopefully our paths will cross again (and more explicitly) on onem u

    Posted by: cet | July 1, 2009 10:04 PM



  17. wonder whether Google Wave will breath new life into OpenSocial? If the environment Google is building enables baless

    Posted by: aziz | July 16, 2009 9:35 AM



  18. I like your point about the cultural differences between networks and how apps that appeal to members of one social network won't necessarily be as popular in another.

    The best apps meet the needs of a specific market. Different networks attract different "markets" of people so this will be a huge factor in what catches on and what doesn't, regardless of the technology.

    Posted by: aspatron | July 16, 2009 9:37 AM



  19. Great article - thanks! It is so important for people to do their homework when starting domain development. If you're interested in learning even more, here is another great site to visit http://BeyondDomaining.com

    Posted by: Beyond Domaining | July 17, 2009 10:53 AM



  20. Tnank a lot![url=http://www.kscastings.com/]Investment Castings[/url]

    Posted by: mary jone | July 20, 2009 5:48 PM




  21. Most apps would have to meet the current market needs, apps are much better than old days and more people started studying application design courses in london where i study it myself. There is good money in the sector.

    Posted by: Payday Loans | July 25, 2009 5:02 AM



  22. thanks for this good article. Its true!

    Posted by: buggy | August 4, 2009 12:46 PM



  23. I like your point about the cultural differences between networks and how apps that appeal to members of one social network won't necessarily be as popular in another.

    Posted by: muhabbet | August 5, 2009 4:49 PM



  24. I was really excited about OpenSocial when it was introduced, but now my excitement has diminished ..Thanks for that nice article..

    Posted by: araba oyunları | August 18, 2009 2:46 PM



  25. The best apps meet the needs of a specific market. Different networks attract different "markets" of people so this will be a huge factor in what catches on and what doesn't, regardless of the technology. Thanks.

    Posted by: araba oyunları | August 19, 2009 5:30 AM



  26. Thanks for nice article...I like your point about the cultural differences between networks and how apps that appeal to members of one social network won't necessarily be as popular in another...

    Posted by: giydirme oyunları | August 19, 2009 5:47 AM



  27. thanks for this good article. Its true!

    Posted by: netlog | September 3, 2009 7:16 AM



  28. You've got a real problem with comment spam as people seek links from your site.

    Posted by: ReaderX | September 23, 2009 7:38 AM



  29. Great article - thanks! It is so important for people to do their homework when starting domain development.

    Posted by: ravi | September 25, 2009 8:57 AM



  30. Want to see Open Social Doing Big things!

    Visit the # 1 Open Social - TV Social Network
    TVFanSpace.com - 90 days after launhc its going wild with signups and traffic!

     Posted by: TVFanSpace.com Author Profile Page | September 28, 2009 6:36 AM



  31. If the environment Google is building enables network site owners to build an app which runs inside Wave and enables the user to see activity relating to their account and contacts, then should Wave revolutionise e-mail, IM and socnet participation an OpenSocial involvement

    Posted by: Dress | October 1, 2009 4:33 PM



  32. Great article - thanks! Its true!
    Wonder Google Wave will breath new life into OpenSocial?

    Posted by: Microfaser | November 30, 2009 8:52 AM



  33. I totally agree with this point that Only 0.7% of Apps Have Crossed Networks (Updated). Even I had seen many social applications that are been crossed.

    Posted by: ropes | December 19, 2009 6:14 AM



  34. thank you very muhch. bunuda yayinlamazsiniz taa:))

    Posted by: indir | December 22, 2009 12:58 AM



  35. Good post. Will watch it. Maybe you have also have a look to Gioco di Bowling

    Posted by: Barbie Giochi | January 10, 2010 5:06 PM



  36. bu bilgiler için teşekkür ederiz.

    Posted by: Kız Barbie Oyunları | January 10, 2010 5:08 PM



  37. Thanks for nice article...I like your point about the cultural differences between networks and how apps that appeal to members of one social network won't necessarily be as popular in another...

    Posted by: Giochi di Barbie | January 21, 2010 7:40 AM



  38. thanks

    I like your point about the cultural differences between networks and how apps that appeal to members of one social network won't necessarily be as popular in another...

    Posted by: منتديات | February 2, 2010 8:24 AM



  39. thank you very muhch. bunuda yayinlamazsiniz taa:))

    Posted by: مركز تحميل | February 2, 2010 11:53 PM



  40. Hi,
    Many of Facebook's users are online and interacting with the site for hours each day and no doubt have a personal connection to what goes on there.They are my trade magazines, and while I'd never cancel my subscriptions, I am as guilty as most people of ignoring them. On the other hand, I never fail to read Tampa's major daily newspaper every morning (with coffee cup in hand) and monitor certain news websites...

    Posted by: DIŞ CEPHE KAPLAMA | February 4, 2010 4:44 AM



  41. opensocial apis create great opportunity for web 2.0

    Posted by: zayıflama | February 8, 2010 8:34 AM



Leave a comment

Optional: Sign in with Connect Facebook   Sign in with Twitter Twitter   Sign in with OpenID OpenID  |  

If you think Twitter is big, check out the Real-Time Web
RWW SPONSORS



FOLLOW @RWW ON TWITTER

ReadWriteWeb on Facebook
ReadWriteCloud - Sponsored by VMware and Intel



TEXT LINK ADS



RWW PARTNERS