They blew it big time by hyping it for RPGs, which never went anywhere. Get the RPGers on board, perhaps, and you can succeed.
Google Kills Wave
11–20 of 246 posts
Re: Google Kills Wave
#12Did Google believe that this was going to succeed as a consumer product, à la Facebook?
Wave, as it exists today, is a great tool for corporate communications. With the right interfaces, integration, and extensions it could definitely displace Exchange and Lotus Notes. Eventually, as a protocol, it had the potential to transcend email.
Maybe Google just hoped Wave would appeal to a different market than it really does.
----
PS #1: I'm sure that corporate uptake of Wave in its current form was limited as well because of the absence of a reasonable client/server that you could run on your own network.
PS #2: Hopefully there are enough of us who like the protocol that, over a number of years, we can build Apache Foundation-quality F/OSS implementations of the needed components.
PS #3: It would be truly ironic if, say in 10 years time, Google finally integrated the Wave Protocol with Gmail because there had been enough private (but federated) uptake as an email replacement.
Re: Google Kills Wave
#13Re: Google Kills Wave
#14I, for one, am very dissapointed by this. Even worse I feel somehow partially responsible. I have been a huge proponent of Wave in theory, but even after getting into the early beta I just never found myself /using/ it. I blame this mainly on it lacking the social graph I cared about.. But I thought I could just bide my time and in 5 years it would have taken over. I am starting to feel like I will have to deal with…
I just don't get it.
Re: Google Kills Wave
#15I feel bad for the Etherpad guys, who as I understand it, sold AppJet to Google to work on Google Wave: http://news.ycombinator.com/item?id=977015
alternatives: http://etherpad.org/etherpadsites.html
Re: Google Kills Wave
#16If I want to 'connect' with friends, I have Facebook, and if I want to im work colleagues, I have Yahoo and MSN.
For document collaboration I have email for non-realtime, Google Docs for near and actual real-time.
I have a hard time seeing where my workflow needs any more collaboration tools.
Re: Google Kills Wave
#17Re: Google Kills Wave
#18unfortunate. it was a good product, for the right market, but it was overhyped and it underdelivered.
Seems to me that not a single person I knew actually wanted to use it, or thought it filled a niche they needed filling.
Re: Google Kills Wave
#19Wave has not seen the user adoption we would have liked. Did Google believe that this was going to succeed as a consumer product, à la Facebook? Wave, as it exists today, is a great tool for corporate communications. With the right interfaces, integration, and extensions it could definitely displace Exchange and Lotus Notes. Eventually, as a protocol, it had the potential to transcend email. Maybe Google just hoped W…
Re: Google Kills Wave
#20I feel bad for the Etherpad guys, who as I understand it, sold AppJet to Google to work on Google Wave: http://news.ycombinator.com/item?id=977015
I still miss etherpad. I use some of the alternatives, but it's not the same :( alternatives: http://etherpad.org/etherpadsites.html