Google Wave

Features

Google Wave was a new Internet communications platform. It was written in Java using OpenJDK and its web interface used the Google Web Toolkit. Google Wave worked like previous messaging systems such as email and Usenet, but instead of sending a message along with its entire thread of previous messages, or requiring all responses to be stored in each user's inbox for context, message documents (referred to as waves) that contain complete threads of multimedia messages (blips) were perpetually stored on a central server. Waves were shared with collaborators who could be added or removed from the wave at any point during a wave's existence.

Waves, described by Google as "equal parts conversation and document", were hosted XML documents that allowed seamless and low latency concurrent modifications. Any participant of a wave could reply anywhere within the message, edit any part of the wave, and add participants at any point in the process. Each edit/reply was a blip and users can reply to individual blips within waves. Recipients were notified of changes/replies in all waves in which they were active and, upon opening a wave, could review those changes in chronological order. In addition, waves were live. All replies/edits were visible in real-time, letter-by-letter, as they were typed by the other collaborators. Multiple participants could edit a single wave simultaneously in Google Wave. Thus, waves could function not only as e-mails and threaded conversations but also as an instant messaging service when many participants were online at the same time. A wave could repeatedly shift roles between e-mail and instant messaging depending on the number of users editing it concurrently. The ability to show messages as they are typed could be disabled, similar to conventional instant messaging.

The ability to modify a wave at any location let users create collaborative documents, edited in a manner akin to wikis. Waves could easily link to other waves. In many respects, it was a more advanced forum. It could be read and known to exist by only one person, or by two or more and could also be public, available for reading and writing to everyone on the Wave.

The history of each wave was stored within it. Collaborators could use a playback feature to observe the order in which it was edited, blips that were added, and who was responsible for what in the wave. The history could also be searched by a user to view and/or modify specific changes, such as specific kinds of changes or messages from a single user.

Reception

During the initial launch of Google Wave, invitations were widely sought by users and were sold on auction sites. Those who received invitations and decided to test Google Wave could not communicate with their contacts on their regular email accounts. The initial spread of Wave was very restricted.

Google Wave initially received positive press coverage for its design and potential uses. After its demise, it was criticized for trying to merge "all forms of communication in a single, crowded space".

End of development of Google Wave

On August 4, 2010, Google announced Wave would no longer be developed as a stand-alone product due to a lack of interest. Google's statement surprised many in the industry and user community.

Google later clarified the Wave service would be available until April 2012, giving users the opportunity to use the export functionality to keep a local copy of their waves in PDF format.

Response to the news of the end of development came from Wave users in the form of a website. After their announcement in early August 2010, the website recorded over 49,000 supporter registrations urging Google Wave's continuation.

In retrospect, the lack of success of Google Wave was attributed among other things to its complicated user interface resulting from a product that merged features of email, instant messengers and wikis but ultimately failed to do anything significantly better than the existing solutions.

Chris Dawson of online technology magazine Zdnet discussed inconsistencies in the reasoning of Google in deciding to end support for Wave, mentioning its "deep involvement" in developing social media networks, to which many of Wave's capabilities are ideally suited.

Apache Wave

Google Wave was accepted by the Apache Software Foundation's Incubator program under the project name Apache Wave. The Google Wave Developer blog was updated with news of the change on December 6, 2010. A Wave Proposal page with details on the project's goals was created on the Apache Foundation's Incubator Wiki.

Wave in a Box

Wave in a Box is the current server implementation of Apache Wave. Currently, there are no demo servers available.

Crisis and SwellRT

In 2016, several discussions took place within the Apache Wave community, aiming to tackle the stagnation and crisis state of the project. The Apache Software Foundation mentor of Apache Wave, Upayavira, was concerned by the project's stagnation, but framed SwellRT (a fork which re-engineered Wave into a backend-as-a-service for building apps) as Wave's potential savior. Eventually, Wave was approved to continue within Apache incubator program, and a copy of SwellRT codebase was placed in the Apache Wave repository in order to grant the Wave community access to it. In this regard, Intellectual Property of SwellRT was transferred to the Apache Foundation in 2017. Still this was not sufficient to resurrect Wave's developer community, and SwellRT continued as independent project.

Retirement

The Wave project retired on January 15, 2018, having never left incubator status.

Extension programming interface

Google Wave is extensible through an application programming interface (API). It provides extensions in the form of Gadgets and Robots, and is embeddable by dropping interactive windows into a given wave on external sites, such as blog sites.

The last version of robots API is 2.0.

Google Wave also supports extension installers, which bundle back-end elements (robots and gadgets) and front-end user interface elements into an integrated package. Users may install extensions directly within the Wave client using an extension installer.

Extensions

Google Wave extensions are add-ins that may be installed on Google Wave to enhance its functionality. They may be Internet bots (robots) to automate common tasks, or gadgets to extend or change user interaction features, e.g., posting blips on microblog feeds or providing RSVP recording mechanisms.

Over 150 Google Wave extensions have been developed either in the form of Gadgets or Robots.

Robots

A robot is an automated participant on a wave. It can read the contents of a wave in which it participates, modify its contents, add or remove participants, and create new blips or new waves. Robots perform actions in response to events. For example, a robot might publish the contents of a wave to a public blog site and update the wave with user comments.

Robots may be added as participants to the Wave itself. In theory, a robot can be added anywhere a human participant can be involved.

Gadgets

Gadget extensions are applications that run within the wave, and to which all participants have access. Robots and Gadgets can be used together, but they generally serve different purposes. A gadget is an application users could participate with, many of which are built on Google's OpenSocial platform. A good comparison would be iGoogle gadgets or Facebook applications.

The gadget is triggered based on the user action. They can be best described as applications installed on a mobile phone. For example, a wave might include a sudoku gadget that lets the wave participants compete to see who can solve the puzzle first.

Gadgets may be added to individual waves and all the participants share and interact with the gadget.

Federation protocol

Google Wave provides federation using an extension of Extensible Messaging and Presence Protocol (XMPP), the free Wave Federation Protocol. Being an open protocol, anyone can use it to build a custom Wave system and become a wave provider. The use of an open protocol is intended to parallel the openness and ease of adoption of the e-mail protocol and, like e-mail, allow communication regardless of provider. Google hoped that waves would replace e-mail as the dominant form of Internet communication. In this way, Google intended to be only one of many wave providers and to also be used as a supplement to e-mail, instant messaging, FTP, etc.

A key feature of the protocol is that waves are stored on the service provider's servers instead of being sent between users. Waves are federated; copies of waves and wavelets are distributed by the wave provider of the originating user to the providers of all other participants in a particular wave or wavelet so all participants have immediate access to up-to-date content. The originating wave server is responsible for hosting, processing, and concurrency control of waves. The protocol allows private reply wavelets within parent waves, where other participants have no access or knowledge of them.

Security for the communications is provided via Transport Layer Security authentication, and encrypted connections and waves/wavelets are identified uniquely by a service provider's domain name and ID strings. User-data is not federated, that is, not shared with other wave providers.

Adoption of Wave Protocol and Wave Federation Protocol

Besides Apache Wave itself, there were other open-source variants of servers and clients with different percentage of Wave Federation and Wave Protocol support. Wave was re-engineered into a backend-as-a-service solution by the SwellRT project. Wave was adopted in different forms for corporate applications by Novell for Novell Pulse, or by SAP for Cloudave, and community projects such as PyOfWave or Kune.

Compatible third-party servers

The following servers were compatible with the Google Wave protocol:

• Kune is a free/open source platform for social networking, collaborative work and web publishing, focusing on work groups and organizations rather than in individuals. It provides lists, tasks, documents, galleries, etc., while using waves underneath. It focuses on free culture and social movements needs.
• Novell Vibe, formerly known as Novell Pulse.
• Rizzoma is a platform for collaborative work in real time. It allows communication within a certain context permitting a chat to instantly become a document where topics of a discussion organized into branches of mind-map diagram and minor details are collapsed to avoid distraction. The user is able to sign in using a Google or Facebook account and choose whether your topics are private or public.
• SAP StreamWork is a collaboration decision making service.
• SwellRT is a backend-as-a-service for building collaborative and federated apps. It is a fork which re-engineered Apache Wave, and was adopted within the Apache Wave project.