Google announced the pre launch of its new open-sourced collaborative tool on Wednesday and by the same token, a call to developpers to help improve and enhance it. Some call it the new gen e-mail. Goo gave it a fashion acronym: the 3Ps for Product, Platform, Protocole.
Early adopters have already mapped out their positions.
Thumbs up for L Gray: http://www.louisgray.com/live/2009/10/google-wave-hits-shore-flash-flood.html
Thumbs down for R Scobel : http://scobleizer.com/2009/10/01/google-wave-crashes-on-beach-of-overhype/
Here some great features that I believe will win over most of us embedded api fans:
- Caracter-by-caracter real-time transmission is one of the highlights:is said to be useful for time-wary users who don’t need to wait for the other person to finish typing to see the entire message as is the case with IM
- Subtree of waves allowing the user to respond to a specific comment within the email without hand-editing it.
- Automatic correction as you type and translation in 40 languages
- My favourite : wave embedded into Twitter and other blogs >respond via wave and uploads to blog real time
- Other client extensions: Maps, photos, social n/w (orkcut)
I can see the relevance of Wave in the workplace as you can share your notes via e-mail (wave UI) and allowing selected users to discuss and add comments within the thread instead of attaching a doc and have users respond to it asynchroniously. My guess is that it could become quite difficult to manage if you add too many good buddies like in social n/w .
There’s a downside to all great innovations: Wave is valued for its unique features but also for its real-time applications. However, the latter can only work with 3G+ (4G). Even more so for wireless apps. To keep in mind that this concerns only a handful of (US) cities.