For seven years, every Chromebook review contained the same sentence: “but it only runs web apps.” At Google I/O in May 2016, that sentence expired. Google announced that the entire Google Play Store, over a million Android apps, was coming to ChromeOS. Chapter eight of our Chromebook history series covers the platform’s biggest software shift ever.
The road to I/O 2016
Google had been circling this idea for years. A 2014 project called ARC (App Runtime for Chrome) let a handful of hand-picked Android apps (Vine, Evernote, Duolingo) run on ChromeOS, but compatibility was poor and the catalog never grew. The lesson was clear: cherry-picking apps didn’t work. Either the whole Play Store came over, or none of it mattered.
The engineering answer was ARC++: the complete Android framework running inside a Linux container, sharing the ChromeOS kernel but isolated from the rest of the system. Not an emulator (Android apps ran at native speed) and not a security compromise, because the container preserved ChromeOS’s sandboxing model. The architecture details still matter when things go wrong; our guide to Play Store error codes on Chromebooks is, in a sense, documentation of ARC++’s seams.
The rollout: slow, bumpy, irreversible
Google named three launch devices: the ASUS Chromebook Flip C100 (the little convertible from our previous chapter, suddenly promoted to historic significance), the Acer Chromebook R11, and the 2015 Chromebook Pixel. Support reached them through 2016 in the Chrome 53 era, then spread across the lineup; by 2017, Google committed that essentially all new Chromebooks would ship Play-Store-capable.
Early reality was messy. Most Android apps were phone-shaped: they opened in tiny portrait windows, handled keyboards badly, and occasionally crashed the container. Resizing an Android window was an adventure. Reviewers who’d spent years asking for “real apps” now complained the real apps felt wrong on a laptop, and fairly so. It took years of releases to make windowing, scaling, and input feel native.
What Android apps actually changed
- The offline argument died. Word, Excel, Photoshop Express, Netflix downloads, offline games: the “useless without Wi-Fi” criticism lost its teeth. (Today’s offline options are covered in our using a Chromebook offline guide.)
- Hardware followed software. Touchscreens went from Pixel luxury to baseline expectation; convertibles became the premium default; stylus support appeared. Every Chromebook designed after 2016 assumes fingers will touch it.
- Storage and specs grew up. Apps need space and RAM, pushing typical configurations from 16GB/2GB toward 64GB/4GB and beyond.
- The identity changed. A Chromebook was no longer a browser appliance; it was a laptop that ran a mobile ecosystem plus the web. That repositioning set up every future step: Linux support, gaming ambitions, and ultimately the Android merger this series ends with.
Why it still matters today
ARC++ was the first time Google grafted Android onto ChromeOS, and the graft’s success quietly answered the decade-old “why two operating systems?” question with “maybe there shouldn’t be.” The 2025 announcement that ChromeOS would be rebuilt on an Android foundation (chapter 21 of this series) is the 2016 decision followed to its logical end.
For users, the practical legacy is simple: installing Android apps is now as central to owning a Chromebook as the browser itself. The browser-only computer Google announced in 2009 lasted exactly seven years.
FAQ
When did Chromebooks get Android apps?
Announced at Google I/O in May 2016, with the first stable rollouts reaching the ASUS Flip C100, Acer R11, and Chromebook Pixel 2 later that year, then expanding across the lineup through 2017.
Do all Chromebooks run Android apps?
Essentially every Chromebook released since 2017 supports the Play Store. Models from 2016 and earlier vary, and all of those are now past their update expiration anyway.
What was ARC++?
The container-based architecture that ran the full Android framework inside ChromeOS at native speed while preserving sandbox security. It replaced the failed app-by-app ARC experiment of 2014 and was itself later succeeded by a VM-based design (ARCVM).
Why did it take seven years to bring apps to ChromeOS?
Partly philosophy (the founding vision was deliberately web-only) and partly engineering: running all of Android securely inside another OS without emulation required container technology that matured in the mid-2010s.
Next in the series: Google returns to premium hardware with the Pixelbook — thin, gorgeous, $999, and finally with an ecosystem to justify it.
