For much of the past year, the Twitter ecosystem has been in a state of flux. Ever since Twitter bought Tweetie and turned it into their own native iPhone app, third-party developers have been wondering where this would leave them. Further moves by Twitter into Android, iPad, Mac, Windows Phone, BlackBerry, and other spaces have only compounded some of this fear. So Twitter has taken some time today in their developer forum to talk a bit about the state of the ecosystem and give some guidance. It’s blunt, but necessarily so.
Specifically, Platform lead Ryan Sarver has a fairly lengthy outline of Twitter’s line of thinking with regard to third-party clients and services. And while there’s a little bit of dancing around the topic at first, it quickly gets very clear: third-parties shouldn’t be creating straight-up Twitter clients any further.
Sarver notes that Twitter views a “consistent user experience” as very important to them. And it’s something they’re going to hold third-party developers to a very high standard to maintain. But they don’t want them to mimic Twitter’s own experience with their native apps in order to do this. They’ve updated the API Terms of Service to reflect all of this.
“Developers have told us that they’d like more guidance from us about the best opportunities to build on Twitter. More specifically, developers ask us if they should build client apps that mimic or reproduce the mainstream Twitter consumer client experience. The answer is no,” Sarver writes very matter-of-factly.
“If you are an existing developer of client apps, you can continue to serve your user base, but we will be holding you to high standards to ensure you do not violate users’ privacy, that you provide consistency in the user experience, and that you rigorously adhere to all areas of our Terms of Service. We have spoken with the major client applications in the Twitter ecosystem about these needs on an ongoing basis, and will continue to ensure a high bar is maintained,” he continues.
Sarver notes that according to Twitter’s own data, some 90 percent of active Twitter users now use official Twitter apps on a monthly basis to access the service.
“We need to move to a less fragmented world, where every user can experience Twitter in a consistent way. This is already happening organically – the number and market share of consumer client apps that are not owned or operated by Twitter has been shrinking,” he writes.
The biggest third-party client in the space is TweetDeck, which was in the process of being acquired by UberMedia when Twitter suspended their apps a few weeks ago for TOS violations. I’ve reached out to Twitter to see where TweetDeck and UberMedia stand now with the new rules but my hunch is that TweetDeck is it’s currently constituted will be okay — it has too many users to be taken away. But if I were a third-party developer, I probably wouldn’t invest time in creating a new TweetDeck-like app.
So where should third-party developers look towards in terms of developing for the ecosystem? Sarver highlights the following areas:
Sarver highlights Twitter’s “diverse ecosystem” of more than 750,000 registered apps. But that ecosystem definitely just got altered quite a bit today. Remember, this is business, not personal.
Created in 2006, Twitter is a global real-time communications platform with 400 million monthly visitors to twitter.com, more than 200 million monthly active users around the world. We see a billion tweets every 2.5 days on every conceivable topic. World leaders, major athletes, star performers, news organizations and entertainment outlets are among the millions of active Twitter accounts through which users can truly get the pulse of the planet.