There was a recent buzz on the internet about Google Wave. It’s an extensible platform for allowing people to collaborate over the web. It also handles tasks like email and IM. I have to say: I’m just not that impressed. It looks an awful lot like a solution looking for a problem. My guess is that Google Wave will be something some edgy companies will use, but isn’t going to get much widespread popularity.
See the Google Wave presentation here (warning: the full video is 1 hour 20 minutes long).
The good things about Google Wave:
– It’s extensible and open-source. People can add-on to this platform, and that’s good. I’m sure some people will come up with some cool stuff.
– The contextual spell-checker is cool. The system can identify mistakes in these sentences: “I’m making been soup. I’ve bean there.” A spell-checker wouldn’t catch those errors because all of those words are spelled correctly. However, the google system can identify that you used the wrong words. (Note: Microsoft also has a contextual spell-checker within Word. You can check out details here.)
– The just-in-time language translator is cool. I’ve heard for a few years that google was getting good at translation. I hope it works well (and if it doesn’t, I’m sure it will get a lot better).
The weak things about Google Wave:
– Their system has an email-type system that can also function as an IM. The problem with this: what problem are they trying to solve? Email and IM work “well enough”. I don’t think there’s much of an advantage here to using Google Wave as your email system. The functionality – while cool – isn’t really improving things in any significant real-world way. My verdict: this feature will only be used by a few edgy tech companies.
– Document playback: they can replay how a document has grown and changed over time. That’s nice, but is anyone going to use this functionality – except in cases where people want to track down who made particular changes to a document (e.g. like a wiki)? It could be somewhat useful in a company, not very useful outside of a corporate environment.
– Collaborative document editing: Everyone can change a document at the same time. That’s nice. There’s actually a free product that does this already: etherpad (etherpad.com). It’s kind of cool. Not very useful for most people. I can’t think of any time within the last five years where this would benefit my life. A few tech companies might be able to use it in some circumstances.
– Ability to access twitter feeds, put photos together into a single page, collaboratively look at google maps, or mirror conversations on a blog. Not that useful. It’s cool that they can do it, but it fits more into the category of “neat technology, but more of a curiosity”. It’s cool that they made it so easy to do this stuff, but it’s not really stuff that people want to do.
– Ability to play games (like chess). I think this is a plug-in thing. I wasn’t quite clear on whether the system enforced chess-rules, or if it was just displaying a bunch of symbols on the screen to both users. Either way, I didn’t really see this as anything other than “look what I can do; not that you would actually want to do it”. The good thing about this demo was showing that Google Wave can display a variety of data.
I can’t figure out why they didn’t add VOIP (voice) capability. I’m sure someone will add it as an extension, but it seems like it would be difficult to collaboratively create a document without being able to talk to the other people you are collaborating with. Are you supposed to simply type your IMs to the other people?
I think they’ve confused “cool technology” with the question “does this offer any significant benefit to the user?” Yes, it’s cool. No, most people are going to ignore it because it isn’t offering them any significant advantage over existing systems. While they did their best to make it easy to use, it’s still too complicated for most users.
The contextual spell checker and translator are something that could easily be dropped into other products, so I don’t really see those as specifically “Google Wave” features. Which leaves “it’s extensible and open-source” as the only real selling point. Hopefully, we’ll see a bunch of cool stuff from users that will justify the existence of Google Wave.
June 1 Update: I just read a similar article over at DaniWeb.com – “A Curmudgeonly Look at Google Wave”
Pingback: Webtorque » Blog Archive » Google Wave: OpenDoc Redux
“The just-in-time language translator is cool.[..] I hope it works well”
Who cares? This enables something that you could not do before. (I’m sure it’s good, but even if it was flawed, it would be better than nothing. I’m sure all the alternatives are too expensive except for high end businesses.)
“Collaborative document editing: [..] Not very useful for most people”
Seriously, before you met the Internet, did you wish you could “blog”? Did you wish there was some way to “type to other people” (IM/texting)? Did you wish there was a network of color fax machines so everyone could send each other their pages?
The thing about Wave is that it’s a technology that can be used multiple ways. You start off “hey, this is a half-decent way to do document version control and commenting”. But if you both happen to be on at the same time, you might think of some questions to ask realtime that you might not bother to write down otherwise. Wave will change the way people collaborate. (Not shown, but if you create a sub-wave, it’s a personal space to put your notes on anyone’s document — the notes will only appear to you, and be stored on your server.)
“. I wasn’t quite clear on whether the system enforced chess-rules, or if it was just displaying a bunch of symbols on the screen to both users”
I’m going to say it’s server-enforced. The wave server gets your keystrokes, then sends data modification commands back to the client. In this case, they are sending a graphic (or multiple graphics) in response to key/mouse clicks. The server is enforcing the chess rules.
I’m going to say Wave will be game-changing. It won’t matter if you adopt it, because it’s 100% server-side. You’ll come to a wave page and interact with it, just like you interact with wikis and blogs. There’s nothing to install.
I assume you mean “who cares if it works well” and not “who cares about language translation”.
You could do it before: babelfish.yahoo.com and translate.google.com. Both of them are free. The benefit to just-in-time translation is that they paired the existing, free translation with IM/email. You could do this before and it was free, but it’s a little bit easier.
(nod) Well, I’m not sure that I like the structure of that argument. The structure is “you didn’t think you wanted X, but now you realize that X is valuable”. The problem with that argument is that you can fit all new technology into that structure (even the flops), and imply that I just don’t realize how good it is. Example: I didn’t see the usefulness or value of a Segway, but I guess I’ll come to realize that the Segway is game-changing transportation.
I will say that the collaborative document editing might function well as an advanced wiki. The ability to add text without using the wiki text markup, the ability to draw pictures and diagrams, and a friendlier “document change replay” system puts it ahead of regular wiki systems.
Pingback: Google Wave: Let us know when it’s ready! — Ideeeas Blog