Google Wave was announced in May 2009 as an email today. Their theory was email was about thirty years old, it hadn't changed much in that time but the digital world around it had. So the thought was what would email look like if it was invented today, the answer was Google Wave, a realtime instant messaging meets email known as waves. By the beginning of August 2010 Google decided it was time to pull the plug on this experiment.
Where did it all go wrong.
In first instance Email is the center of all our lives and is better in my opinion than Fax and even email hasn't killed off that. Second if email was invented toady it wouldn't be Google Wave in its current form, it would be Google Wave developed further down the line. Thirdly, email should be developed not a new technology so why wasn't email on steroids developed.
I'm a big fan of Google Wave, I use it for a number of different tasks and I'd even started moving a lot of long term planning conversations with colleagues to it. I was finding more and more ways to use it for my work.
What I found the biggest problem with Wave though, was the fact it didn't have a subject box, even an optional one. If I send an email it always has a subject box. It's the way I sort my message and search for them and I so wanted that in wave.
Though the extensions in Wave brought great expansion to its use, many of them didn't work as described. What I found though is many of the extensions I wanted available native in wave's. I wanted things like import and export documents. Countdowns to open and close wave discussions. Audio and video conversations that were recorded live then the recordings embedded like Ustream does for later review. Drawing boards, embedding waves in each other and externally, and even password protect part of waves. There could have been type what you say functionality or visual representations of links.
All of these functions would have made Google Wave what it was supposed to be and further more are already available technology, either used by Google or being developed by them.
Google became so much more towards the end, there were types of Wave such as meetings, brainstorming, to do lists, plus more. Each bringing a clear vision of what Google Wave could do and for someone who used it, I can say it did it better than most, but not perfect and not what we'd expect from Google.That was a big problem for me.
Wave began to show widgets that allowed for conversations or mini wave like forums to be attached to websites and was tested to a live Ustream Broadcast. This really began to show off the potential of the system and if Wave wasn't closing I'd have been trying that.
So what was its biggest problems, the answer. Scale. The scale of the project was big but also required to be small at the same time. Google were the only provider of Wave, meaning you had to be a Google member with a Gmail account that limits the amount of people willing to replace many email like tasks with wave. This stopped many people who would probably experiment or benefit using waves but not signup.
Second is the smallness of Wave, it's big and bulky but it works. I'd use it on a phone but it's too big. I'd use it on a tablet for work but only for task lists, brain storming basically the business functionality. I'd use it on my computer for meetings. That's the problem I couldn't use an aspect of it on one device or the whole Wave technology on something small like a phone, and belive me I've tried. The project just needed to be scaled like email has been across devices.
So I will wave goodbye to Google Wave, it was amazing and I hope its technologies do end up in my future email clients but as a straight replacement for my email I'm sorry the world just wants it to develop email not be replace it.
No comments:
Post a Comment