Lockdown
Officially, Google killed Reader because “over the years usage has declined”.1 I believe that statement, especially if API clients weren't considered “usage”, but I don't believe that's the entire reason. — The most common assumption I've seen others cite is that …
Context & Ripple Effects
Google’s explanation of declining use follows a longer unsettled RSS market: a 2009 account described the sector as weakening, while Google said Reader was doing just fine in 2010. A March 2013 report also tied the service’s end to privacy and compliance concerns, giving the closure a broader operational context than audience size alone.
The immediate issue is not merely the loss of a reader interface. Reader’s API had supported third-party clients, against the backdrop of Google’s scheduled API shutdowns in 2011, making the decision a test of how much continuity developers can expect from Google-hosted services.
First-order effects
- Google Reader users and third-party clients built on its API must move saved feeds, reading workflows, and integrations to another service or lose access to them.
- Google eliminates the operating and compliance burden associated with Reader, while its stated usage rationale leaves API-dependent activity outside a clearly defined measure.
Second-order effects
- RSS providers competing for Reader’s displaced users must handle migration and recreate the synchronization features that made a shared Google backend valuable.
- Developers using Google APIs have a stronger incentive to limit dependence on a single Google service, particularly where an API does not carry a durable product commitment.
Third-order effects
- If platform operators continue retiring low-priority services and interfaces, feed readers and other personal data tools will compete on exportability and migration support rather than on a single hosted backend.
- The closure points toward a wider SDK-governance gap: API access can enable an ecosystem without assuring that the underlying product will remain available.
The trend: Consumer web platforms are consolidating around services with clearer strategic and operational value, shifting migration risk onto users and API-dependent developers.