/
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

KitKat is now on almost 40% of Android devices - but Lollipop is still stuck under 0.1%

Andy Weir / Neowin :

Neowin Andy Weir

Context & Ripple Effects

Google's own distribution numbers show the update pipeline barely moving: Lollipop, launched in late 2014, is still on fewer than one in a thousand devices, while 2013's KitKat holds almost 40%. The bottleneck is structural — every Android release has to clear manufacturers and carriers before it reaches handsets, so each new version starts from near zero.

Later coverage confirmed the pattern wasn't a launch hiccup: Marshmallow managed just 2.3% share more than a year after its release, and even eight months post-launch it took that long to pass 10%. This snapshot is the earliest data point in that arc.

First-order effects

  • Developers targeting Lollipop APIs are writing for an install base of effectively zero, so apps ship against KitKat compatibility regardless of what Google's latest platform offers.
  • OEMs and carriers holding Lollipop rollups face pressure from early adopters while their installed base stays overwhelmingly on KitKat.

Second-order effects

  • With new versions reaching devices this slowly, security fixes and platform features arrive years late for most users — the fragmentation tax falls on buyers, not on Google or the handset makers who cause it.
  • Manufacturers compete on hardware specs rather than software currency, since shipping the newest Android is no longer a realistic differentiator when rivals' flagships run two-year-old versions.

Third-order effects

  • If every release follows the same multi-year crawl, Android permanently splits into a fast-moving developer platform and a slow-moving consumer base — a dynamic Google itself eventually acknowledged by quietly winding down monthly distribution dashboard updates once the numbers stopped flattering anyone.

The trend: Android version adoption keeps decoupling from release cadence — each generation spends years stuck behind manufacturer and carrier update pipelines, making fragmentation a permanent feature of the ecosystem rather than a transitional problem.