Android 4.0 now on 7.1 percent of devices, still woefully behind previous versions
Google tracks the different version numbers of Android devices that access Google Play (nee Android Market) and every month or two we check in to see how the latest versions are doing.
Context & Ripple Effects
Ice Cream Sandwich has gone from roughly 0.6 percent of devices — about a million handsets in Google's January distribution snapshot to 7.1 percent by June, real growth that still leaves Android 4.0 trailing every earlier version still in circulation. The Verge's monthly check-in on Google Play device data is the running scoreboard for how fast new Android releases actually reach users.
The slow ramp lands on ground Technologizer flagged back in 2010, when 'the worst Android fragmentation is yet to come' argued that carrier and manufacturer update control would strand new versions on a minority of devices. With ComScore putting Android at 51 percent of US smartphones as of May, the stakes are scale: a report of a blame dispute between AT&T and Google over phones failing to receive updates — unconfirmed, but circulating in May — points at exactly the pipeline fragmentation critics named.
First-order effects
- Developers shipping to Google Play cannot target Android 4.0 alone: with 92.9 percent of devices on older versions, apps must still be built against Gingerbread-era capabilities, capping what the newest APIs are worth.
- Carriers and handset makers take the reputational hit for the gap — the rumored AT&T–Google dispute over undelivered updates shows update delivery becoming a public blame game rather than a quiet operational detail.
Second-order effects
- Update speed turns into a competitive differentiator between OEMs: whichever manufacturer gets ICS onto its flagship line fastest can market currency of platform against slower rivals, pressuring the rest to shorten their own rollouts.
- The split installed base raises Android development costs relative to a single-version target, nudging developer attention toward whichever platform or device segment lets them ship one build.
Third-order effects
- If each release keeps taking quarters rather than weeks to reach even a tenth of devices, Google's ability to steer its own platform weakens relative to the carriers and OEMs who control the last mile — the structural outcome the 2010 fragmentation argument predicted.
- Persistent lag creates pressure on Google to move functionality out of the OS and into updatable services and apps, so new features reach old phones without waiting on carrier-certified firmware.
The trend: Android's version adoption is settling into a pattern where each release's reach is set less by Google's launch than by carrier and OEM update pipelines, making fragmentation a permanent feature of the platform's scale.