Tuesday, March 22, 2011

Status of Google Wave

crosspost from the official Wave help directory.

As Google announced in August 2010, Google is not continuing active development of Google Wave as a stand-alone product, but has been working hard on the open source Wave in a box project and on making waves accessible through Google Docs.

Google lets you know that it will keep wave.google.com running past December 31, 2010 until a suitable replacement to host all your waves is available. In the meantime, you can now use the export feature to download a zipped version of up to ten waves at a time.

Additionally, Wave in a Box, the project to make it easy for anyone to host their own wave server, has made significant progress on both functionality and community growth. Just last week, the Apache Software Foundation accepted Wave into its incubator for new projects.

Thanks yet again to all our users for giving Wave a try with your schools, businesses and organizations and to the developers who are working on the next steps for the open source project!

Friday, December 18, 2009

Google Acquires Etherpad

From february 2010, the Etherpad team will be working fulltime on wave. This is good news for anyone who's been annoyed by the beta-flavour of wave's collaborative editing features. Etherpad has been around for a while, and is far more mature than the current collaborative editing features in wave.

This also means that Google continues to invest in the further development of Wave. (Not that we doubt this, but it's nice to see some real tangible proofs of commitment like this)

Saturday, October 17, 2009

Samuel L. Jackson Rides The Google Wave... Pulp Fiction Style

A very good way of illustrating the use of Google Wave :-)

Friday, July 24, 2009

Sandbox Access arrived ... oh wait ?

Early this morning, I finally received a long awaited email saying that I was invited to the Google Wave Developer Sandbox. I tried to clear my schedule for the day as good as possible for some first experiments, only to find out that this "invitation" required me to fill in another form.

Finally, the form tells you that it will take a couple days to process your request and *really* grant you the access. They make fantastic technology, but the folks from Google Definitely know how to tease people the right way as well.

Friday, July 17, 2009

Sandbox Access is finally coming

There was an interesting announcement on the Google Dev blog today. They stated that after granting sandbox access to 5800 developers from google I/O, and various developer day events, they finally started distributing accounts to people who filled in the request form.

What really makes me check my mailbox every five minutes now is the fact that they are distributing accounts mainly on a first-come first-served basis. So I hope you filled in the form right after you saw the Google Wave I/O video.

Saturday, July 4, 2009

Emerging Wave Applications

A batch of Developers received access to the Google Wave sandbox and guerrilla coders around the world are unleashing their creativity on the defined API.

The PyGo wave server is a non-google developed server on which you can get an account today. And more important, you can upload your own bots and gadgets to share them with other PyGo users.

There are also two emulators out there: Avital Oliver's Emulator, inspired on the earlier Vidar Hokstad iframe emulator

On to the applications ...

Grauniady - Guardian Google Wave Prototype Robot



Grauniady (grauniady@appspot.com) searches the latest items from The Guardian for a given phrase. This robot is a great example how mainstream media could use Google Wave.

Wavethingy - The first Monetizing Robot



Andres Ferrate demonstrated Wavethingy (the first monetizing robot) at the first Google Wave API hackathon.

Wavethingy (wavethingy@appspot.com) searches Amazon for DVDs and books, and gives the author a cut of any purchases made off the links.

Bloggy



Bloggy publishes the contents of a wave, to a blog, comparable to what you saw on the google wave demo.

Thanks to wavety.com for the contents of this post

Sunday, June 21, 2009

Is Google Wave just Gmail on Waves?

In a previous article the question whether Google Wave can tackle the ever growing inbox was raised. A few tips were tossed, mainly suggesting user discipline assisted by Google Wave.

I haven’t played with Google Wave yet, my thoughts in this article are solely based on screenshots of the Google Wave client (see for example Figure 1). But when I compare those screenshots of the Google Wave client to Gmail it seems to me there’s not much difference. We still have a central inbox, only now it contains waves. While I love the wave concept, I fear Wave extensions and robots will only increase the size of our inboxes.



Figure 1. Google Wave. Source: The Official Google Blog


There’s no doubt waves have the potential of drastically changing communication and collaboration. However, assuming the screenshots are representative, I do doubt the current Google Wave client will improve the management of my inbox. In this article I will try to figure out a way to collect and present waves to the user without cluttering their inbox.


Inbox vs. Archiving


On of the key points from the previous article is to delete, act on and/or archive mails in your inbox. This in fact got me wondering, how or what do I actually archive? In my case, I have about 1400 messages in my inbox, another 1300 archived. Archived mails mostly include newsletters, iTunes receipts, serial number of programs I bought, et cetera. On the contrary, my inbox contains all kinds of mails, but mostly conversations with contacts. This means my archive is actually cleaner or better structured than my inbox! Or at least the way I am archiving is not sufficient to cover all emails in my inbox.

Before going further, let’s take a look at some other inboxes.

Snail mail Regardless what you do once you’ve opened the envelope and read your mail, you never put it back into the mailbox! In the laziest case, you either throw it away or put it on a pile. Otherwise you classify the mail in categories such as correspondences, bills, magazines, commercial, ... Mostly without even realizing.

Task Managers They often provide an inbox for quickly gathering new tasks from emails, sms, webpages, et cetera. Once you have a spare moment of time, you start labeling the tasks, pick a due date and assign them to projects or more general context (cfr. GTD).

By some mysterious mechanism these kinds of inboxes end up empty. Mysterious? No. Snail mail of course takes up physical volume which is either limited by your mailbox or your hallway. Regarding task managers, I guess we simply prefer shorter task lists over longer ones.

So do we need ways to classify waves in our inbox? We already have labels and filters, you say? True. We all know the combination of labels and search serves as an alternative to folders, that’s what Gmail is about and Google Wave seems to use the same principles. However, labeled e-mail keeps sitting in front of us in the bloated inbox unless we archive it which is just putting it on a second pile. So there’s actually no real difference between the Wave inbox and the Wave archive. Both pile up to a confusing mess of waves which we have to query to find anything (luckily Google is good at that).


Another View


So we need ways to classify waves and move them out of our inbox. We need to bring some of the inbox cleaning mechanisms from snail mail and task managers to the wave inbox.

So let’s start with automatically moving waves out of the inbox once we’ve opened the wave and start classifying the wave right away. The default classification could be archive. I know, now we’re creating one big pile again, but let’s take the Gmail concept of labeling and saved searches to a higher level. Since we can expect an explosion of robots and gadgets, we can use them for a more intelligent classification (even before we opened the wave).
In my eyes the central view on Google Wave should be something along the lines of Figure 2; an (almost) empty inbox and saved searches. I call those saved searches views on my wave collection. Like the current filtering system, we can create views based on labels, based on contacts (Friends, Family, ...), but also based on collaborations and documents (Project X, Project Y, ...), based on robots (Facebook, Bloggie, ...), based on gadgets (Chess, polls, ...), date ranges and so on.
You might even go as far as deleting the notion of an inbox altogether and simply define a view of new waves. Conceptually this is even more beautiful.



Figure 2. A mockup of the concept of Views in Google Wave.


You’ll notice each view has a badge counting the number of new waves for that view. We could even add more badges such as a badge for the number of active waves. Views based on robots and gadgets could define their own badges. For example, Taskie may count the pending tasks, while Facebookie counts the number of updates and wall posts separately, ...

So with one eye drop on this Google Wave mockup I see what’s actually new in my inbox, using the top view icons I see a summary of new, active or otherwise classified waves in my wave collection. Those are positioned central instead of tucked away in a sidebar. Finally, the active view presents me a filtered list of only those waves I am currently interested in.


Start


While Google say they started with the question “What would email be like if it was invented today?”, I can’t help but think they actually started with “So we have our mails in Gmail, what else can we add?”. They’ve build an amazing platform, but it’s not quite there yet. However, I think under the Google Wave hood we have the right engine to go beyond Gmail on Waves and change our views on waves.