How android became the world's most used mobile OS while staying open-source.
Giving away the operating system was the strategy, not a side effect. Google kept the license free and built a proprietary services layer on top — a split that still shapes how mobile engineering teams get hired and structured today.
Two Audiences
If you're building a mobile team, this history explains a hiring problem you've probably already hit: candidates who list "Android" on a resume span two very different skill sets. Some know the AOSP layer — kernel, runtime, low-level systems work. Others know the GMS layer — Play Services, push, billing, location. Rarely both. Writing a job description that conflates the two is the fastest way to attract the wrong candidate.
Yochana screens for which layer a candidate actually operates in, plus whether they've dealt with real-world fragmentation across OEM skins and OS versions — not just shipped a single app to a single reference device.
If you work across both AOSP and GMS, or specialize in device-compatibility and fragmentation testing, that's a more specific and more marketable skill set than "Android developer." Say so explicitly — which layer, which OEM ecosystems, which markets.
Experience with budget-hardware optimization or GMS-light environments (China, parts of APAC) is a genuine differentiator most candidates can't claim.
The Problem Android Solved
Before 2008, phone manufacturers had two bad options: build a proprietary OS from scratch, or license Windows Mobile and pay per-device fees to Microsoft. Symbian and BlackBerry OS were aging and hard to extend. None of this worked for the budget and mid-range manufacturers who would soon drive smartphone growth across India, China, Southeast Asia, and Latin America.
Google released the Android Open Source Project under the Apache License 2.0 — free to take, modify, and ship. That single decision removed the biggest cost barrier standing between a hardware maker and a smartphone product.
Two Layers, Only One Is Free
AOSP — The Open Layer
The genuinely free, modifiable core: kernel, runtime, base UI framework. Anyone can fork it — Amazon's Fire OS and various GMS-free Android builds sold in China are proof.
GMS — The Controlled Layer
The proprietary bundle on top: Play Store, Gmail, Maps, YouTube, and the Play Services libraries most third-party apps depend on. Manufacturers need a signed licensing agreement with Google to access it.
Fragmentation — The Trade-off
Freedom to fork means Google doesn't fully control every derivative in the wild — the direct cause of the device and OS-version fragmentation Android QA still deals with today.
Why Everyone Said Yes
| Stakeholder | What Android Offered |
|---|---|
| Phone manufacturers | A free, customizable OS base — Samsung, Xiaomi, OnePlus build skins like One UI and MIUI without OS development costs |
| Budget / emerging-market OEMs | A viable smartphone product at price points proprietary licensing could never support |
| App developers | One dominant, standardized target platform, despite device fragmentation |
| Carriers | Devices across every price tier, from ultra-budget to flagship |
Apple kept iOS closed and exclusive to its own hardware — leaving Android as the default OS for essentially every other manufacturer, which over time became most of the global device volume.
What This Means for Building Android Teams
- Fragmentation is a permanent hiring consideration — QA and compatibility testing across OEMs, OS versions, and screen classes is an ongoing skill requirement, not a solved problem
- GMS expertise is distinct from AOSP expertise — push, billing, and location work is a different discipline than kernel or low-level systems work
- Regulatory shifts affect the roadmap — EU antitrust rulings on GMS bundling have already changed how some manufacturers ship devices
- Emerging-market device diversity is specialized — budget-hardware and GMS-light optimization is a different skill than flagship-device development
Frequently Asked
The AOSP core is free under Apache 2.0. Access to Google Mobile Services — Play Store, Gmail, Maps — requires a separate licensing agreement with Google, which includes compatibility requirements.
Because manufacturers are free to fork and customize AOSP, Google can't fully standardize every device in the wild — the same openness that drove adoption also produced the fragmentation problem.
An AOSP engineer works on the open-source core — kernel, runtime, system UI. A GMS engineer works with Google's proprietary services layer — Play Services, push notifications, billing, location. The two skill sets rarely overlap fully.
By screening for which layer — AOSP or GMS — a candidate actually operates in, and for real fragmentation and multi-OEM experience, rather than a generic "Android developer" resume line.
Building an Android or mobile engineering team?
Yochana places specialized IT talent across mobile, cloud, and platform engineering, with a 15 to 20 day average fill time.
Talk to Yochana
