Earlier this summer, ProgrammableWeb announced that Twitter API changes would lead to Twitterrific ending real time updates and push notifications. Although Twitter delayed its API moves, the time has come. On August 16 (next week), Twitter will deprecate Site Streams, User Streams, and legacy Direct Message endpoints.
Twitterrific has been bracing its user base for these changes for most of this year. But, Twitterrific isn’t the only one affected. For example, Tweetbot, another Twitter client, has been prepping for this change as well. From Tweetbot’s website:
“On August 16th Twitter will be removing the streaming API used by Tweetbot and other 3rd party clients. They have a replacement API with most of the same features and we are trying to get access to it. Even if we can’t get access to this new API, the majority of features in Tweetbot will still work. In the worst case scenario we won’t be able show notifications for Likes/Retweets and notifications for Tweets, Mentions, DMs & Follows would be delayed for 1-2 minutes. You’ll still be able to read your timeline, mentions, DMs and post Tweets just like you do today.”
Despite the frustration from Twitter’s developer community, Twitter does not appear to be changing course. It’s latest post on the Twitter Developer Forum reiterates the August 16 deprecation date, and guides developers to the Account Activity API. To assist developers, Twitter has published two migration guides: the Account Activity Migration Guide and the Direct Message Migration Guide. Twitter has also published a playbook for developers building apps the ingest data and respond to direct messages.
Twitter has not skimped out on developers in helping them transition to the Account Activity API. But, there is no denying that features are going away. Further, Twitter’s new API strategy comes at a cost to developers and third party apps. The cost aspect is certainly not helping Twitter’s relationship with those already angered by its decision. Nonetheless, Twitter has announced that it will continue frequent communication with any developer affected by its changes and hopes to continue growing its developer relationships.