fbpx

Share:

Twitter’s Internal Email Details Why it Shut Down API That Powered Tweetbot, Twitterrific

Share:

In an internal company email published by TechCrunch, Twitter has explained why it had to shut down the API that powered many features in popular third-party apps like Tweetbot and Twitterrific. The social media company cited “technical and business constraints” that it can no longer ignore as the main reason behind this decision.

Twitter

Twitter noted that some apps relied on “legacy technology” that was still in a “beta state” after more than 9 years, and had to be killed “out of operational necessity”. In reality, however, Twitter itself is the reason these APIs have been stuck in a beta state for nearly a decade. The company decided not to invest in supporting those legacy APIs, or shift them over to its new API platform.

Twitter continues to argue that its apps and website are “the best Twitter experience”, even as users take to the social network to complain that the company is #BreakingMyTwitter.

Below is the full email from Twitter’s director of product Rob Johnson:

Hi team,

Today, we’re publishing a blog post about our priorities for where we’re investing today in Twitter client experiences. I wanted to share some more with you about how we reached these decisions, and how we’re thinking about 3rd party clients specifically.

First, some history:

3rd party clients have had a notable impact on the Twitter service and the products we build. Independent developers built the first Twitter client for Mac and the first native app for iPhone. These clients pioneered product features we all know and love about Twitter, like mute, the pull-to-refresh gesture, and more.
We love that developers build experiences on our APIs to push our service, technology, and the public conversation forward. We deeply respect the time, energy, and passion they’ve put into building amazing things using Twitter.

But we haven’t always done a good job of being straightforward with developers about the decisions we make regarding 3rd party clients. In 2011, we told developers (in an email) not to build apps that mimic the core Twitter experience. In 2012, we announced changes to our developer policies intended to make these limitations clearer by capping the number of users allowed for a 3rd party client. And, in the years following those announcements, we’ve told developers repeatedly that our roadmap for our APIs does not prioritize client use cases — even as we’ve continued to maintain a couple specific APIs used heavily by these clients and quietly granted user cap exceptions to the clients that needed them.

It is now time to make the hard decision to end support for these legacy APIs — acknowledging that some aspects of these apps would be degraded as a result. Today, we are facing technical and business constraints we can’t ignore. The User Streams and Site Streams APIs that serve core functions of many of these clients have been in a “beta” state for more than 9 years, and are built on a technology stack we no longer support. We’re not changing our rules, or setting out to “kill” 3rd party clients; but we are killing, out of operational necessity, some of the legacy APIs that power some features of those clients. And it has not been a realistic option for us today to invest in building a totally new service to replace these APIs, which are used by less than 1% of Twitter developers.

We’ve heard the feedback from our customers about the pain this causes. We check out #BreakingMyTwitter quite often and have spoken with many of the developers of major 3rd party clients to understand their needs and concerns. We’re committed to understanding why people hire 3rd party clients over our own apps. And we’re going to try to do better with communicating these changes honestly and clearly to developers. We have a lot of work to do. This change is a hard, but important step, towards doing it. Thank you for working with us to get there.

Thanks,

Rob

If you are a regular Tweetbot or Twitterrific user, don’t forget to share your thoughts with us in the comments section.

Share: