About a month ago I got access to the early beta of Google Wave. I initially joined with a few friends and we started playing around with it. I then decided to write up a post of the experience.
So a month down the track has my opinion changed? Has the luster worn off? Kind of and yes. My opinion has not changed but my original take was a lot more generous and optimistic. Now that the novelty has faded and I have had the chance to look more critically at it the flaws.
Fundamentally what they are trying to achieve with Wave is admirable. I have not seen this attempted in such a scope before. This reimaging of how we communicate. Before all, digital forms of communication have been direct analogues of its physical counterpart. Instant Messaging is the phone and Email is the snail mail. Wave was a brand new way of doing things, of starting from the basis of technology and building from there.
Well there lies the problem I think. Email and IM work. Sure they have their flaws but the barrier to entry is so low and the use of them is so easy and convenient that changing the norm will be incredibly difficult.
Now to the flaws of Google Wave. It suffers from the old problem of Jack of all trades, master of none. You can use Wave as an IM platform, as an email like client, as a collaboration tool you can even use it as a rudimentary file transfer platform. However all the individual parts are weak and combined together does not improve it.
Instant Messaging. If I use an instant messaging client it is unobtrusive, small, light weight and responsive. I need to talk to someone then double click the icon in the system tray and then from the menu double click their name and away we go. It is discrete and easy to use, tracking our chat history if I want and still has drag and drop file transfer, also because chat platforms have become so open you can grab something like trillian which can patch into all the platforms so you can chat with anyone regardless of what software they use. With Google Wave I need to open a browser, login, start a new Wave and invite you. Now we can talk. Traditional IM takes ~2-3 seconds to start a conversation, Google Wave ~10-30 seconds.
Email. If I have a computer I will have my email client setup on it. There is no question there. Email has many, many problems ranging from the obvious, Spam, to trust, how do I know that DarthVader@hotmail.com is really the Dark Lord of the Sith? However as I said before the barrier to entry and ease of use is so low that almost everyone has access to email. For Google Wave if it was purely emailing your family and friends then it is almost comparable and in some cases much better. Wave’s track easier and turn them more into conversations you can follow instead of having to scroll through masses of text in an email. However what if I am emailing a business a question? Why do I need to add them as a contact to my Google account to add them to the Wave? Instead of email where you only need the address in Wave you need them added to your contact list. Yes Wave has some nicer features here for email like functions but email still remains easier and more palatable to use.
Collaboration. As a collaboration tool, again Google Wave has some fantastic ideas, the ability to replay Wave’s, for nested conversations and the simple drag and drop interface. For very small project’s I can see this being useful. However for serious collaboration project’s then an actual tool designed and written for this end is much more robust. Something like Sharepoint and even creating your own Wiki. When using Google Wave and the post count and the amount of people grew the Wave’s slowed down immensely. I understand it’s a beta but the amount of content created with even relatively simple projects is still an incredible amount I do not believe that a Wave could cope.
To sum up I like what they have tried to achieve and I believe the fundamental idea, this approaching communication from a digital background, is amazing. However I also think that the problems with Google Wave are built into the way it works so continuing down this path, trying to fix the symptoms as fixing the underlying problems is not possible.
Fixing Google Wave would require such a massive effort and a reworking and rewriting from the ground up that I think it would be simpler to view Wave as a first attempt; take what was learnt and start again.
Wave needs to be hosted in the cloud as it is now, accessible from a browser. It also needs a desktop component that synchronizes with the cloud so it can run like a common email client taking the load off the browser which at the moment simply cannot handle it. It also needs a third IM-like interface, say a mini version that would run in the system tray and would have a stripped down version that would still synchronize with the desktop client and the cloud. That would fix most of the issues I have with Google Wave.