Trying out Google Wave

Google-Wave-logoThanks to an invite from Garrett I gave Google Wave a spin today. There definitely is a lot of demand for something like Wave. Today my number one workflow and productivity app is email. I spend about 2 hours on it per day (according to RescueTime) and this doesn’t even count usage of it on the iPhone. Given how central it is for my productivity, it is pathetic how little it has improved over the past decade. Other than better embedding of media (images, PDF) and more reliable IMAP synchronization there really isn’t much of a difference between my mail client today and what I was using in 1999.

There are a number of alternatives to email for collaboration and communication, but none of them quite work yet. IM is real-time (good) but functionality is very limited (it lacks open APIs, no forwarding or other routing, no rich media). The social networks have built-in messaging, but the user interface is terrible. Wiki’s and Google Docs are great for collaboration, but have no messaging component.

Given all this, it’s great to see that a team at Google is trying a different approach. Google Wave is essentially a closed messaging system that structures messages around threads (aka conversations). Messages are updated in real time (i.e. you see people type), thus it also has many of the qualities of IM but also of the collaborative qualities of Google Docs or a Wiki. Conversations can easily be embedded in web pages, although I did not try this out. Finally it uses a number of clever ways to mark up and display messages in a more structured way. Overall it is a good user experience, although it still feels a little alpha.

The first thing to notice is the lack of integration. While it copies a lot of the functionality of other services, it doesn’t allow you to leverage existing ones. How do I migrate my existing social network and contact data into Wave, how do I integrate devices that are not web based (e.g. mobile devices) and users that want to use existing clients? While Google Wave gives you an email address <> emails sent to it don’t show up in your inbox when I tried.

The second issue I see with Wave is the UI. Seeing people type in real time is great unless you want to get work done. I usually read about 200 emails in 75 threads and write somewhere around 50. The goal of a good UI is to hide things which are not currently relevant. Showing me someone is typing before he has finished his message is usually counterproductive. Google Wave also isn’t quite as responsive as GMail or let alone a local client. And speed really matters. At 200 emails a day, needing 3 seconds longer for each means an hour less productivity a week.

For me, the main conclusion is that Wave does not replace email. In fact, I think it doesn’t even try to. With some additional polish, Wave has the potential to be a powerful tool for groups to collaborate internally on projects and documents. Essentially a Google Docs with built in Workflow. But for external communication one would need a tool that offers better integration with other platforms and a UI that is written with the goal of getting things done.

Comments (5)

  1. William

    You touch here on the real strength of email — that you don’t have to respond to it until you’re ready. IM is too much like the phone for me. On the rare occasion that something is real-time, IM is useful. Most of the time it’s a concentration breaker. Wave seems nice for real-time, but right now the sense I get is that people are trying to claw time back from their apps, and I’m not sure how well Wave fits in to that.

  2. Rob Adams

    The one thing that I really like compared to email would be the ability to unsubscribe from a wave once it’s no longer relevant to you. At Webroot, we have these email threads where the number of recipients keeps growing and everyone keeps hitting reply to all, and there’s no way to escape once you’ve been sucked in.

  3. Mad Max

    If I see my colleagues at work using (outdated versions of ?) Eudora, or the impossible webmail interface of the company (every other time you use it, you loose the message you’re composing… I don’t want it to happen it a third time to me…), I do feel some progress in email interfaces, and I wonder how enterprises can tolerate the productivity loss resulting from such obsolete equipment…

  4. Guido Appenzeller

    @William: Yeah, good user interface design is about showing the bare essential that you need to know, and hide everything that is not relevant. I can see that you sometimes want to transition a “batch” conversation (e.g. email) into a real-time one. But you need some type of control to do that.

    @Rob: Yeah, we have all seen these. Unsubscribing from a thread would be a killer feature.

    @Max: GMail is very popular and definitely not a bad choice. I do like the offline capability and faster response time of clients though. My current setup is Apple Mail with two plug-ins (Act On and Letterbox). It’s low on features but very, very fast.

  5. Guido Appenzeller

    And apologies to Garrett for mis-abbreviating his name! Fixed now.


Leave a Comment

Your email address will not be published. Required fields are marked *