Embrace, extend, extinguish: How Google crushed and abandoned the RSS industry
Summary: Most of the commentary I've read so far about the loss of Google Reader has been about its use as an RSS client. But that's a red herring. The real victims were companies that had planned in 2005 and 2006 to build RSS sync engines.
Context & Ripple Effects
The 2009 account of a declining RSS reader market had already framed the category as fragile. The Reader shutdown matters beyond one client because the article identifies RSS synchronization businesses conceived in 2005 and 2006 as the deeper casualties of Google’s earlier role in the market.
First-order effects
- Google Reader users lose Google’s RSS client, while companies whose synchronization plans had been shaped by Reader’s market presence lose a key foundation for those plans.
Second-order effects
- RSS client makers and sync-service providers must compete for users without Google Reader as the default hub, making reliable synchronization a product responsibility rather than an assumed platform layer.
Third-order effects
- The episode highlights the dependency risk in markets built around a dominant company’s free infrastructure: a product exit can reshape adjacent businesses even when the underlying RSS standard remains available.
The trend: RSS is becoming a test case for how open standards can still be commercially shaped by the rise and withdrawal of a dominant platform’s service layer.