Twitter to Devs: Don't Make Twitter Clients... Or Else
Pure play Twitter clients — apps like Echofon, Twidroyd and UberTwitter — got a sharp slap on the wrist today from Twitter platform chief Ryan Sarver. — In an API announcement post, Sarver finally made clear what third-party developers …
Context & Ripple Effects
Twitter had already acquired Tweetie and converted it into its native iPhone app, putting the company in direct control of a major access point to its service. The prior day's developer-roadmap announcement directed builders away from competing clients and toward data products and vertical applications.
The newly mandatory developer terms turn that direction into an ecosystem boundary. Critics characterize the shift as Twitter bulldozing parts of the app ecosystem, making policy stability a central issue for developers such as Twidroyd and UberTwitter.
First-order effects
- Twidroyd, UberTwitter and other pure-play client developers must align their products with Twitter's new terms rather than treat the API as a basis for competing access apps.
- Twitter gains stronger control over the user experience delivered through its service and can steer developer effort toward data and vertical products.
Second-order effects
- Developers seeking to remain in Twitter's ecosystem are pushed to differentiate through specialized workflows or data uses instead of the core client interface.
- Twitter's native iPhone app gains protection from direct third-party client competition, shifting the competitive contest from interface design toward permitted complementary services.
Third-order effects
- The move points to an access-layer model in which a platform can use developer terms to reserve the most strategic user interface for itself while outsourcing narrower innovation.
- If other platforms adopt similar boundaries, API-dependent companies will face greater pressure to build businesses that complement, rather than replicate, a platform's core product.
The trend: Major consumer platforms are tightening control of their primary access layers while redirecting outside developers toward complementary niches.