Twitter CEO touts building ‘true platform,’ ignores developers' anger
Appearing on “Charlie Rose,” Dick Costolo said Twitter is focusing on a broad ecosystem, but chalked API access limits up to its broad vision, sidestepping developers' ire at being cut out.
Context & Ripple Effects
Dick Costolo's 'true platform' framing on Charlie Rose is the latest step in a line the CEO has been walking since 2011, when he told developers to move up the value chain rather than compete with Twitter directly — and when the company explained why it didn't want anyone building new third-party clients. The interview lands one day after confirmed API policy changes forced services like IFTTT to strip out their Twitter integrations, so the 'broad ecosystem' language is being delivered into a developer community already cut off.
The timing matters because it caps a bruising week for Twitter's consumer-facing image: an iPad app update drew user backlash and a new profile-page design was unveiled on NBC's Today Show, all while a rumored tweet-download feature was floated for year-end. Costolo is pitching vision to a general audience while the people who extended Twitter through its API are being told, implicitly, that they are not part of it.
First-order effects
- Developers whose products depend on Twitter data — IFTTT among them, per the confirmed integration removals — lose working features immediately under the new API limits, with no roadmap from Costolo's interview suggesting relief.
- Twitter consolidates control of its own surface area: clients, cards, and profile experiences now flow from the company itself, making the ecosystem Costolo describes one that runs on Twitter's terms rather than alongside it.
Second-order effects
- Third-party developers face a credibility problem with their own users and must either rebuild around what limited access remains or shift effort to platforms with more open APIs, thinning the tool layer that made Twitter more useful than its official apps.
- Rival networks gain a recruiting argument: every constrained integration is a case study they can cite when courting the same developers, turning Twitter's API policy into competitors' pitch material.
Third-order effects
- If the pattern holds, mature consumer platforms treat open APIs as a subsidy paid only during growth phases and withdrawn at scale — making developer trust a structural dependency that platforms can spend down, as Twitter has been doing since its 2011 warnings to builders.
- The episode hardens a governance question the industry keeps deferring: whether platform access should be contractual and predictable rather than revocable at the owner's discretion, since developers have no recourse when the rules change overnight.
The trend: Consumer platforms that grew on developer goodwill are systematically reclaiming their APIs as they mature, trading ecosystem breadth for product control.