3 ms·

1) I like the live typing, though it does sometimes lead to people ignoring the rest of somebody's message after reading the first sentence. It's good for colla

1) I like the live typing, though it does sometimes lead to people ignoring the rest of somebody's message after reading the first sentence. It's good for collaborating on documents like class notes, to-do lists, and other things. Maybe it would be nice if you could adjust the level of syncing: every character, every word, every blip, etc. 2) You could turn on email notifications. I suspect this wasn't done by default because for people like me who had waves constantly being updated and changed, the notifications would have flooded my inbox. The integration definitely could have used some work, but there were ways for you to be notified.

adhipg 15y ago
I thought the email notifications weren't turned on by default was because Wave was being marketed as the new alternative to email - a system to use to get rid of emails.
- maaku 15y ago
  One of the big reasons Wave failed at Google was that everyone thought it was supposed to be a replacement for email and it wasn't--it wasn't meant to be and it doesn't serve as one. Wave was meant to replace a certain way in which we use email, which is a subtle but important difference. It was supposed to replace the emailing of versions of documents around, or the long email threads to organize simple things like getting lunch or dinner. These are things where email still to this day falls flat, and Wave solves completely. There is ample room for startups to be disruptive using nothing more than the open source Apache Wave software.
  - ak217 15y ago
    I have always been dumbfounded by the fact that Google didn't try integrating wave into gmail. If they managed to make a back-end to support turning any email exchange (between people with Google accounts) into a wave at the click of a button (and without leaving the shell of the gmail interface), I have a feeling this product would have been a resounding success - the same way gchat became an instant success when integrated with gmail.
    - fraserharris 15y ago
      Whats stopping someone from making a GMail add-on?

adhipg 15y ago

I thought the email notifications weren't turned on by default was because Wave was being marketed as the new alternative to email - a system to use to get rid of emails.

maaku 15y ago
One of the big reasons Wave failed at Google was that everyone thought it was supposed to be a replacement for email and it wasn't--it wasn't meant to be and it doesn't serve as one. Wave was meant to replace a certain way in which we use email, which is a subtle but important difference. It was supposed to replace the emailing of versions of documents around, or the long email threads to organize simple things like getting lunch or dinner. These are things where email still to this day falls flat, and Wave solves completely. There is ample room for startups to be disruptive using nothing more than the open source Apache Wave software.
- ak217 15y ago
  I have always been dumbfounded by the fact that Google didn't try integrating wave into gmail. If they managed to make a back-end to support turning any email exchange (between people with Google accounts) into a wave at the click of a button (and without leaving the shell of the gmail interface), I have a feeling this product would have been a resounding success - the same way gchat became an instant success when integrated with gmail.
  - fraserharris 15y ago
    Whats stopping someone from making a GMail add-on?