Twitter explains why developers shouldn't build new clients
Ryan Sarver, a member of Twitter's platform/api team, took a few minutes today to address concerns about the Twitter ecosystem and in particular its announcement on Friday that developers shouldn't develop new twitter clients.
Context & Ripple Effects
This is the second time Twitter has had to manage a developer revolt, and the pattern is hardening. In April 2010 the company issued an official response trying to calm ecosystem fears after earlier policy shifts (officially responding to developers); this week it went further, announcing on March 11 that developers should stop building competing clients and focus on data and verticals instead, backed by new mandatory terms for everyone in the ecosystem (dropping the ecosystem hammer). The Tweetie acquisition — folded into Twitter's own native iPhone app — already showed the company prefers owning its core clients.
Two days later, Ryan Sarver of the platform/API team took to explaining the rationale rather than retracting it, which signals the policy is settled. Reaction was immediate and skeptical: @carnage4life tweeted that telling developers certain app types are 'bad business' sounds threatening whether intended or not, and critics warned Twitter is bulldozing its own app ecosystem. The stakes are visible in the same week's news — Japanese users turned to Twitter as cell networks jammed after the March 11 earthquake, underscoring how much reach rides on clients Twitter doesn't control.
First-order effects
- Existing third-party client developers now compete directly against Twitter's first-party apps under mandatory terms of service that formally reserve the client category for the company itself.
- Developers must reposition toward the lanes Twitter has designated — data products and vertical applications — or exit the ecosystem.
Second-order effects
- Capital and talent that funded client startups will redirect toward analytics, vertical tools, and enterprise data services, since the client category is now officially closed.
- Every consumer platform watching this exchange inherits a template: acquire a leading client (the Tweetie route), then declare remaining independent clients off-limits — raising the perceived risk of building on any single company's API.
Third-order effects
- If the pattern holds, open-API consumer platforms structurally converge on controlled distribution: the developer ecosystem persists only in categories the platform deems non-core, and platform risk becomes a priced factor in every build decision.
- The trust contract between platforms and third-party developers weakens system-wide — developers who watched Twitter reverse course from its 2010 reassurances will discount future promises from any platform making similar ones.
The trend: Consumer internet platforms are converting formerly open developer ecosystems into controlled distribution channels, reserving their most valuable surface areas — clients and media — for first-party products while pushing third parties into data and vertical niches.