Chrome 42 will be the last version to support Android 4.0 Ice Cream Sandwich
Emil Protalinski / VentureBeat :
Context & Ripple Effects
With Chrome 42, Google draws its first mobile line in the sand on legacy platforms: Android 4.0 Ice Cream Sandwich devices stay frozen on that build while everyone else keeps getting updates. It is the opening move in a broader culling — months later Google would announce it was retiring Chrome support for Windows XP, Vista, and older Mac versions in April 2016, applying the same end-of-support logic to desktop.
The move matters because Chrome functions as Google's most direct lever over what software runs on old hardware, and because security work is the stated currency: the same year, Google joined Microsoft and Mozilla in coordinating the removal of RC4 encryption across all major browsers, showing how quickly legacy support decisions ripple through the whole browser ecosystem.
First-order effects
- Ice Cream Sandwich users are cut off from future Chrome releases and their security fixes immediately after version 42 ships, leaving them to choose between an outdated browser, a third-party alternative, or new hardware.
Second-order effects
- Competing browser vendors inherit the stranded-ICS user base but face the same rising cost of supporting a 2011-era Android stack, pressuring them toward parallel cutoff decisions rather than a durable advantage.
Third-order effects
- The pattern hardens Chrome's release cadence into a de facto forcing function for OS upgrades — a role confirmed by the desktop retirements and by Android itself, where even flagship phones like the OnePlus 3 got only a few years of updates before Android O marked their last major version.
The trend: Browser support lifecycles are becoming the mechanism that retires legacy operating systems, with Google's Chrome cadence setting the pace on both mobile and desktop.