Google's iron grip on Android: Controlling open source by any means necessary
Android is open—except for all the good parts. — Six years ago, in November 2007, the Android Open Source Project (AOSP) was announced. The original iPhone came out just a few months earlier …
Context & Ripple Effects
The arc here is long and well-documented in our own coverage: Google announced the Android Open Source Project in November 2007 and shipped it publicly a year later (Android became available as open source in October 2008), promising an openly developed mobile platform to counter the iPhone. But cracks showed early — Freedom to Tinker argued back in September 2009 that the Android open-source model had a short circuit, with key development happening behind closed doors before code drops.
Oracle's 2010 lawsuit over Java (Oracle v Google) added a legal dimension to how much of Android Google actually controlled. Ars Technica's October 2013 piece crystallizes that critique — Android is open 'except for all the good parts' — and it traveled unusually far for an analysis post, drawing same-day amplification from investors and builders including Bill Gurley, Chris Dixon, Anil Dash, and Matt Rosoff.
First-order effects
- Device makers who ship AOSP without Google's proprietary layer get an OS missing the apps consumers actually buy phones for, making Play Store access — and acceptance of Google's terms — effectively mandatory for mainstream handset vendors.
- Google keeps de facto control of the platform roadmap while carrying none of the traditional obligations of an open-source steward, since the valuable components (apps, services, brand) sit outside the Apache-licensed core.
Second-order effects
- Rivals can weaponize the gap: any competitor pitching carriers and OEMs an alternative platform has a ready-made argument that Google's 'open' Android is contractually gated, and the confirmed commentary around this story that 'Android first' is a myth for startups reinforces where developer gravity actually sits.
- Hardware partners face sharpening dependence — the more essential Google's closed app bundle becomes to selling Android handsets, the more pricing and feature leverage Google holds over Samsung and other licensees in negotiations.
Third-order effects
- If the pattern holds, 'open source' hardens into a distribution strategy rather than a governance commitment: a permissively licensed kernel surrounded by proprietary chokepoints, a template other platform companies can replicate.
- A platform whose openness is nominal invites scrutiny — from regulators weighing tying of Play Store access to OEM terms, and from fork-makers testing whether the license commitments are enforceable — though whether that scrutiny materializes is genuinely unresolved at this point.
The trend: Mobile platforms are converging on 'governed openness' — permissive open-source cores wrapped in proprietary services and compatibility requirements that keep effective control with the sponsor.