Chromebooks can now run some Android apps for the first time, including Evernote and Vine
We knew that Google planned to add support for running Android apps on Chromebooks since the company announced it back at Google I/O in June, but today we've had confirmation that the first Android apps …
Context & Ripple Effects
Google confirmed today that the first Android apps are running on Chromebooks, with Evernote and Vine as the launch titles — delivering on what the company previewed at Google I/O in June 2014. The pickup was unusually broad for a feature announcement: Google's own Chrome Blog plus Ars Technica, The Verge, PC Magazine, The Register, Electronista, BetaNews and Google Operating System all carried it the same day.
The move completes a loop Google opened in January, when it brought Chrome apps to Android and iOS and let developers ship them through both mobile stores. With Android apps now flowing the other way onto Chrome OS, Google's two platforms are starting to converge from opposite directions, and the long-standing 'app gap' criticism aimed at Chromebooks gets its first concrete answer.
First-order effects
- Chromebook owners gain access to their first native Android apps — Evernote and Vine — rather than web-app substitutes, immediately strengthening the machines' software story for buyers weighing them against Windows laptops.
- Developers who have already shipped Android versions get a new desktop-class surface for existing code through the App Runtime for Chrome, lowering the marginal cost of reaching Chrome OS users.
Second-order effects
- Microsoft faces renewed pressure at the low end of the laptop market, where Chromebooks' main weakness has been app availability rather than price or battery life; narrowing that gap forces Windows to compete on merits beyond cost.
- Evernote and Vine effectively become test cases: if their ports perform well, other large Android developers face user expectation — and a ready runtime — to follow onto Chrome OS.
Third-order effects
- If the runtime approach holds, the distinction between 'Android device' and 'Chromebook' starts to dissolve at the app layer, pushing the industry toward fewer, broader app targets instead of one codebase per OS — with Google controlling the bridge on both ends.
- A credible Android-on-Chrome path also repositions Chromebooks in enterprise and education procurement, where the app gap has been the standard objection, shifting the competitive frame toward ecosystems rather than individual devices.
The trend: Google is merging its mobile and browser OSes into a single app ecosystem, with Android apps becoming the shared runtime layer across form factors.