Google Answers was destroyed by Yahoo Answers - you could see the approach they were going for though - a properly answered question can be shown again and again. SO seemed to strike a balance between the two.
Google Answers was destroyed by Yahoo Answers - you could see the approach they were going for though - a properly answered question can be shown again and again. SO seemed to strike a balance between the two.
Wave was a textbook example of how you can fail if people don't understand why they should use your product. They gave up on it (by handing it to the Apache Foundation where it continues to be developed), rolled the clever collaboration technology into Google Docs, and told everyone they'd made it so you could edit a doc at the same time as someone else. Everyone continues to love it to this day.
So you're right that it's not like Slack or Hipchat, but I think you may also misunderstand its purpose.
The 'about' page: https://web.archive.org/web/20100427183005/http://wave.googl...
Actually, looking at the screenshot on that page, I can see why s_dev sees it as something like Slack. It has a much more 'chat'-based interface than I remember. Sorry s_dev.
Simplifying the interface, inviting more people to the beta when it was originally out, and increasing the ability to federate easily were three big things that were missing from wave for more people to adopt it imo.
The purpose of Google Wave was basically to be a fancy do all messaging service. Many critics have compared Slack to Google Wave including Hunter Walk an ex YTer and Googler. You can see that Google Wave was probably even more powerful - so powerful that it looked daunting and confusing and people didn't know how to use it.
Wave.google.com was an example product using said protocol. Since the protocol was barely spoken of, even by developers, everyone assumed the website was the (only) product. Since the website did a lot of things, and none of it well, often being compared to email, it flopped and the entire project folded..
Now the project lives on in obscurity under Apache: http://incubator.apache.org/wave/about.html
¹ Technically, the "Wave Federation Protocol", but anyone that really looked into Wave would know that the protocol was the most important element of the project.
You mean like google docs?
GA worked quite well at first. There were some very active users that did excellent work and got paid quite nicely for their efforts. But a vague set of rule changes started to migrate in.
For example, a non-verified observer could comment on a question and pretty much give the entire answer. An official GA Researcher would answer the the question above the line, and the response from Google would be "Well, you didn't add any information to this topic than what was already on the page, so no payment for you". Riiiiight.
There were other little quirks and then eventually Google announced one day it was over. That's just how it rolled with them. I'm chalking it up to shiny things elsewhere that took attention away from GA. I did get a nice fleecy blanket as a Christmas gift one year. Not sure why.
That's somewhat true for certain technical aspects but it's too quick to ignore the mistakes Google made and minimize the value of work which more successful products put into the user experience.
Google never made the case for why using Wave would benefit you; as with Buzz, Plus, etc. Googlers reported liking it because they had both critical mass and pressure to use it long enough to see the benefits but few people outside did.
Instead, what we did hear about a lot was the technology which was going to change the world right up until it failed. This is a common failure mode for Google where the strong engineering culture crowds out UX, forgetting that for almost any product that's an implementation detail which most people shouldn't need to care about.
Wave has been collecting dust as an Apache project ever since.