No More Offline Gmail in Google Chrome
Chrome 12, the upcoming version of Google's browser which is likely to be released today, removes a useful feature: the built-in Gears plugin. While most Google services dropped support for Gears and removed offline access, Gears is still being used in Gmail.
Context & Ripple Effects
Gears started as Google's answer to a web that couldn't work offline: the plugin Chrome shipped with let web apps store data locally, and it powered Gmail's offline mode when that graduated from Labs in December 2009. But by late 2009 Google had already signaled the endgame, waving goodbye to Gears in favor of HTML5, and most Google services dropped the plugin even though Gmail still depended on it.
With Chrome 12, Google removes the built-in Gears plugin entirely — which means Gmail loses its only offline mechanism before an HTML5 replacement ships, leaving users of the world's most-used webmail client without offline access in Google's own browser.
First-order effects
- Gmail users on Chrome lose offline reading and composing entirely once Chrome 12 lands, since Gears was the technology behind the Labs-graduated offline mode.
- Any remaining web apps still relying on Gears break in Chrome 12, forcing developers who hadn't migrated off the deprecated plugin to scramble.
Second-order effects
- Google faces immediate pressure to ship HTML5-based offline replacements for Gmail, Calendar, and Docs faster than its original timeline, because its own browser just cut off a flagship product's feature.
- Competing browsers and app vendors watching Gears die get confirmation that building on proprietary browser plugins is unsafe — pushing their roadmaps toward standard HTML5 offline APIs.
Third-order effects
- If the pattern holds, browser makers stop shipping capability through bundled plugins altogether, and offline web access becomes a standards-defined feature every browser must implement rather than a single vendor's extension.
- That shift hands leverage to standards bodies over Google's own extensions: the company that pioneered offline web apps now has to get the features it wants ratified into HTML5 instead of shipping them unilaterally.
The trend: Browser capabilities are migrating from proprietary plugins like Gears to open HTML5 standards, with Google deliberately breaking its own products' dependencies to force the transition.