"Google Will Surprise You"
Aug. 10th, 2009 12:29 amI heard about Google Wave a while back, but didn't give it nearly enough attention. After seeing the the ten-minute version of the presentation, I think it really could be a game-changer. Here are the key bits:
1. Wave unifies email, IM, and collaborative document editing. Arguably, it attempts (in a way that might possibly succeed!) to make the previous forms of all of those obsolete.
2. Wave adds a threaded comment system to everything (and a really powerful one; in particular, you can control permissions/visibility at any level of the tree). That's a feature many (all?) collaborative document editing systems currently lack. True threading of replies could also cut a lot of redundancy and confusion out of email, especially when one or more of the following are true: The subject matter is confusing, multiple people are involved in the discussion, messages contain more than one question, messages refer to eachother.
3. Wave is an open protocol. This pretty much fits with Google's "do then monetize" business model. Google doesn't really care who ends up doing cool things with Wave, they'll figure out how to use that to make money either way. Historical precedent says they shouldn't count on making money from controlling the protocol itself.
1. Wave unifies email, IM, and collaborative document editing. Arguably, it attempts (in a way that might possibly succeed!) to make the previous forms of all of those obsolete.
2. Wave adds a threaded comment system to everything (and a really powerful one; in particular, you can control permissions/visibility at any level of the tree). That's a feature many (all?) collaborative document editing systems currently lack. True threading of replies could also cut a lot of redundancy and confusion out of email, especially when one or more of the following are true: The subject matter is confusing, multiple people are involved in the discussion, messages contain more than one question, messages refer to eachother.
3. Wave is an open protocol. This pretty much fits with Google's "do then monetize" business model. Google doesn't really care who ends up doing cool things with Wave, they'll figure out how to use that to make money either way. Historical precedent says they shouldn't count on making money from controlling the protocol itself.