Google Wave API Day Sydney

[Gruden]

On the 19th June Google held a whole-day developer event at their Pyrmont office to showcase their new Google Wave technology and Gruden were lucky enough to be invited along.



The Day

As interesting as the technology - was the format used to showcase it.

The day started with a couple of short talks introducing the Google Waves system, the various pieces that make up the whole and Google’s vision for the technology. The 80 odd developers were then broken into small groups, each accompanied by a couple of Googlers and taken off to various corners of Google’s amazing Sydney offices for a lunch and informal Q&A.

The second half of the day was dominated by the hackathon - the idea here was for the developers to work together or alone on some wave related development of their choosing. During this extended period it seemed that the entire Wave team were on hand for discussion, brain storming, feedback and assistance. The documentation guy was there to hear how documentation could be improved, the Python API girl was immediately on hand to answer my App Engine questions, the UX guy was closely observing how people interacted with Wave and where they had troubles, the Java team were recompiling the API server to include additional dependencies. This level of interaction seemed to be a great way for the Wave team to learn how people are going to approach their product and a great way to help the developers who turned up to get up and running quickly. It was also great to see the level of talent we have locally - Google maps was developed in Sydney and it’s this same team that are behind Wave.

The hackathon culminated in people demonstrating their days’ work live in front of the group over traditional geek fare of beer & pizza. There were nearly 30 demos ranging from GPS hacks to games of connect 4 and hangman to bots that could define terms and tell you what is next on TV. The winner on the night was a shared white-boarding app implemented in Flash.



What is Google Wave?

There is no simple way to explain it. The most succinct explanation is possibly phrased as a question - if email was to be re-invented today, from the ground up, what would it look like? And by “from the ground up” we’re talking client, server, protocol, the lot.

At a fundamental level, Wave is an open protocol specification (http://www.waveprotocol.org/). The idea is that, as with email, a variety of companies will develop competing clients (eg. Outlook, Hotmail, Mail.app, Thunderbird) and servers (eg. Exchange, Postfix, Courier) based on the Wave specification.

On a more practical level Wave is email, real-time chat and collaborative content editing & versioning rolled into one. It allows for multiple people to communicate in real time using text and rich content, while retaining the full history of the conversation and the ability to browse backwards and forwards through this history.

Wave also incorporates a framework for developers to create gadgets (client side mini-apps that run within a wave) and robots (server side applications that interact with waves in various ways).

In Google’s own words:

Google Wave is a product that helps users communicate and collaborate on the web. A “wave” is equal parts conversation and document, where users can almost instantly communicate and work together with richly formatted text, photos, videos, maps, and more. Google Wave is also a platform with a rich set of open APIs that allow developers to embed waves in other web services and to build extensions that work inside waves.

- http://code.google.com/apis/wave/

If you want to know more about Google Wave there is a fairly lengthy video of it’s unveiling during the keynote of the Google IO conference a few weeks back. This video contains a number of interesting demonstrations.

There are also a number of online resources depending on whether you are interested in the back story, the big picture, the APIs or the protocol.



Will Google Wave change the world?

Maybe, but not any time soon. The protocols that we all depend on to send and receive email were initially developed in the early 80’s and while things move a lot faster now they still years to mature and get adopted.

Google Wave represents a major paradigm shift for end users to get their heads around which is not helped by the fact that it currently has serious usability issues. It is also very much in early beta - crashes are not uncommon and it needs some serious optimisation to avoid causing browsers to occasionally hang. Most of the time these are friendly and just require browser refreshes, but they are frequent.

But for all this it is an incredible step forward at many levels and it addresses many of the current shortfalls in current modes of digital communication. Google have shown they can address performance and usability issues in their products, so the extent to which Google open up and allow competition will probably be the deciding factor in Wave’s success.

Thanks to Jan Vaughan for the great photos



More...