By John Gruber
WorkOS: APIs to ship SSO, SCIM, FGA, and User Management in minutes. Check out their launch week.
The End of Third-Party Twitter Clients?
Wednesday, 16 May 2018
After August 16th, 2018, “streaming services” at Twitter will be removed. This means two things for third-party apps:
- Push notifications will no longer arrive
- Timelines won’t refresh automatically
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 and have had one reprieve.
This antipathy to third-party clients is especially confounding considering that Twitter recently dropped support for their own native Mac client. As far as I’m aware, once this comes to pass next month, there will be no way to receive notifications of Twitter DMs on a Mac. None. (Twitter’s website doesn’t even support Safari’s desktop notification feature.) That’s just wacky.
Twitter management obviously wants to steer people to their first-party mobile app and desktop website. I get that. But they already have that: the overwhelming number of Twitter users use exactly those products to access the service. What Twitter management seems to be missing is that many of its most influential users — including yours truly, yes — have been on the platform a long time and have a high tendency to be among those who not just use, but depend upon third-party clients.
To me this is like finding out you’re now required to access email entirely through a web browser. Sure, lots of people already do it that way and either prefer it or think it’s eh, just fine, who cares — but a lot of others hate it and find it completely disruptive to longstanding workflows.
Twitter isn’t explicitly saying that they’re shutting down third-party clients, but I don’t know that it’s feasible for them to exist if they don’t have access to these APIs. It’s like breaking up with someone by being a jerk to them rather than telling them you’re breaking up.
I urge Twitter to reconsider this decision. Third-party clients account for a relatively small part of the Twitter ecosystem, but it’s an important one. Twitter may not care about a native Mac client, but the users of these apps, and the developers who make them, certainly do.