This is a short series of essays on how I have been using Google Wave in the few weeks since I’ve got my invite and why I think it is a great tool for collaborating.
This started out as an idea for a single blog post, but as I began outlining it and fleshing out the sections I wanted to write, it soon became too big for a single article and so I decided to split it into a few different ones so as to make each part bite-sized, making the whole thing easier to read and spreading it out over time a bit.
I’ll use this first article to keep track of all the subsequent ones, so as to turn it into a kind of index of the whole series (look for it at the end of this post).
My feeling so far can be summed up in like this: I really like wave!
I’ve been wanting a product like this for a long, long time and I’ve been using things like Google Docs for some of the purposes I now use wave for, but some things have been lacking all along.
I always knew what I wanted out of such a product (I’ve worked on a prototype of a system loosely resembling part of what wave is many years ago, on my last years at university, and I’ve been pinning for something like this to show up ever since then) and now, after using wave for a while, I find that it fulfills my needs quite nicely.
It is still not all there, of course (and I will address this on an upcoming article,) but it is on the right track.
This, then, is why I love Google Wave and why I think it is a product with great, great potential.
In the rest of the series I’ll describe some of my best use cases, interesting ways I found to use it and what I still feel is lacking.
Hope you enjoy it! (And no, at this time I have no invites to hand out, sorry.) :-)
- Part 1 – Google Wave - what it is and isn’t
- Part 2 – Google Wave - how I use it