A Google Wave reality check
MOUNTAIN VIEW, Calif.--Lars Rasmussen sighed, half an hour into a demonstration of Google Wave, the company's audacious attempt to reinvent Internet communication: we'd found another bug.
Rasmussen had patiently worked around other minor bugs during the demo Tuesday at Google's headquarters, but when images dragged into a wave wouldn't load properly, he asked his brother Jens, seated at the conference room table, to get an engineer on the issue right away. It's about two months before Google opens up Wave access to a larger audience, and there is a ton of work to be done.
Google's Lars Rasmussen demonstrated Wave for the first time in May, and is now focused on stamping out the bugs.
(Credit: James Martin/CNET)Google Wave was unveiled in May at the Google I/O Developer conference, and dazzled attendees with its goal: a combination of real-time communication with social-networking and search capabilities built into a familiar interface. Wave is more than just an in-box on steroids, however. It's also a communications platform that developers can use to build their own applications, something that many were excited about in the early hours of Wave's life on the public stage.
Behind the scenes, the reality is sobering for the Rasmussens and the 6,000 or so people actively using Wave. Job No. 1 for the brothers Rasmussen--who are managing the Google Wave project--is making sure Wave is stable enough to accommodate 100,000 new users that will start doing the Wave after September 30, when Google opens up the limited preview to a wider audience.
At the moment, around 25 percent of all Wave sessions end in a crash, Lars said. That's obviously not acceptable and, in an ironic twist, the highest priority bug on Google Wave at the moment involves search.
"I would imagine in six months this will be fast, slick, stable and usable," Lars said. "Right now, you have to be a super early adopter (to use Wave). By September 30, an early adopter."
Wave has been in the works for about two and a half years. The original prototype--constructed in nine months to pitch the concept to CEO Eric Schmidt and co-founders Sergey Brin and Larry Page--was actually discarded in favor of a system that provided better scale, Lars said.
Much of that time has been spent simply designing the workflow of Wave: how to add people to a wave, reply to a wave, add pictures, and create rules. Wave shares some basic infrastructure with Gmail, but is essentially a completely separate undertaking and has been a bit of an "organizational experiment" for Google in terms of giving an important project a great deal of autonomy, Lars said.
Google Wave is designed to be a next-generation Internet communications application and platform. When it works.
(Credit: Screenshot by Rafe Needleman/CNET)So why go public now, with so much yet to be accomplished? The brothers Rasmussen have heard the shouts of "vaporware," and actually chose the opposite launch strategy for the product that launched their Google careers: Google Maps wasn't unveiled until it was complete.
The difference with Wave is that Google believes developer feedback is crucial to its evolution as a product. "We wanted to get people thinking about how we're going to use it and what people are going to use it for," Lars said.
For now, however, Wave is carefully labeled as a "developer preview," a status that doesn't even rise to the level of one of Google's ubiquitous beta projects. While Google still has no formal process for determining what projects are previews as opposed to betas as opposed to full-blown products, the goal for Wave is reduce the number of crashes to less than 1 percent of all session starts, at which point the "beta" tag can be more confidently applied.
When introducing Wave in May, Google said it hoped to open the service up to the general public some time in 2009. That seems unlikely when viewing Wave in late July, but launching a product that has been hyped as much as Wave with anything even close to the number of bugs currently present would be a disaster.
Lars knows this. "Google can be a cushy place to work; we're not going to run out of payroll anytime soon. But we're putting a lot of pressure on ourselves."
Tom Krazit writes about the ever-expanding world of Internet search, including Google, Yahoo, online advertising, and portals, as well as the evolution of mobile computing. He has written about traditional PC companies, chip manufacturers, and mobile computers, spending the last three years covering Apple. E-mail Tom. 
Google seems to be in a rush these days to get stuff out. Or like the Google OS (which is a year away) talk about stuff not even ready for beta. Its as if they feel they must do this or finish second? Frankly, I don't like have baked stuff and Google lately is becoming all about that.
Twitter is genus.
Apple keeps things under wrap because they are not in the business of development so they don't really need others to help build any products. Its all completely controlled which is in line with their company philosophy as well. They like to be in total control and not let anyone else play.
Do not forget to read related articles about Google Wave at the address
http://www.haikaladli.co.cc/2009/10/google-wave.html
Probably the biggest problem is Google can't "just" talk to developers, normal "users" see this stuff too. Wave as shown promises to be a major shift in how we communicate and collaborate online, and is set to be a major "platform". To be honest, Wave looks far more exciting than "Chrome OS" and might prove to be the biggest thing Google have done since "Google Search", a grander vision than Google Docs.
Am I excited about Wave? Yes, as an enduser it looks really useful, however as a developer the possibilities are dizzying. If Google can get this right, this could be the Internet's new "Killer App".
But Wave just looks like Twitter and Facebook with some quasi mode interface gone insane.
Sorry, down, fanboy, down!
I think Google Wave has promise. I can't quite fully yet understand what it does, but that's the point, right? This is such a radical divergence, it's not another evolutionary step, but a revolutionary one. We'll just have to see if it pans out as something that can be useful and adopted.
I do think it's funny that we demand perfection coming out of the gate these days, but (and I wasn't around for it), how well did TV work when it first was introduced to the masses? How well does satellite TV work today when it's cloudy?
I am excited because it's so unique and Google has a reputation for unique and new. So I want to play and play first. Sorry, can't really contain the fanboy in me.
the real reality check for me is how are they gonna get this widely adopted outside of tech circles (and businesses once it becomes stable)?
i mean sure it's revolutionary and convenient but people already have an email and since google decided not to connect this to traditional email accounts, people aren't going to see the point of opening another email account while still having to keep up with the one they already have, especially if no one they know is on wave
i think that's gonna be the challenge
When all the specs of HTML5 are in place, things like Google Wave will work with less crashing and such. It's just cause Google is doing a big part of the work of actually coming up with all the new standards that will be part of HTML5. Google Wave is probably the most intensive Javascript AJAX web project ever created.
- by anders83 October 25, 2009 12:34 AM PDT
- another google wave review w/ dev screenshot: http://variableghz.com/2009/10/google-wave-review/
- Like this Reply to this comment
-
(30 Comments)