Android (operating system)

Lore & Background

Android Inc. Steve Perlman provided early seed funding. for at least $50 million, with key employees joining Google. The operating system's source code is known as the Android Open Source Project (AOSP), which is free and open-source, though most devices run Google's proprietary version with additional closed-source software like Google Mobile Services.

Reader's Guide

Its open-source core (AOSP) has enabled a wide ecosystem of devices, including Android TV, Wear OS, Android Automotive, Android XR, and Android for PCs, as well as numerous modified distributions like Amazon Fire OS and LineageOS. The operating system's flexibility and Google's ecosystem—including Google Play, Google Chrome, and Google Play Services—have made it the foundation for the majority of smartphones worldwide. Android's history includes the Nexus series of devices, which introduced new software iterations and hardware standards, and the Google Play edition program. The platform's trademark is restricted by Google to certified products, while the source code remains freely available under the Apache License.

Did You Know?

• Android Inc. was originally founded to build an operating system for digital cameras, not phones.
• The first public Android versions were codenamed Cupcake and Donut, starting the dessert-themed naming tradition.

Origins: From Startup to Google's Mobile Bet

Android's story began well before Google's name became synonymous with mobile computing. started developing what would become the world's dominant mobile operating system. Before any public release, the software went through at least two internal iterations within Google and the Open Handset Alliance. Because no physical hardware existed yet, early testing relied entirely on software emulation. Both the operating system and its SDK were distributed as free software under the Apache License, with source code made openly available. Notably, the internal codenames "Astro Boy" and "Bender" that appeared on pre-1.0 milestone builds were never used as official release names.

The Dessent Naming Era and Its End

One of Android's most recognizable cultural touches was its dessert-based naming scheme. From that point forward, every major release carried a sweet-treat identity: Donut, Eclair, Froyo (short for frozen yogurt), Gingerbread, Honeycomb, Ice Cream Sandwich, Jelly Bean, and so on through the alphabet. The theme gave each version a memorable, approachable personality that resonated with both developers and consumers. However, the alphabetical progression eventually ran into practical limits. This marked a significant departure from the playful branding that had defined the platform's public identity for roughly a decade, signaling a maturation in how Google communicated its software releases to the world.

Release Cadence and the Developer Compliance Framework

The typical cycle involves announcing the next version at the Google I/O developer conference in May, accompanied by the opening of beta testing. The stable, public-facing build then arrives between August and October, giving developers a consistent window to adapt their applications. Beyond the release calendar, Google has enforced increasingly strict developer compliance. These targeting obligations have since expanded to cover Wear OS, Android TV, and Android Automotive OS, each granted a twelve-month grace period before the requirement takes effect. This framework ensures the broader ecosystem keeps pace with the platform's evolution.

Milestone Releases and the Deepening Technical Foundation

Several Android releases stand out as technical turning points. It represented a dedicated design philosophy for larger screens rather than a simple phone OS scaled up. Google's Gabe Cohen noted it was "theoretically compatible" with any 2.3.x device in production. The underlying Linux kernel also evolved steadily, progressing from 2.6.27 in Cupcake through 3.0.1 in Ice Cream Sandwich to 3.4.0 by Jelly Bean 4.2, reflecting the platform's deepening technical foundation.