Former product head of Twitter's developer platform details the plans, like custom timelines, that Twitter abandoned post-acquisition, eroding developer trust
Twitter is where the world shares its opinions and aspirations; it's where brands, celebrities, and politicians interact with people, live and in the open.
Context & Ripple Effects
This retrospective closes an arc that began with Twitter's 2017 attempt to reset developer relations around a streamlined, tiered API, followed by Developer Labs in 2019, which promised rebuilt APIs and nudged developers toward paid plans. In between came the 2018 end of legacy API support that killed third-party apps like Tweetbot.
The new detail — that custom timelines and other roadmap items were shelved after the acquisition — reframes those earlier moves not as strategy shifts but as broken commitments, and gives weight to ex-exec Amir Shevat's estimate that roughly 17% of historical engagement ran through third-party apps built by teams like Tapbots.
First-order effects
- Developers who invested against the published roadmap — including client makers like Tapbots — get confirmation that planned features such as custom timelines were abandoned internally, validating their decision to stop building for Twitter.
- Twitter itself forfeits the engagement those third-party surfaces carried, since the ~17% share attributed to them has no first-party replacement for most of it.
Second-order effects
- Independent client developers redirect their effort to platforms whose APIs they can trust, taking niche tooling and audience experiments with them.
- Twitter's paid-API pitch loses credibility: after the legacy shutdown and now the revealed abandonment of roadmap promises, each new tiered offering starts from a deeper trust deficit.
Third-order effects
- If the pattern holds, social platforms consolidate around first-party clients and tightly rationed data access, with developer ecosystems surviving only where API commitments are contractually or reputationally enforceable.
- Trust becomes the scarce input in platform strategy: a track record of honoring developer-facing roadmaps turns into a competitive asset that laggards cannot buy back quickly.
The trend: Social platforms are retreating from open developer ecosystems toward first-party control, and repeated API reversals are converting developer trust into a durable competitive moat for whoever keeps their commitments.