I think the problem is that Wave is, fundamentally, a "Jack of All Trades, Master of None" platform. It tries to replace e-mail, IM, and office suite groupware and doesn't obviously lend itself to any one of those tasks well enough to market itself.
Google could have probably mitigated that by working to clearly demonstrate its usefulness in various use cases (eg. as a collaborative brainstorming and writing tool), but I got the impression they just said "Look at this cool thing we made! Help us find uses for it!" Wave as a protocol is still useful... it just may need a variety of more specialized clients on top of it to really shine. On Sep 4, 9:57 am, Alex <[email protected]> wrote: > I think the reason for failure of Google Wave are these : > > - Copying this ideahttp://www.wipo.int/pctdb/en/wo.jsp?WO=2005025177 > (Sept. 2003) without knowing potentials behind it . > > - Creating inhouse applications without knowing what was the reason to > create such protocol in Origin. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
