Lars Rasmussen stood on stage at the Moscone Center in San Francisco on 28 May 2009 and spent roughly 80 minutes showing a room of developers a product called Google Wave, and when he finished, thousands of people stood up and clapped.
The demo had everything: real-time character-by-character typing visible to other participants, drag-and-drop photo sharing, embedded maps, conversation playback that let you scrub through the history of a thread like a video, and a robot called Rosy that auto-translated French into English as a user typed.
Fifteen months later, on 4 August 2010, Google announced it was shutting the whole thing down. The product had failed to find users who could explain it to other users.
The demo is still on YouTube. It remains one of the widely-watched product unveilings in Google’s history and one of the strangest case studies in modern tech.
What the room actually saw
Lars Rasmussen and his brother Jens had built Google Maps after Google acquired their Sydney startup Where 2 Technologies in 2004. By 2009 they had been working for years on reimagining email for the modern era. The pitch was that email, instant messaging, document collaboration, and wikis were all really the same thing pretending to be different things, and a single tool could absorb all of them.
The unit of Wave was a “wave,” which behaved like an email thread, a chat window, and a shared document at once. Anyone added to the wave could edit any part of it. Edits appeared character by character in real time. A playback bar let new participants replay the conversation from the start. Bots could be invited into a wave to translate, spell-check, or pull in data from outside services. Embedded gadgets let people vote, share a Google Map, or play a game inside the thread.
Developers in the audience clapped because they understood, technically, what they were looking at. The federation protocol underneath Wave was open. Anyone could run their own Wave server. The data model was novel. The engineering was genuinely impressive. The standing ovation was for the craft.
The problem nobody named on stage
At no point during the demo did anyone explain, in one sentence, what a normal person would use Wave for.
The closest the presentation came was the framing question itself: what would email look like if invented today?
But that is a designer’s question, not a user’s. A user does not wake up wanting a reinvented inbox. A user wants to ask a colleague when the meeting is, or send a photo to a parent, or agree on a restaurant with three friends.
Wave could do all of those things. So could email, SMS, Facebook, Google Docs, and Skype, and the people who needed to do those things already had habits built around the existing tools. Wave required them to abandon the habit, persuade everyone they wanted to talk to also to abandon the habit, and then learn a new interface that combined four interaction models at once.
The standing ovation was a kind of trap. The developers in the room were exactly the wrong audience for predicting consumer adoption. They were primed to be impressed by technical novelty, surrounded by other people being impressed, and operating in what psychologists call the false consensus effect, the tendency to assume other people share the reactions of the group you are currently sitting in. The applause sounded like proof of market fit. It was proof of room fit.
The invitation era
Google did not open Wave to the public after the demo. Instead, on 30 September 2009, it sent out invitations, each of which carried a handful of additional invites the recipient could pass on. The scarcity was meant to replicate the Gmail launch of 2004, which had turned beta invites into a status symbol and seeded the product through tech-savvy early adopters.
The Gmail playbook did not transfer. Gmail solved a problem everyone already had: small mailboxes, slow webmail, no search. A Gmail invite was a ticket to a faster version of something the recipient already used every day. A Wave invite was a ticket to a product the recipient had to figure out from scratch, and then convince other people to also figure out from scratch, because Wave was useless if the people you wanted to talk to were not also on Wave.
Early users logged in, looked at the empty interface, did not know who to invite, did not know what to write, and closed the tab. A common complaint in the press at the time was that Wave felt like walking into a party where the rules of conversation had been changed without warning.
The interface that did too much
The default Wave screen had four panels. The leftmost showed navigation. The next showed an inbox of waves. The next showed the contents of the selected wave. The rightmost showed contacts and gadgets. Inside a single wave, replies could be nested inline at any point in any message, so a long thread looked less like a conversation and more like a document that had been annotated by a committee in different coloured pens.
The real-time typing feature, which had drawn one of the loudest cheers at I/O, turned out to be uncomfortable in daily use. Watching someone else compose a sentence letter by letter, including their backspaces and rewrites, felt invasive. Most users wanted the polished version of a thought, not its keystroke-level construction. The feature that had defined the demo became the feature people most often asked to turn off.
Playback, the other showpiece, had a similar fate. In theory, dropping a new person into a long wave and letting them scrub through its history was elegant. In practice, the history of a collaborative document tends to be a mess of false starts, deletions, and reorderings that is harder to follow than a clean summary written by a human.
The shutdown
On 4 August 2010, Urs Hölzle, Google’s senior vice president of operations, wrote a short blog post announcing that Wave had failed to gain sufficient user adoption and that the company would stop developing it as a standalone product. The team would be moved to other projects. The code would eventually be donated to the Apache Software Foundation, where it lived on for several years as Apache Wave before being retired.
Fifteen months had elapsed between the standing ovation and the shutdown announcement. In that time, Wave had attracted significant initial interest but failed to retain sustained users. The internal metric that mattered, daily active conversations between non-Google employees, never reached a level that justified the engineering cost.
Lars Rasmussen left Google for Facebook later in 2010. In interviews afterwards, he was candid that the team had underestimated how hard it would be to explain the product, and that the federation and open-protocol ambitions had absorbed engineering effort that might have been better spent on a simpler core experience.
What survived
Wave did not vanish without trace. The real-time collaborative editing engine that powered it, including the operational transformation algorithms used to merge simultaneous edits, became foundational to Google Docs, which by the mid-2010s was the default collaborative writing tool for hundreds of millions of people. The multi-user cursors that now feel ordinary in Docs, Figma, Notion, and dozens of other products trace a direct lineage to the Wave demo.
Threaded inline replies, embedded bots, and gadgets in chat all reappeared in later products. Slack, launched in 2013, took the chat-as-shared-workspace idea and stripped it back to something a team could understand in five minutes. Microsoft Teams followed. Notion took the idea that documents could simultaneously function as databases and conversation spaces and made it legible by hiding most of the power behind clean defaults. The ideas in Wave were not wrong. The packaging was.
The lesson the demo encoded
The standing ovation at Moscone is a useful artefact because it shows what room-level applause can and cannot tell a company. The developers clapping in 2009 were responding honestly to a piece of engineering they admired. They were not, and could not have been, a representative sample of the people who would have to adopt the product for it to succeed. The room contained almost nobody who would later try to explain Wave to a parent, a small business owner, a teacher, or a friend who just wanted to send a photo.
Google has spent the years since trying not to repeat the mistake, with mixed results. Google+ launched in 2011 with a clearer pitch and still failed. Inbox by Gmail launched in 2014 with strong reviews and was shut down in 2019. The company has shipped and killed enough products that the website killedbygoogle.com tracks more than 290 of them. The most recent additions to the catalogue arrive alongside aggressive AI pushes, including a December 2025 relaunch of Gemini Deep Research built on Gemini 3 Pro, a product whose long-term fate will depend on the same question Wave failed to answer: can a normal person, in one sentence, say what it is for.
The video is still on YouTube. Watch the moment around the 78-minute mark when Rasmussen finishes his closing line and the camera pans across the auditorium. The clapping goes on for a long time. Most of the people in that shot would never use the product they were applauding. A handful of them would go on to build the tools that did the same job, more quietly, a few years later, by saying out loud what Wave was for and then doing only that.
