Google's OpenSocial Too Late To Be a Win?

DeeQ writes with a link to a post on News.com's social networking blog. Author Caroline McCarthy wonders if Google's OpenSocial initiative has missed its moment in the sun. It's been something like six weeks now since the search giant offered up its open-source social media initiative ... but where have been the usual swift victories? Moreover, OpenSocial isn't done yet, and it's not expected until sometime next year. In the meantime Facebook is capitalizing on Google's delay, and other networks are stepping in as well. "Kraus adds that some of the independent platform strategies would be necessary even if OpenSocial were finalized. One of them is LinkedIn's 'InApps,' which also aims to spread LinkedIn's data and influence outside the business-oriented social network through partnerships with other Web sites. 'OpenSocial so far is really about how developers embed their application into a social network,' Kraus explained. 'A good chunk of LinkedIn's APIs is about how LinkedIn extends their social-networking data into other sites.'"

Comments

Re:Needs to find its niche

[blitzkrieg3]

For it to work, OpenSocial has to find its focus--it needs something to separate it from the other social networking sites beyond merely being a Google project. If it doesn't, it's just going to go the way of Friendster--it'll be out there, but nobody will really be using it.

I think you're really missing the point. Google wants all these different networks, that have different niches, to have access to each other. So now I'll still have a facebook for friends at school, a myspace for my band, and a flickr for photos, but I won't need to upload all my photos to EVERY website using they're own implementation of photos.

There will still be different niches, but I'll be able to manage each of my different "personalities" (if you will) from one place.

Re:Worried about Google investors

[Sloppy]

how do they actually plan to lock in their position ?

One and a half ways, as far as I can tell:

1. If they can get multiple (popular) sites to use the same API, so that add-on developers only have to write one version of the code, then that creates a feedback loop. It makes site developers want to use the API in order to take advantage of existing add-ons, and it makes add-on developers want to use the API to take advantage of existing sites.
2. The API is sold to the public as being for developers. But one of the things I quickly noticed about it, is that it's good for more than that. It's also great for crawlers. Why crawl a site and try to make sense out of their HTML structure, when there's an API call to get someone's friends list? If sites adopt this API, it will allow Google (not really lock-in; any other crawler could do it too) to make semantic sense of "social" websites, which happen to be popular. Maybe some day you'll be able to google "friends:El Cabri" and get all sorts of ideas for ways the info could be [ab]used. Crawling is part of Google's business anyway (they're a/the leader) so this could strengthen them.

Re:social web sites

[Lemmy Caution]

There is a third use for them that is related to the "keeping in touch with people." The little apps in Facebook act as a mechanism for maintaining social interaction, and allow managed cross-involvement between groups of friends. In other words, I can have my brother (in Texas) join me (on the West Coast) and a colleague (in New York) over a game of Scrabble, and chat with each other. Because it aggregates all your "social attention" in one place, it isn't like trying to cobble interest in one of a million "online scrabble" sites.

And the "keep in touch" function isn't important for close friends: it's better for staying in touch with acquaintances and more distant friends, giving you a viable reason to drop a quick hello without the awkward "I know it's been years since we've chatted, but..." In the space between the deeply personal and the completely professional is a kind of sociability that is vital for many people's careers.

Compare to Facebook's

[aftk2]

I don't know - I was skeptical about Facebook's API when I learned that our company would be developing apps for its platform. But it's actually pretty impressive. You have several different views and footprints at your application's disposal, a number of different ways to promote your app, an easy route to making your application interactive (FBML) as well as more advanced methods (FQL, the web service API).

Contrast that with OpenSocial. I recently wrote a white paper on it, which I wouldn't mind getting feedback on. It should make OpenSocial's strengths (and its significant weaknesses) pretty apparent:

A First Look at OpenSocial
Answering Questions About Google's Effort at Standardizing Social Network Widgets, and the Creation of Your First OpenSocial Widget .