Like mountain men in the industrializing West, a lot of smaller developers have been getting forced out — or forced to join larger companies. But some have not only hung on to their Facebook applications, they’ve also jumped to these new platforms. There, they also trap users with the most competitive game or the silliest poke.
[aditude-amp id="flyingcarpet" targeting='{"env":"staging","page_type":"article","post_id":93119,"post_type":"story","post_chan":"none","tags":null,"ai":false,"category":"none","all_categories":"social,","session":"C"}']As MySpace, Google and other social networking companies move in, I decided to ask one leading developer, Blake Commagere, how he was managing the changing world, especially the new frontier of the rival platforms. Commagere, who you may know as the creator of applications like Vampires and Werewolves on Facebook, tells me he has created leading applications on each network’s platform — with details on how he did it.
We now have two standards and if the huge markets that MySpace, hi5 and Orkut represent aren’t enough to convince all the Facebook developers out there to learn a new standard, I’d be surprised.
Frankly, Myspace could have come up with a completely different platform that didn’t conform to OpenSocial or Facebook and while a lot of developers may have complained (myself included), I would have still done everything necessary to port to MySpace. It’s a huge market – you’d have to be insane to ignore it.
VB: Do you think Facebook might merge its platform with MySpace and/or other social networks using OpenSocial?
BC: It would be interesting to know whether Facebook andOpen Social will take steps to ultimately merge their platforms – that would be a huge win for developers like me. In the meantime, I’ve already built a framework that allows my apps to run on both OpenSocial and Facebook, and I’ve considered open sourcing it, but I think it may be too constrictive to most application developers.
For example – if you aren’t using an MVC [software] architecture and PHP smarty templating, then conforming to my framework would probably feel like as much work as porting to another platform. It’s useful for me since I designed it for my apps to run on both Facebook and OpenSocial, but probably not useful to the rest of the world. What this means though is I’ve had to write an abstraction layer between my apps and the platforms since each platform has some differences – and while that abstraction layer was fun to create, the hope the development community had was that porting apps between social networks would be trivial, and we haven’t gotten there yet.
VB: So, how is that framework doing for you?
BC: My apps have taken a leading position on each platform – some of the platforms have more viral channels available and as a result the apps fare better on those platforms. I think the success of my apps has been consistent relative to other applications that have ported over as well.
As a breakdown:
On Bebo, the apps have done well – they are growing consistently, but not as quickly as they did on Facebook. It took me about 2 months to reach a million installs. A million users in 2 months is a great accomplishment and I think the only reason that that isn’t making headlines is many of us app developers have been spoiled by a million users in 10 days experiences and stories. The Bebo team did a great job of making ports easy – porting to Bebo took me 9 hours. Best. Decision. Ever. As far as differences in the network, the tone of Bebo is such that it allows for more anonymity in profiles. More anonymity results in a social graph that is not as strongly connected as the social graph in, say, Facebook and as a result, we see lower conversion rates through those viral channels. Think of it this way: You’re more likely to try out an application when you get the invite from “Blake Commagere,” a friend you know and have spent time with. Compare that to an invite from “EvilBoarder42,” a person you may not have met yet, but friended as a result of a mutual interest in snowboarding. Granted, on networks that permit more anonymity there are still tons of real friendships, but there will definitely be more weak links in the graphs the more anonymity is permitted.
My apps are doing okay on MySpace. They have not yet opened up newsfeed/notifications and so apps are relying on comment posts and bulletin posts to spread. Since MySpace has historically been very focused on self-expression, this is a good strategy, but widgets have been using those channels to spread for years, so the conversion rates are not as strong as they could be. Furthermore — MySpace does permit more anonymity than Facebook and as a result conversions do take a hit there. Once MySpace has newsfeed/notifications opened up, I think apps will explode in growth.
And, a very important point on the MySpace use of comments and bulletin boards as viral channels is this very important point: Over time any viral channel will result in diminishing returns from a user aquisition standpoint. (Think about the first time you got junk mail “oooh” with the last time “ugh”). The first times widgets (think slideshows from slide and rockyou) were using the bulletin boards on myspace as viral channels, they spread like wildfire. Now, since those channels have been leveraged significantly in the past, they aren’t going to produce the results they used to as users have been trained to look for unwanted messages in those channels, which is why we are all eager for MySpace to open up newsfeed & notifications.
On hi5, since they have opened up the notion of newsfeed/notifications, the apps have really exploded in growth! One thing I am eager to finish is a translation of my apps – I think that given the predominately international user base on hi5, I’ll see some huge benefits there.
VB: How have different implementations of OpenSocial affected your development time? What do you think about the new version of the OpenSocial technical specifications for its member social networks, version 0.8?
BC: Personally, I haven’t felt benefits or pain from the different platform customizations – most of the customizations seem to be just things leading up to 0.8 features anyway, rather than a departure from spec.
VentureBeat's mission is to be a digital town square for technical decision-makers to gain knowledge about transformative enterprise technology and transact. Learn More