I shared the following message with our Twitter team this morning 
We just published a blog post about our priorities for Twitter client experiences. I want to share some insight on how we reached these decisions, and how we’re thinking about 3rd party clients moving forward blog.twitter.com/official/en_us…
First, some history. 3rd party clients have had a notable impact on the Twitter service and the products we built. 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.
We love that developers build experiences on our APIs to push our service and technology forward. We deeply respect the time, energy, and passion they’ve put into building amazing things using Twitter
We’ve shared with developers repeatedly that our roadmap for our APIs does not prioritize 3rd party 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. We haven't been clear enough
It’s now time to make the hard decision to end support for these legacy APIs — acknowledging that some aspects of these clients will be degraded as a result. We are facing technical and business constraints we can’t ignore and need to turn these off
We introduced the Account Activity API as a faster & more streamlined way for developers building customer service and brand engagement tools, chatbots, + more. As this new API doesn’t include home timeline data, it is not intended as a solution for 3rd party clients
We’ve heard feedback (#breakingmytwitter) from our customers about the pain this causes. We’re committed to understanding why people hire 3rd party clients over our own apps, and we’re going to do better with communicating changes
We know we have a lot of work to do. Thank you for working with us to get there.
