Av: Stefan Deak

Stefan Deak — Tue, 10 Mar 2009 07:41:38 +0000

It is not quite the same thing to use Facebook’s, Orkut’s or Hi5′s platform in order to build an application using an API and to build a separate platform which can be populated by Facebook’s, Orkut’s and Hi5′a members.

I’d like to think about it sort as of a car (the community) and it’s driver (a visitor with implicit and explicit preferences). Depending on the driver the car will be handled in different ways.

And just like about any driver can swap easily between cars so I imagine that this member database should work. You just logon and all your network bindings and information will be there. The only thing you’ll need to do is to tune your privacy settings.

For newly launched services such a database could be a way to get going quickly. For companies handling such databases you could make money by leasing out users, but they would also have the possibility aggregate new user data since they would still own the account data.

Av: Jesper Åström

Jesper Åström — Mon, 09 Mar 2009 12:06:10 +0000

In some way it allready has been done. Just think of the cross platform applications for facebook, Hi5, Orkut etc. Such applications focus and appeals to a specific interest of a certain population. They tap into the db’s of the allready existing monsters and extract the data they need in order to turn revenue or stickiness from/to these online ”institutions” or subcultures.

Also, I would really recommend anyone interested to tap into the HUGE resources of Yahoo Developer Network. My god.. I got a lump in my stomac when I realized how much info is actually public :)

//Jesper

Kommentarer till The next development phase for services featuring large member databases

Av: Stefan Deak

Av: Jesper Åström