Twitter lets users switch back to the previous version of TweetDeck, and appears to have restored legacy API access allowing some third-party apps to work again
Overnight, users across Twitter began reporting that the older, and much better, version of TweetDeck has returned along …
Context & Ripple Effects
Five days earlier, Twitter employees said removing support for legacy APIs was what broke TweetDeck, and the company had simultaneously told users they'd need Twitter Blue to keep using TweetDeck within 30 days — part of a forced migration to the revamped version previewed back in 2021. Overnight, both moves appear reversed: users can switch back to the older client, and legacy API access seems restored, letting some third-party apps work again.
The reversal matters because TweetDeck's power-user base and the third-party developer ecosystem were collateral damage of the same access decision — one switch at the API layer took out both, and one switch brought them back.
First-order effects
- Power users who rely on multi-column workflows regain the older TweetDeck immediately, without paying for Blue or adopting the new version's feature set (full composer, Spaces, polls).
- Third-party apps whose functionality broke when legacy API support was pulled can operate again for as long as the restored access lasts.
Second-order effects
- The 30-day Blue paywall deadline loses its enforcement mechanism — if legacy clients still work, Twitter's conversion funnel into paid subscriptions weakens, pressuring the company to re-cut off access or formalize grandfathering.
- Third-party developers face renewed planning risk: their apps now depend on undocumented legacy access Twitter has already revoked once this month, making v2-API investment (the default since late 2021) the only durable path.
Third-order effects
- If flip-flops become the norm, Twitter's API becomes a lever the owner pulls ad hoc rather than a contract developers build against — echoing earlier retrenchments like killing the standalone Windows app in 2016, and shifting the ecosystem toward whoever controls the access layer rather than whoever builds on it.
The trend: Platform API access is being wielded as an instrument of monetization and control, with reversibility itself becoming the defining risk for anyone building on top of it.