Google Wave

Google Wave
source
Name	Google Wave
Developer	Google
Released	2009 (preview)
Discontinued	2010 (server shutdown 2012)
Programming language	JavaScript, Java
Platform	Web, browser
License	Proprietary (original), Apache License 2.0 (continuation)

Google Wave was a real-time collaboration and communication platform introduced by Google in 2009 as a blend of email-style messaging and collaborative document editing. Designed by engineers from Google's Gmail and Google Docs teams and unveiled at a keynote that featured Bret Taylor, the project sought to combine aspects of WYSIWYG editors, IRC, and wiki-style history into a single web application. The prototype drew attention from technologists at O'Reilly Media, TechCrunch, and attendees of the Google I/O conference but faced adoption challenges that led to strategic shifts by Google's product leadership.

History

Google announced the project during Google I/O 2009, where product managers and engineers showcased synchronous editing and playback features to an audience including staff from YouTube, Blogger (service), and representatives of open-source communities such as the Apache Software Foundation. Early development incorporated work from contributors with prior experience at Sun Microsystems and Palm, Inc. and leveraged web standards promoted by the World Wide Web Consortium. The project ran as an invitation-only preview with waves hosted on Google's infrastructure; it generated discussion among journalists at Wired (magazine), analysts at Gartner, and developers posting on Stack Overflow. Despite excitement, executives from Google announced in 2010 that active development would be reduced, and in 2012 the public service was suspended, prompting responses from stakeholders including the Free Software Foundation and members of the open source community.

Features and technology

The platform featured a live, character-by-character collaboration model inspired by earlier systems like Collaborative real-time editor prototypes and research projects from Xerox PARC. It combined elements of threaded conversations seen in Usenet and Slashdot, inline multimedia from YouTube and Picasa, and revision history similar to facilities in Wikipedia and Subversion (software). The client used advanced JavaScript techniques and leveraged the Google Web Toolkit alongside server components written in Java (programming language), running on the same infrastructure that supported Gmail and Google Docs. Extensibility was provided via a bot and gadget API that invited integrations with services like Twitter, Dropbox (company), and third-party authentication from OpenID. Security and identity models referenced concepts from OAuth and discussions among engineers with ties to Mozilla Foundation and enterprise architects at Salesforce.

Reception and criticism

Initial reception combined praise from commentators at The New York Times, The Guardian, and Financial Times for innovative interface concepts, while analysts at Forrester Research and bloggers at TechCrunch questioned practical use cases relative to established tools like Microsoft Office and Slack (software). Critics highlighted cognitive overload concerns raised by researchers at MIT Media Lab and usability issues noted by experts from Nielsen Norman Group, citing the simultaneous-editing model and evolving conventions compared to protocols like SMTP and platforms such as Facebook. Privacy advocates at the Electronic Frontier Foundation and legal scholars linked to Stanford Law School debated data portability and retention policies, and enterprise customers familiar with offerings from IBM and Oracle Corporation expressed caution about migration and compliance. The developer community on GitHub and poster networks such as Stack Overflow produced both integrations and critiques, while venture capital observers at Sequoia Capital and Andreessen Horowitz tracked user adoption metrics.

Shutdown and legacy

After reduced development focus in 2010 and a formal announcement, Google transitioned the effort toward open-source contributions and maintained limited access before terminating the hosted service in 2012; operations teams coordinated with partners at the Apache Software Foundation during the transfer. The closure prompted commentary in outlets such as Bloomberg (news) and prompted comparisons to other discontinued services like Google Reader and Wave of public concern-style debates around product lifecycle at Google. Former product leads and engineers moved to other projects within Google and to startups in the Silicon Valley ecosystem, influencing collaborative features later seen in Google Docs and real-time capabilities in platforms such as Microsoft Office 365 and Slack (software).

Open-source continuation (Apache Wave)

Following the shutdown, the codebase and protocols inspired an open-source initiative accepted by the Apache Software Foundation as a sandbox project and later incubated as Apache Wave (incubation status), attracting contributors from the Eclipse Foundation, independent developers on GitHub, and researchers at institutions like Carnegie Mellon University. The Apache incarnation focused on protocol standardization, federation, and interoperability with messaging systems including XMPP and attempted integrations with tools deployed by organizations such as Red Hat and Canonical (company). Although Apache Wave did not achieve mainstream deployment comparable to Email or HTTP, its artifacts influenced real-time collaboration research in academia and informed engineering decisions at companies like Dropbox (company), Atlassian, and Microsoft Corporation.

Category:Discontinued Google services