From the very first Chrome OS reviews in 2009, one question never went away: why does Google run two operating systems? For sixteen years the official answer was some variation of “they serve different needs.” In 2025, the answer changed to: they won’t for much longer. Chapter twenty-one of our Chromebook history series covers the year the merger became real.
The slow reveal
The convergence had been visible for years to anyone watching the plumbing: Android apps in 2016, shared Bluetooth and virtualization stacks, and Google’s June 2024 statement that ChromeOS would adopt “portions of the Android stack.” In November 2024, reporting by Android Authority’s Mishaal Rahman went further: Google intended to migrate ChromeOS fully onto Android underpinnings, turning the years of quiet groundwork into a destination.
Confirmation came in stages through 2025. In June, Sameer Samat (Google’s president of the Android ecosystem) told an interviewer plainly that Google was “combining ChromeOS and Android into a single platform.” Then in September 2025, onstage at Qualcomm’s Snapdragon Summit, Samat made it unambiguous: Android would be the winner of the two-OS question, with users seeing results in 2026. Google framed the move around AI: building one platform where Gemini, agents, and Google’s models work identically across phones, tablets, and laptops, and around focusing engineering on a single stack.
What “merger” actually means
Google’s own clarification is the key sentence of this era: the plan is “taking the ChromeOS experience and re-baselining the technology underneath it on Android”, not turning laptops into big phones. In practice:
- The kernel, drivers, and app frameworks become Android’s; the desktop experience (windowing, shelf, browser-first workflow) is rebuilt on top.
- Android 16’s desktop windowing work, which shipped real resizable-window multitasking for big screens, serves as visible groundwork.
- The full Chrome browser and the Play Store ship together natively, ending the container gymnastics that made 2016’s Play Store arrival such an engineering saga.
- Job listings later in 2025 named the internal project, Aluminium OS, an “Android-based” system “built with AI at the core”, and court filings sketched the timeline: hoped-for release in 2026, testing possibly late that year, full maturity closer to 2028.
The reaction: hope, dread, and déjà vu
The ChromeOS faithful heard alarm bells: the platform’s superpowers (2009’s speed-simplicity-security trinity, stateless logins, self-healing updates) are properties of ChromeOS’s architecture, not obviously of Android’s. Skeptics also remembered Fuchsia, Google’s last grand OS unification that quietly shrank to smart displays. Optimists countered that Android’s app ecosystem, developer mindshare, and AI investment dwarf what ChromeOS could ever attract alone, and that Google was, for once, migrating the foundation while explicitly promising to keep the experience.
For owners, Google’s continuity message was concrete: existing Chromebooks keep their AUE update commitments, and ChromeOS releases continue through the transition. What the merger meant for the next device you’d buy: that story unfolds in our next chapters.
Why it still matters today
This is the hinge of the entire odyssey. Every earlier chapter (the ARM flexibility, the Play Store graft, Phone Hub, the Android stack adoption) reads in hindsight as an approach to this moment. The 2025 announcement resolved Google’s oldest structural ambiguity and set the terms for everything now on shelves: the continuing Chromebook line, the Googlebook launch, and the ten-year update promises that bridge owners across the divide.
FAQ
When was the Android-ChromeOS merger officially confirmed?
September 2025, by Android ecosystem president Sameer Samat at Qualcomm’s Snapdragon Summit, following his June 2025 statement that the platforms were being combined. Reporting had signaled the direction since November 2024.
What is Aluminium OS?
The internal name (revealed via job listings in late 2025) for the merged, Android-based platform with AI at its core, the system that debuted publicly with the Googlebook in 2026, covered in chapter twenty-three.
Will my Chromebook stop working because of the merger?
No. Google has committed that existing Chromebooks keep receiving ChromeOS updates through their published AUE dates, and new ChromeOS Chromebooks continue to launch during the transition.
Why did Google merge the two systems?
Officially: to build AI experiences once, on one platform, and to focus engineering effort. Structurally: maintaining two consumer operating systems was always redundant: the only question was which foundation would win, and Android’s scale answered it.
Next in the series: January 2026 — Gemini lands in Chrome on Chromebook Plus, and the Steam gaming dream quietly ends.
