Once again Twitter is about to do what we’ve come to expect from the company. From Apps of a Feather:
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…
This change, currently poised to happen after June 19th, 2018, means two main things: push notifications will no longer arrive and timelines won’t refresh automatically anymore. Currently there’s no way for third-party developers to fix these things. Twitter has yet to give third-party developers access to the new Account Activity API. But even if they should get access in time to fix their applications, things like push notifications will be inherently limited, essentially rendering them useless:
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.