I finally found time to view the video of Google Wave at the Google I/O 2009 developers’ conference. It’s nearly an hour and a half, so I’m starting this after about a third of it … If you’re in the collaboration business as a user, provider, or advisor, go watch it!
How many times have you tried to persuade colleagues that discussions should happen in the collaboration database, not via email? So we don’t have messages clogging the system. So the discussion doesn’t diverge into multiple threads. So newcomers can catch up without someone having to send back copies of everything that’s gone one. Well, Wave starts by disposing of that problem. Because “a Wave” is a single threaded collection in one place, and it can look like email, or a collaboratively co-authored document, or a discussion, or any combination. And there’s replay, so even if you come late to a conversation you can see how it got to where it is – if it matters. And it can look like instant messaging too, if you and your colleague(s) are both online to Wave at the same time.
Lots of smart integration stuff. Embed your Wave in a blog – then updates can happen from the Wave client, or the blog page, or anywhere else it happens to be visible, and all manifestations update in real time. There’s only one copy – remember? Add pictures. And because Wave takes advantage of today’s network capabilities, edits can show up on everyone’s screens at once. Even concurrent edits. Even if they are backtracking stuff that was “sent” previously: no more sending emails to correct the correction you sent to the original incorrect email. Interactive meetings, anyone? On a mobile? It’s all there.
For the heavily technical: Wave relies on HTML 5 and, for one element which the new standard can’t handle, a little of Gears. Google are pressing for this element to become part of the standard. For the object oriented among you: it screams Model-View-Controller out of every simultaneous update!
It’s been two years in the making, and this is only a preview (it will make it into the traditional Google Beta, i.e. release, later this year). Why now? For the same reason that Wave will be open sourced: Google wants to fire the imagination of smart developers, and harness them not just to build more smart apps in Wave but to improve the underlying platform too.
Even if you never adopt the tool itself, when it goes public later on, the ideas and the understanding about how collaboration works are an education in themselves. Email is decades old, so are bulletin boards. Why should we still work like that? Oh – and Wave can do translation in real time. As you type.
• HTML 5, W3C development (this is currently the Editor’s Draft 23 June 2009)
• Went Walkabout. Brought back Google Wave Google Blog, 28 May 2009
• Google Wave home page: the video is embedded here, plus news and the chance to sign up when the release comes along