Was Google Wave just ahead of its time?
Remember Google wave? As Wiikipedia explains Google Wave is a web-based computing platform and communications protocol designed to merge key features of communications media such as email, instant messaging, wikis, and social networking.Communications using the system can be synchronous or asynchronous. Software extensions provide contextual spelling and grammar checking, automated language translation,[3] and other features.
Initially released only to developers, a preview release of Google Wave was extended to 100,000 users in September 2009, each allowed to invite additional users. Google accepted most requests submitted starting November 29, 2009, soon after the September extended release of the technical preview. On May 19, 2010, Google Wave was released to the general public.
However Wave proved to be short lived. On August 4, 2010, Google announced the suspension of stand-alone Wave development and development was handed over to the Apache Software Foundation which started to develop a server-based product called Wave in a Box.
What went wrong? Certainly Wave felt clunky to use and was not always particularly reliable. The interface felt crowded and sometimes confusing. But I think the main problem was that we just didn’t get the idea. Now only three years on, it might have been so different. Just within one project I am working on, Learning Layers, we are using Flash Meeting and skype for regular synchronous communication, Doodle polls to set up meetings, dropbox to share files, Diigo to share bookmarks, Google docs for collaborative writing, to say nothing of the project internal media wiki site and the public wordpress based web site. And of course a list serve which bombards us with ever more email. We all complain that communication is not good enough and simultaneously that we have too much communication.
In reality communication has moved from being episodic, where email replaced snailmail and online meetings replaced face to face – to a stream. Managing that stream is problematic. And that, I think, was what Wave was designed to do. Sadly it was ahead of its time. Come back Wave, all is forgiven.
I think that wave wasn’t ahead of it’s time. We used it in our team and it worked quite well. We didn’t like the idea move to another services and fortunately our team works on web technologies and it wasn’t very difficult to resurrect old wave.
So we did it in rizzoma.com it has all functionality that wave did. And we also tried to make interface clean for newcomers.
At the moment I am just search on web and think how to make wave easier for use. Let me know if you have any ideas for it.