"... I'd steer well clear of building anything that I expected to make money on for Facebook. ..."
Been thinking about this problem. There is a trend at the moment for web2 companies creating apps, exposing API's then allowing third parties to use them. If this is a trend and consolidation occurs is it wise to use these API's? Will there be a choice as large numbers of users move to these online apps effectively recreating the monopolies that past operating systems had?
Could a solution be to spread the usage of API's across a larger number of services?
I've been researching widgets/gadgets a bit and the Netvibes API allows cross-platform widgets...which removes their monopoly power, and insures that even if they replicate your functionality, you can refocus on other sources of users.
So, if one were to abstract the Facebook API into a "social networks" API of your own, it'd be a sane path. Then, if Facebook launches an exact duplicate of your app, you just refocus your efforts on MySpace, Xanga, LinkedIn, whatever.
Of course, this assumes that the others follow the lead of Facebook (which I think is a great idea business-wise--APIs are great for business and good for your users...but not good for your "partners", if you have a habit of picking the winners and killing them with your own implementation).
So, I'm definitely not saying folks shouldn't make use of the Facebook API. But think about using it to add value to something already valuable, rather than just building tools that live and die by involvement with Facebook.
Been thinking about this problem. There is a trend at the moment for web2 companies creating apps, exposing API's then allowing third parties to use them. If this is a trend and consolidation occurs is it wise to use these API's? Will there be a choice as large numbers of users move to these online apps effectively recreating the monopolies that past operating systems had?
Could a solution be to spread the usage of API's across a larger number of services?