Google gears for mobile?

Google Gears is a great development .. Not just in itself, but for the Web as a whole. I have always been a fan of Google and my next thought would be .. How about Google Gears for mobile?

It sounds very logical to me .. and a great move for the Mobile Web.

Not only will this benefit Google Apps .. but in my view, it would also benefit the Mobile Web – especially if, we , as developers can extend this to the mobile platform ..

I need to understand Google’s roadmap a bit more on this, but I dont see why not .. and it has clear benefits for us as an industry ..

Adds Bryan Rieger at forumoxford ..

Seeing as it’s open source and they’re talking about submitting it to a standards body I’m sure it’s only a matter of time before Nokia creates an S60 version, and Opera (or NetFront) incorporates it into their mobile offerings.

I’ve seen a couple of projects doing something similar with Python (Flash Lite -> Flyer), but the Gears API/plugin seems to make the whole local storage thing much, much easier (and cleaner)

Watch this space I say!


  1. Vinu says:

    Hey Ajit,
    I had actually twttrd about it yesterday :) not thinking on the same line are we?

  2. Paul Golding says:

    Offline storage is an old technique of the mobile world and was essential to so many prehistoric apps, simply because the network connection was unreliable. In that sense, it goes against the philosophy of “always connected” computing that mobile has always aspired to.
    Where it will prove useful in mobile web contexts is if it can be used to cache data, such as large image uploads, until such time as certain network conditions are met, such as within WiFi coverage rather than 3G/GPRS coverage. In this sense, local cache is a seamless mobility technology.
    This means that network coverage is still possible, but the web application chooses not to upload large data sets until the coverage meets certain conditions. This is a slightly different model than pure online/offline computing. It is a hybrid and such a model would be extremely useful for mobile web applications.
    An example would be using Gmail on the move. I want to check my mail, compose messages etc, but I don’t want the 5MB powerpoint I just attached to actually get sent because it will cost too much or take too long. However, I still want to continue as if I’m using the app as normal, without having to change my work pattern to suit my network connection.
    That’s a stodgy corporate example. Uploading a video to Youtube might be more sexy.

  3. Ajit Jaokar says:

    thanks Paul, Venu. Considering todays announcement(see below) .. that post may be wierdly prophetic!