Stay on Top of Enterprise Technology Trends
Get updates impacting your industry from our GigaOm Research Community
The past week has seen a lot of drama around Twitter’s relationship with third-party app developers. Fred Wilson’s post about the company’s evolution seemed to touch off a powder keg of emotion about what the company’s approach to new services might be, and that was still bubbling when Twitter announced that it had bought Atebits, maker of the iPhone app Tweetie, which touched off a new round of criticism. Developers have protested on a Google group, formed a Twitter group with the hashtag #unionoftwitterapps and made caustic comments about the company in blog posts, podcasts and pretty much everywhere else.
Wilson’s post suggested that Twitter had grown so large and ubiquitous that it had reached an “inflection point,” where it could become the center of a developing ecosystem or infrastructure of other products and services. But the acquisition of Tweetie put a different spin on that message: the implication seemed to be that Twitter had become so large and ubiquitous that it could (and possibly should) either acquire or compete with the third-party apps that have grown up around the company. And the reason it wants to do that is pretty obvious: to own the relationship with the user.
Developer Ben Metcalfe has some suggestions about what Twitter could do next week during the Chirp conference to create opportunities for third-party developers in a number of areas, as a kind of “exit strategy.” But as Chris Dixon of Hunch points out in a blog post, the biggest remaining hurdle for both Twitter and third-party developers is the fact that neither side knows what the company’s eventual business model will be (or if Twitter knows, it isn’t saying). That vacuum is what is causing a lot of the tension, and it likely won’t go away entirely until the vacuum is filled.
Some companies might think: “Why should we care whether developers are mad at us or not? We own the ecosystem — without us, they would have nothing, so they can just sit there and take it, while we compete with them or buy one of their competitors or whatever else we want to do.” But the reality is that many of those third-party apps did provide a substantial amount of functionality that Twitter was missing, whether it was photo uploading or URL shortening or geo-location. Maybe some developers did take a ride on Twitter’s coattails — but others did add value, and as a result helped Twitter become the global phenomenon it is now.
And trying to extend some kind of olive branch to the developer community that has built up around Twitter isn’t just a nice thing to do. As large as it is, and as much money as it has now, the company can’t realistically build all the things it needs or acquire all the things it needs tomorrow. It is still going to need lots of help, and the benefits of a thriving developer ecosystem are manifold: not only does it produce valuable add-ons that might never have occurred to Twitter HQ, but it is also a very powerful form of marketing, both for the product and for the company itself.
“There’s some misunderstanding around platforms,” Evan Mr. Williams told the New York Times. “I’ve been trying to figure out how to talk to developers about this.” Hopefully the Twitter CEO has found a way, because the company’s Chirp conference is next week, and there are going to be plenty of people looking for answers.
Related content from GigaOM Pro (sub req’d):
Post and thumbnail photos courtesy of Flickr user Image Munky