You may have heard the name “Google Wave” thrown around recently in tech news. Google Wave is Google’s hot new product, still in development and testing via an invitation, much like how Gmail started out. But what is Google Wave? Well, let’s start there.
What Is Google Wave?
When I was trying to think of my own definition of what Google Wave can do, I ended up with “real-time, extensible communication and collaboration.” When I looked up Google’s own definition, it turned out I wasn’t far off:
Google Wave is an online tool for real-time communication and collaboration. A wave can be both a conversation and a document where people can discuss and work together using richly formatted text, photos, videos, maps, and more.
At it’s very most basic, Google Wave can be thought of as real-time email, or really fancy instant messaging. But it’s really much more than that. Let’s define a key term or two, and then break down the definition.
Waves, Wavelets, and Blips
In Google Wave, the first unit of organization you will encounter is called a wave. A wave can be thought of as a forum topic, or a series of emails pertaining to a single topic.

Each Wave can contain wavelets, or sub-waves that have branched off the main wave, and blips, single units of communication within a wave or wavelet. When you create a wave, you can invite other people to participate in it. You can also invite individuals to wavelets, effectively giving them permission to access a certain part of a wave.
Let’s continue by breaking down the pieces of Google Wave’s abilities.
Real-Time Communication
Google Wave can be used to simply communicate with other people. If I start a wave and invite you to it, you can reply to my original blip with your own blip; I can then reply to that blip with my own. Used this way, Google Wave very much resembles email, with a few key differences.
First, communication is real time, meaning not only do I not have to press “send” or some other similar button when I am finished, but in fact, other users of a wave can see me type in real-time (unless I disallow it), allowing a more “instant message” feel to communication if so desired. Of course, the participants are welcome to come back at their leisure and respond whenever they wish.

via Wave: Google’s take on the future of communication
Secondly, participation is collective. For example, let’s imagine I have started a wave and invited my friend, Jonathan, to it. Jonathan and I have a back-and-forth about a particular issue at the office. Several blips into the conversation, we decide Jeff would be a good resource to consult. We add Jeff to the wave, and immediately Jeff has access to the entire conversation, including a “playback” feature that lets him see the blips as they were added and modified (in case the wave has branched into wavelets or edits have been made to blips).

Real-Time Collaboration
Blips in a wave are, by default, shared by any member of the wave. This means that any user that is a participant of a wave can edit any blip in the wave, effectively allowing for real-time collaboration between multiple individuals by editing the same blip at the same time. Any number of participants can edit the wave concurrently—imagine a meeting of 10 members of your department, each of them making changes to a shared wave.
But Wave’s true power comes in the final piece of the definition: extensibility.
Extensible
Google Wave is extensible in a couple of ways. The first is the notion of robots. Robots are automated users, for all intents and purposes. They are added to a wave the same way other people are, and they are programmed to carry out specific tasks. Some robots translate between languages on the fly; some robots perform other types of lookups or cross-platform postings of wave data, such as posting a wave’s data to Twitter or a blog.

Gadgets are another way to extend Google Wave. Gadgets are inserted into a specific place in a blip and provide extra functionality. This could be as simple as showing a URL in an iFrame or as complex as collaborative source code editing and highlighting, and even online games.

Looking To the Future
The future of Google Wave looks bright. Even in its current half-finished implementation, it is a powerful tool. As it becomes easier to create and install gadgets and people become more accustomed to using Wave, it has the capability to be an integral part of daily workflows. Furthermore, a protocol for Google Wave is being developed, allowing different providers to communicate with each other (much as how different companies host their own email at their domain). If you get an opportunity to try out Google Wave, I recommend you take the time to play with it and really see what it can do; also, if you have the time, the Google IO demo of Google Wave is also very interesting!
#1 by Matthew Morgan - October 30th, 2009 at 12:29
I can see where this would be awesome, but I think I’d feel better about something this intimate if I could load it on my own server and run it from there.
When I was reading this, though, I couldn’t help but think this could add a whole new dimension to pair programming. ;)
#2 by Brandon Tilley - November 1st, 2009 at 10:09
Eventually you’ll be able to. Similar to email, you’ll be able to run you’re own Wave server (that is why Wave usernames uses the traditional user@domain pattern), and using the Wave protocol, the different servers will be able to communicate with each other.
#3 by Gec - November 1st, 2009 at 11:49
Aye mate, your own server or their’s, there is no “intimacy” on the internet. They see everything. Now they want us to wear chips, supposedly for our own protection.
You’re right about the programming part though, it’s the next new thing.
Cheers!
#4 by Matthew Morgan - November 3rd, 2009 at 05:32
Well, Gec, that’s really one of the reasons for my comment. If you can run it on your own server, it doesn’t have to be on the internet at all. If it is being used to exchange sensitive information, it can be on a completely separate network with no internet connectivity.
I was just joking about the pair programming thing. I don’t think I know anyone who could prevent their head exploding if they were editing a source code file and simultaneously seeing someone else edit the same code.
#5 by Gec - November 29th, 2009 at 03:12
They say you’ll eventually be able to run on your own server so you’ll be able to have some “privacy”. But.
BUT… they CAN see you from their satellites, and soon enough they’ll have the technology (chances are, they already have it) to actually see what you are typing, with infrared satellite cameras and whatnot.
When we’ll have the chips, it will just get _easier_.
Cheers! ;)