Since last Thursday I have picked up snippets of buzz around Google Wave and finished watching the demo video today (had kept it for my workout to have that pass more quickly 😉 ). I am just speechless and can’t wait for it to be publically available.
Wave is a new communication tool that is email, instant messenger, microblog, blog, collaborative writing tool, and some more all in one. It redefines the way online communication is done because you do not have to think about whether you want to write an email, send a Twitter message or start a chat. You just do it all in Wave.
The Wave team from Australia demonstrated so many features and extensions of Wave that your head spins (not in a particular order):
- instant messenger
- embed waves into a blog
- drag and drop photos and links
- embed videos
- instant translator (I think that one got the biggest applause)
- add people to an ongoing conversation
- connect waves
- inline commenting
- collaborative gaming
- linking other services, e.g. Twitter, bug tracker, and be able to either update from within Wave or these other services
- federation: communication between different Wave installations
- playback of the development of a Wave conversation
I think the only things that are missing are audio and video chat. I could imagine audio comments to show up like text comments or have an audio conversation be recorded while working on a document.
Now, how can some of these features be used for learning and for research? The one point that jumps to mind instantly is the possibility of collaborative writing (including using visual media). You see instantly what the others type and do not have to wait until changes are committed. That is similar to EtherPad. You can add comments to a document which can be hidden or displayed which is easier to detect them and to deal with them than in Google Docs where you write them inline with the text. Parts of a current wave can be opened as a new wave to branch conversations.
When you want to research the flow of communication, for example how people interact when writing collaboratively on a document, all you have to do is hit “playback” and the wave unfolds in front of your eyes. I already liked the “playback” feature when I discovered it in the concept mapping software CmapTools. Even though I have not used it yet beyond testing purposes, it has a ton of potential if you are involved in that kind of research because you do not need an additional program to record what has been done, but you can have all actions recorded automatically.
Another great thing about Wave is that it can run on any server and does not have to sit on a Google server. The GUI is also changeable. This is great news because Google is often accused of listening in on conversations, using it all to their own benefit. When the Wave runs on a server different from the Google one, there is no information exchange. However, Wave communications can take place across different servers so that Wave users do not necessarily have to create accounts on all Waves. They then form a federation. According to the developers, only the content that is meant for the Wave users across the systems will be sent to the federation Waves. If a private comment is made between two users of one Wave, the other server does not see that comment at all. That makes Wave attractive to companies, institutions etc. that want to use it, but do not want to put their communication and documents out there on a Google server for confidentiality reasons.
The demo made it all look so simple, but the Wave team spent two years on getting this far and they have pooled resources from other Google programming teams. Google opened the code and invited programmers to get busy on extensions and gadgets for Google Wave to make it more powerful even before the official launch. Let’s see when the Wave will hit our keyboards.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.