Linked by Eugenia Loli on Thu 15th Oct 2009 20:18 UTC
Thread beginning with comment 389460
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2009-09-17
well I thought the concept was simple enough (don't have an invite to Wave so I can't comment on its implementation), but I think Google deserves a lot of the blame for the confusion surrounding Wave, in their massive one hour tech demo they don't even begin to explain its inner workings till the very end and it was the smallest part of the presentation. It was mostly showing off gadgets completely unrelated to the core functionality. They were a nice way of showing that Wave is extendable and has an API to play with, but showing that stuff first really confuses things. The presentation also made no attempt to explain real world use cases, simply saying its an email replacement and letting people draw their own conclusions from that.
The final nail in the coffin of confusion is releasing the preview in the manner they did. Giving a collaboration tool to large numbers of people who have nothing to collaborate on is a recipe for confusion. Add that features that make using it as a communication tool more bearable, like draft mode or access controls, are totally absent at this point. Well its no wonder a lot of people are turned off.