Wednesday, May 19, 2010 | 9:41 AM
When we first launched Google Wave in developer preview mode at last year's I/O, thousands of developers started playing around on WaveSandbox.com, experimenting with the APIs, and checking out the preliminary set of specs and whitepapers on waveprotocol.org. Back then, many developers looked around and decided that they couldn't do what they wanted with the APIs yet, or the protocol wasn't fleshed out enough for their needs, so they filed their feature requests and slowly disappeared from the Wave world.
Today, we'd like to encourage all those developers to take a second look. Over the past year, and today at Google I/O, we've launched a series of improvements that make Wave a more compelling platform, product, and protocol, and enable the kind of apps and integrations developers first dreamed of when they encountered Wave.
Here's a quick recap of the last few months of API releases:
- We introduced (and iterated on!) an extensions gallery, making it easier for users to find extensions.
- We launchedRobots API v2 and the Active Robots API, making it easier to integrate with external systems. That release, along with Mashable's Google Wave API Contest, resulted in robots like Ferry for Google Docs integration, Mr. Ray for email integration, and Salesforce.com's just-announced Force.com Toolkit for for the Google Wave APIs, which shows how developers can bring Google Wave together with the Force.com platform and Salesforce Chatter.
- We releasedanonymous read-only access for embedded waves, making Wave a more compelling platform for publishing content and discussions on the web, and leading to some live blogging experiments.
And here's what we've announced at I/O:
- Run robots on any server -- not just App Engine. This means you run robots on your own web servers, and you can use your language of choice, making it significantly easier to write robots that integrate with your existing website and systems. Read more in the docs. Use a robot to manipulate and retrieve attachments within a wave, so you can build something like a wave -> Flickr album converter, a CSV -> interactive map builder, or as we'll be demo'ing live at the I/O talk, a wave -> PowerPoint exporter. Read more in the docs. Use the "Wave This" service to let your website's visitors easily create waves out of the content on your site. You can see an example of it in use with the Wave This Chrome Extension. Read more in the docs. Fetch waves on behalf of users with Wave data APIs to build lightweight clients or apps like what we just launched, the official Google Wave Notifier Chrome Extension. Read more in the docs.
Beyond the API releases, we're also open sourcing a lot more of Google Wave's code, including the rich text editor, so you can learn how to run a wave server, like the one Novell Pulse is working on, and start prototyping with a simple frontend for editing and replying to waves. You can also extend that code to build your own alternative Wave clients. Today, SAP announced that they are working to adopt the Google Wave Federation Protocol in their product, StreamWork. Stay tuned for another blogpost with more pointers and details.
Now, all of this sounds great, but as a developer building on top of a platform, many of you will be most concerned about one thing: users. We've been in invite-only mode for the past year, and built up a loyal user base of about 1 million active users. Today, we will let anyone with a Google account use Google Wave (no more invites!), *and* even better, any company or organization using Google Apps can enable Wave for their domain. So, there should both be more users who want to use your extensions and more businesses that want developers to build extensions for them. Win-win!
We're not done yet, of course. The product and the APIs are in Labs, because we think it's important to stay flexible when creating a whole new paradigm in web based communication and collaboration. We want to be able to respond to your feedback, and we still have a lot left to do to make the vision a reality.
But we think we've made good progress with these improvements, and we invite you to check them out, give us your feedback, and hopefully join us on the rest of this journey.