What Apps Will Be Screwed by Twitter’s API Changes? [Twitter]on August 17th, 2012
Today Twitter announced a series of API changes aimed at “mainstreaming” the user experience of the product. In other words they don’t want you to use any apps to access your account besides its own. Here’s what’s on the chopping block.
Twitter’s still being pretty coy about which apps will and won’t be granted authorization saying that its guidelines for developers remain guidelines for developers:
… includes, of course, “traditional” Twitter clients like Tweetbot and Echofon. Nearly eighteen months ago, we gave developers guidance that they should not build client apps that mimic or reproduce the mainstream Twitter consumer client experience.” And to reiterate what I wrote in my last post, that guidance continues to apply today.
So that’s two right there that are definitely on their way out unless they evolve. It seems like Twitter aims to keep them out either by refusing to authorize them or by limiting access to the API such that it’s impossible for the apps to continue. Maybe? Twitter’s certainly leaving themselves a lot of wiggle room to pick and choose who they do and do not like. Twitter broke down apps into four quadrants. It’s cool with everything that’s not in the top right:
What other apps are about to go? Who’s OK? Here’s the beginnings of a list:
Probably screwed Clients
Plume for Twitter
Probably OK Supported by Twitter statements
OK Owned by Twitter
What else is on its way out? Let us know below and we’ll update. We also pinged Twitter to see how hard Twitter plans to come down on apps that violate its guidelines. We’ll let you know when they get back to us.