Android Orphans: Visualizing a Sad History of Support
The announcement that Nexus One users won't be getting upgraded to Android 4.0 Ice Cream Sandwich led some to justifiably question Google's support of their devices. I look at it a little differently: Nexus One owners are lucky.
Context & Ripple Effects
When Google launched the Nexus One in January 2010 it was sold directly by the company as its own flagship — the device that was supposed to define what Android should be, as O'Reilly Radar's early take on the Nexus One launch noted. By November 2010 the follow-up Nexus S had already pulled back to a safer, retail-carrier model, per GigaOM's coverage of how Google looked to play it safe with the Nexus S.
This week Google confirmed the Nexus One will not receive Android 4.0 Ice Cream Sandwich, and The Understatement's response is a timeline visualization of Android update support across devices — picked up the same day by BGR as an infographic on fragmentation. Its contrarian framing: against the update record of most Android handsets, Nexus One owners are actually the lucky ones.
First-order effects
- Nexus One owners now have a confirmed end-of-life for OS upgrades roughly 21 months after launch, capping the device at Gingerbread-era software despite it being Google's own branded phone.
- Google's update decision lands just as Ice Cream Sandwich ships, making the Nexus S — not the Nexus One — the reference device that demonstrates the new OS.
Second-order effects
- The visualization implicitly indicts carrier and OEM update pipelines more than Google's own: if even the Nexus One looks well-supported by comparison, Samsung, HTC and Motorola devices with slower or absent upgrades face renewed scrutiny from buyers choosing their next handset.
- Google's incentive to keep the Nexus program as a controlled, first-party update channel strengthens, since the program's credibility as 'the phone that gets updated' is now the main differentiator it can point to.
Third-order effects
- If the pattern holds, Android's structural split deepens between Google-controlled reference hardware that tracks new releases and the fragmented OEM/carrier installed base that lags — turning update policy into a purchasing criterion rather than an afterthought.
- Sustained fragmentation pressure points toward Google asserting more control over the Android experience through hardware and services rather than relying on partners to deliver timely OS updates.
The trend: Android's widening update gap is pushing Google to treat first-party Nexus hardware as the only reliable delivery vehicle for new OS versions.