/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

What's powering Web apps: Google waving goodbye to Gears, hello to HTML5 [Updated]

Of all the things Google is really good at, patience isn't necessarily one of them.  —  To prove Web applications like Gmail and Google Docs could be as sophisticated as desktop apps …

L.A. Times Tech Blog Mark Milian

Context & Ripple Effects

Gears has been on borrowed time for a while in this corpus: the plug-in was framed as 'replacing one problem with another' back in June 2007, and even a sympathetic re-examination in October 2008 treated it as a stopgap rather than a destination. Google's own framing at launch — that offline-capable Web apps like Gmail and Google Docs should rival desktop software — always implied the workaround would be retired once browsers caught up.

The retirement now lands alongside a broader platform push: just weeks earlier, on November 9, 2009, coverage asked whether Google would extend Wave's real-time collaboration across all its apps, which reads as the same strategy viewed from the product side — build app sophistication into the platform rather than bolt it on via plug-in.

First-order effects

  • Gears users and developers who built offline functionality on the plug-in face a deprecation path: Google is signaling that new investment goes to HTML5 equivalents (local storage, offline modes) inside Gmail and Google Docs, not Gears maintenance.

Second-order effects

  • Browser vendors become the decisive layer: if Google stops shipping Gears, Firefox and IE users get offline-capable Google apps only as fast as those browsers adopt the relevant HTML5 features, pressuring them to implement the spec or lose engagement with Google's suite.

Third-order effects

  • The pattern points toward browser-native capabilities replacing vendor plug-ins as the way Web apps reach desktop parity — a shift that concentrates power in whoever controls the browser engine, and that Google is positioned to accelerate given its own Chrome efforts.

The trend: Web applications are migrating from vendor-specific plug-ins toward standardized HTML5 capabilities, with Google using Gmail and Docs as the forcing function for the transition.