Update on Google Wave
We have always pursued innovative projects because we want to drive breakthroughs in computer science that dramatically improve our users' lives. Last year at Google I/O, when we launched our developer preview of Google Wave, a web app for real time communication and collaboration …
Context & Ripple Effects
Google Wave went from the most-hyped launch of 2009 to a discontinued product in roughly fifteen months. The developer preview unveiled at last year's Google I/O was pitched as a new communication platform for a new web, and early coverage ranged from breathless demos to a CNET reality check questioning whether anyone would actually adopt it. By late 2009 Wave was still invitation-gated enough that running it on the iPhone counted as news in itself (TechCrunch's October 2009 writeup of the workaround).
The shutdown lands as an admission that adoption never escaped that hype bubble — and the syndication pattern is telling: Silicon Alley Insider framed it as proof Google deserves credit for killing projects that don't work, while TechCrunch and CNET treated the death itself as the story, with Eric Schmidt fielding questions on the demise.
First-order effects
- Users and developers who built on Wave's APIs lose the platform Google billed as email-and-instant-messaging's successor, with no successor product named in the announcement.
- Google absorbs the reputational cost of its highest-profile failure since launching the developer preview at I/O in May 2009 — the gap between demo-stage ambition and shipped adoption is now public record.
Second-order effects
- Rival collaboration vendors get the clearest possible sales pitch: Google's own flagship bet on real-time collaborative editing failed commercially, giving incumbents ammunition against 'the next Wave' pitches.
- Inside Google, the kill-fast precedent set here — praised explicitly by Silicon Alley Insider's framing — makes future experimental launches harder to take seriously without a path to mainstream adoption.
Third-order effects
- If the pattern holds, big-platform innovation budgets shift toward absorbing successful experiments into existing products rather than shipping standalone successors to entrenched categories like email — and the open-sourcing-or-orphaning of ambitious protocols becomes a recurring question for any platform vendor.
- Wave's fate becomes the reference case for the adoption gap between developer-preview enthusiasm and mainstream behavior, one every subsequent real-time collaboration effort gets measured against.
The trend: Large platforms are shortening their tolerance for low-adoption moonshots, killing ambitious communication products within months rather than letting them linger — and pricing that speed of execution as a virtue.