Twitter being dicks to developers (again)
Over on .net, I offer my take on Twitter’s latest salvo against Twitter client devs. Personally, I think Twitter’s people are being total dicks in smacking third-party clients again. Short version: DMs will fail as of June 14 unless third-party clients utilise jump-through-hoops/user-unfriendly OAuth for login. Good luck to devs rewriting their apps and submitting iOS updates in that time-frame. Oh, and Twitter’s own apps aren’t affected, naturally, because they are “part of the service”.
Marco Arment provides an alternate take, the main argument of which appears to be:
These are the risks that you take when you base your personal happiness or your business on a single, irreplaceable, young, evolving third-party service.
Of course, he’s right in this. You are taking a risk when you base your income (or a chunk of it) on another company’s service. But Twitter’s also taking a risk in kicking out the ladder from underneath it. In controlling the platform and removing the apps that made it a success, it will piss of developers and millions of users. In offering regular hypocrisy (such as the bullshit about wanting third-party clients gone because a “consistent user experience is more crucial than ever”, despite its own clients being all over the place), it makes it so no-one can really trust what the company says. But, most importantly, as Matt Gemmell states in the article I wrote for .net:
Placing limitations on developers’ opportunities for innovation tends to be the death knell of a platform.
Twitter would argue that it wants innovation, just not in the client space. In other words, take Twitter data and do things with it. The thing is, Twitter’s users want and need innovation in the space Twitter is killing and yet not supporting fully on its own. But then Arment says, rightly:
The old Twitter is gone. The new Twitter is faster, bigger, much more stable, full of Javascript and dysfunctional hash-bang URLs, and much more interested in owning the clients that most people use. And next year’s Twitter might be radically different from today’s.
Or it might not exist at all, if it keeps screwing people over and everyone buggers off elsewhere.