• http://buzzintechnology.com B.I.

    During Google I/O 2010, other than Google TV, I only remember Google taking digs/pot shots at Apple at every given opportunity. It will be interesting to see What Vic Gundotra has in store this year.

  • http://www.informationworkshop.org MarkHernandez

    One big elephant in the room I hope Google can address at Google I/O is the handset updating challenge to all the different handsets through all the different carriers (and sometimes underneath the UI layers the handset makers apply). Apple has already made the “locationgate” issue all but moot before they even testify in Congress, having already updated all iPhones that wish to be updated.

    Developers will find it difficult to add new features to their apps if the giant Android installed base is lagging or selectively abandoned (many recent handsets will never receive and OS update.) iOS 5 promises to be made available to the current and previous generation(s) with no delay, without carrier interference and developers will be able to update their apps to quickly take advantage of new OS features and be released at the same time as the OS update.

    How “updating” affects technology being pushed forward and subsequently a platform’s competitiveness will be interesting to watch.

  • http://www.inlevel.com I.L.

    Apart from the Android forking problem on handsets mentioned by MarkHernandez, there is also the issue with tablet-focused Android 3.0. It is quite another beast than the rest of the pack.

    And as reviews of Xoom show, it still requires improvements to be able to successfully compete with iOS 4 powering iPads.

    As for the Chrome web store mentioned in the article, there is a need for marketplaces for web apps, but I’m not sure Google is going here in the right direction.

  • http://www.smc-seo.co.uk Stuart Mark Condé

    This is interesting. I’ve had people telling me I should be using various Google technologies over the years such as Wave and, looking at this article, I’m glad I didn’t invest the time.

    However, I guess if you’re blasting out ideas at the rate that Google does, your going to have a few failures.

  • http://www.exittoshell.com Tim M.

    What was once Google Gears has been fully absorbed into modern web browsers under the catch-all label of HTML5. So I would call much of that work a success, but not as a discrete product.

  • WaltFrench

    I’d sure love to hear some success stories about the benefits-vs-costs of Honeycomb adaptation. Some success stories, not just how much “tonnage” looks great for having been done. Seems that developers who want to support the tablet space might better stick with a Froyo code base so they can address BlackBerry, Xoom, Nook, Sammy & others, dealing with different resolutions by hand.

  • http://norskben.posterous.com norskben

    quite accurate ;P especially on appengine, and android (of course)

  • http://tobiascohen.com Tobias Cohen

    Google left a lot of people in the lurch when they abandoned Gears, including their own Gmail service. HTML5 simply can’t do everything that Gears can do, even in the latest browsers.

    Most of the “apps” in the Chrome web store are nothing more than bookmarks to existing web apps, with no additional features or functionality.

    App engine is definitely a success, I know a lot of projects are using it, although who knows how they’ll cope if/when Google decides to shut it down like many of their other projects.

  • jamiekeaney

    Google needs to adopt the “fail quickly” approach in their products!