Google I/O: Spotty product launch history mutes expectations
Summary: Google's I/O developer conference kicks off Tuesday and expectations appear to be relatively low. Why? Product announcements out of I/O appear to be hit or miss. In fact, success or failure is basically a coin flip
Google's I/O developer conference kicks off Tuesday and expectations appear to be relatively low. Why? Product announcements out of I/O appear to be hit or miss. In fact, success or failure is basically a coin flip.
My plan was to look at previous I/O announcements and examine how things turned out. Danny Sullivan beat me to it and has a handy recap. Here's the rough breakdown:
- In 2008, Google used I/O to talk about Gears, Android, Google Friend Connect and Google App Engine. Gears and Friend Connect are toast. Android was a big win and App Engine is a work in progress. One enterprise software insider recently noted that Google breaks out App Engine once a year at I/O, talks it up and then forgets about it. Whether that perception of App Engine is accurate or not remains to be seen, but that take is telling.
- In 2009, Google introduced Google Wave. Developers thought it was great. No one else did. Wave was killed.
- Last year, Google used I/O to talk WebM, the video encoding format. WebM won YouTube and the jury is out beyond that. Google also talked the Chrome Web Store---an occasionally handy tool, but not a world beater. Google also showed off some voice recognition---a clear win on the mobile front---and Google TV. Google TV also got folks excited at first, but then the interface bombed with consumers. The search giant also talked about a music service, which has yet to appear officially.
With that track record is it any wonder that folks aren't expecting much? If you go back into the archives, it's almost comical how technology's chattering class gushes and then retreats or drops the follow-up entirely. In 2009, Sam Diaz noted that developers gave Wave a standing ovation. Oops. Diaz said that Wave had a chance, but the learning curve was steep. My former partner in crime was also highly conflicted about Google TV---which was a revolution that later needed to go back to the drawing board. Maybe it's the keyboard.
That progression is common with Google's flagship developer conference. Euphoria followed by buzz, then backlash and then a thud.
Looking at Google's session topics clearly revolve around Android---the search giant's best horse beyond search. One key session will be Honeycomb Highlights. If I were to be a total cynic I'd have to ask "what highlights?" Google didn't give Honeycomb a lot of app support out of the gate when it c
ould have launched a kick-butt Google Docs. Honeycomb more often than not is viewed as the weak link in the Android tablet army. Will Google address Honeycomb's issues---which revolve around stability and third party apps? Or will Google do what Microsoft did with Vista and blame problems on perception? If Google isn't careful Honeycomb may become its Vista.
Another Android topic revolves around NFC (near field communications). Google, local, commerce and NFC could be compelling.
Chrome, Commerce and App Engine are also session tracks worth noting. It's also worth noting that those three categories---with the exception of Chrome---are sort of middling in the momentum department.
Google Apps will also be worth noting. The offering is at an interesting juncture---momentum continues and competition surges just as news attention wanes. For Google that's good news. The same buzz-to-mundane cycle happened with Linux too. Now you can't find a data center without some percentage of Linux implemented.
In addition, the Geo track is worth watching---if only because of all the hubbub around location tracking.
Add it up and Google has an interesting set-up for this I/O. Expectations are low and that means Google has a nice environment to surprise a few of us.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
Good analysis of Google failures. But, smart for Google to keep at it. For
RE: Google I/O: Spotty product launch history mutes expectations
Also, there's no reason why past failures can't be incorporated in future developments elsewhere. I'm sure the functionality in Wave will pop up somewhere else eventually. I also think it would have been better received if it had been an extension of GMail rather than a seperate service.
RE: Google I/O: Spotty product launch history mutes expectations
I think they were overconfident with Wave, where they decided to have it driven by invitations, when they had to throw it open to all. They decided to exclude IE for running Wave, meant half of their target audience was already out. Biggest issue seemed to me the lack of any relevant use case for it.
RE: Google I/O: Spotty product launch history mutes expectations
"Also, there's no reason why past failures can't be incorporated in future developments elsewhere."
Or future failures. I feel that if Google wanted a brighter future they would develop better product offerings and not be as much of the half assed products they offer now. Mind you they have some functional offerings but they are half baked at best. There is nothing that has been seen as a true full fledged product but then again everything they offer is through the cloud and can only be loaded so fast and even then they have no real true base to stand on whereas other companies have been developing software for ages. They should focus more on their strong products and look into how to make them stable and offer more rich features. Good Luck Google... Oh and stop invading peoples privacy!
"developers gave Wave a standing ovation"
RE: Google I/O: Spotty product launch history mutes expectations
I think because all of their stuff is cloud-based they find the temptation to release products very hard to resist - they're easy to deploy and being ad-supported it's all about getting eyeballs on the screen. The result of this is the "see what sticks" approach,
Microsoft by comparison have tons of research projects that could be deemed as "failures" because they don't directly lead to anything, the only difference is they keep it in-house whereas Google put theirs public.
As I said in my original post though, just because a company (any company) fails with one product doesn't mean that the nuts and bolts of it don't end up surfacing elsewhere.
RE: Google I/O: Spotty product launch history mutes expectations
RE: Google I/O: Spotty product launch history mutes expectations
I am hoping to hear more about Native Client and PNaCl.
RE: Google I/O: Spotty product launch history mutes expectations
I hope they address Honeycomb and give us some closure on upcoming updates and fixes to help make it the OS it really should be. Anything else they talk about after that is all a bonus in my book (I am sure most of it will be useless fluff though).
You can bet that Google will be working overtime on fixing the problems
RE: Google I/O: Spotty product launch history mutes expectations
RE: Google I/O: Spotty product launch history mutes expectations
But don't you think that PNaCl could be hit or miss for Google? They are either going to do it right, or really wrong.
Exactly, the success of PNaCl is not a forgone conclusion. The idea is
RE: Google I/O: Spotty product launch history mutes expectations
Add to that the hyperbole tech bloggers conjured up about a Moto Xoom not running any software (only videos) after CES, and the only conclusion one can make is that you guys are full of it.
RE: Google I/O: Spotty product launch history mutes expectations
I love my APPLE TV! best purchase ever!!
RE: Google I/O: Spotty product launch history mutes expectations
I love my Google TV.
It's certainly not my best purchase ever. But it does make my friends who have Apple TV green with envy when they visit and see the things ATV can't even begin to do.
Google will keep trying to get it right, but, you analysis is mostly
RE: Google I/O: Spotty product launch history mutes expectations
How do we know they will keep trying? They certainly did not keep trying with Wave and other failed ventures. Maybe they will do the same to GoogleTV, pull the plug.
dave95: Pulling the plug on GoogleTV is always a possibility, but, I think