Wave, After a Month of Use
I like it even more, now. Naturally, more of my friends and family are using it, so there’s a greater level of activity. Fewer conversations are about wave. There are a surplus of invites available now, so let me know if you want one.
I’ve still only bothered to check out one public wave — no surprise, as they are more analogous to newsgroups than to email, and I never had any interest in newsgroups. A number of interesting bots and extensions are already being developed. Many are amusing, but some are actually very useful. I look forward to seeing what tools are developed for wave.
I am now more confident that Google has been was playing up all of the shiny features a little too much. At least, they have been from my point of view, but their target demographic is anyone that uses email — quite broad. So maybe their marketing strategy is the right choice for most of that group. In practice, I don’t find myself using the extensions or bots much at all. There are definitely some great ones available, but most of them are designed for fairly specific scenarios. Take, for example, the map gadget that Google produced. It’s perfect if you need to give someone directions. In the scope of general conversation, though, that’s not a very common occurrence.
The real value (again, from my perspective — a programmer) is in the protocol and its openness. The wave protocol is far better suited to current technology than email. It’s secure by default, whereas sending an email is like sending a post card — wide open for anyone to read. It’s also very versatile, as we’ve seen with the array of third party gadgets and bots. The openness is great because there couldn’t be global adoption without it. Wave is an improvement over email in every way, and the only downside that I can see is that there will have to be a transition period during which we’ll be using both email and wave.
I frequently hear the same comments and questions about wave:
What is it for? I don’t know what to do with this.
It’s intended to replace email. I think Google has failed to sufficiently convey this. They’ve spent a lot of time explaining all of the edge-case things you can do with it, without sufficiently highlighting the most common use case. The message from Google has been “collaborate! wiki! photos! gadgets!” Those things are great, but 99.9% of blips will be pure and plain text. I hope Google can find a way to emphasize the fact that it does plain text a whole lot better than email, too.
There’s no one here. What good is it if no one is using it?
Be patient — it was launched less than two months ago, and still isn’t open to the public. Everyone can’t be using it right now. Many people still haven’t heard of it. If Google has given you invites to share, then send them to your friends, and soon you’ll have more friends using it.
But everyone already uses email. It’s the standard. And even if a lot of people start using wave, there will always be holdouts, so why bother?
Is that to be the attitude for the next 100 years? The standard is inadequate and change is past due. The sooner email dies, the better. Yes, there will be holdouts, especially in industry, so a transition period is inevitable. It’s a small price to pay. Keeping up with both email and wave is easier if you install a notifier, which will inform you when there’s new activity on your wave account:
Notifiers for other browsers and platforms are available, as well as wave apps for the iPhone and Android.