After June 19th, 2018, “streaming services” at Twitter will be removed. This means two things for third-party apps:
If you use an app like Talon, Tweetbot, Tweetings, or Twitterrific, there is no way for its developer to fix these issues.
We are incredibly eager to update our apps. However, despite many requests for clarification and guidance, Twitter has not provided a way for us to recreate the lost functionality. We've been waiting for more than a year.
This change affects people who use third-party Twitter apps. All software platforms are affected, but it’s worse on iOS and Android where users rely on push notifications to know when something happens on Twitter.
Third-party apps open a network connection to Twitter and receive a continuous stream of updates (hence the name). For push notifications, this connection is done on the developer’s server and used to generate messages that are sent to your devices. For timeline updates, the stream is opened directly on your mobile device or desktop computer.
This streaming connection is being replaced by an Account Activity API. This new infrastructure is based on “webhooks” that Twitter uses to contact your server when there’s activity for an account. But there are problems for app developers…
The new Account Activity API is currently in beta testing, but third-party developers have not been given access and time is running out.
With access we might be able to implement some push notifications, but they would be limited at the standard level to 35 Twitter accounts – our products must deliver notifications to hundreds of thousands of customers. No pricing has been given for Enterprise level service with unlimited accounts – we have no idea if this will be an affordable option for us and our users.
Automatic refresh of your timeline just won't work: there is no web server on your mobile device or desktop computer that Twitter can contact with updates. Since updating your timeline with other methods is rate-limited by Twitter, you will see delays in real-time updates during sporting events and breaking news.
A recent statement by Twitter sheds some light on this situation. In response to a query about the new Bookmarks feature they said:
… as we stated on the blog nearly a year ago, the API plans are focused on data features and access, more than on delivering client app product features.
Push notifications and automatic timeline updates are both client app features.
Despite a long history of third-party contributions to the Twitter ecosystem, the company continues to actively discourage “client apps that mimic or reproduce the mainstream Twitter consumer client experience.” Including platforms where there is no native app.
As third-party developers, our hands are tied. However, you can help by letting Twitter know how you feel:
Many folks don't realize that their favorite Twitter app is about to break, so awareness is the first step. Together, we may be able to get Twitter to constructively address this state of affairs before the June deadline.