A short history of Android versions, from Cupcake to today
From the first Android phone to modern numbered releases: the dessert names, the milestones that mattered for apps, and why your version number still counts.
Almost every Android phone you see today runs a version of the same system that began on a single handset in 2008. Along the way, Android changed its look, its rules for apps and even the way it names its releases. This short history walks through the main stages, keeping to well-known facts, so that the version number on your phone tells you something real.
Where Android came from
Android started as a small company, Android Inc., which Google acquired in 2005. The first commercial Android phone, the HTC Dream, which some markets sold as the T-Mobile G1, arrived in 2008 together with the first public release, Android 1.0. It had a touch screen with a slide-out keyboard and an app store of its own, and it set the pattern: a shared system that many phone makers could use.
A key part of that pattern is that the core of Android is released as open source, known as the Android Open Source Project. Phone makers take that base, add their own design and extras, and ship it. That is why menus look different on different brands, and why updates reach phones at different speeds.
The dessert names
For many years each major release carried the name of a dessert, and the names followed the alphabet.
- Cupcake, Donut, Eclair, Froyo and Gingerbread covered the early years, when Android grew from a niche system into a mainstream one.
- Honeycomb was a release made for tablets.
- Ice Cream Sandwich brought phones and tablets together under one design.
- Jelly Bean, KitKat and Lollipop followed. KitKat aimed to run well on phones with little memory, and Lollipop introduced the Material Design look.
- Marshmallow, Nougat, Oreo and Pie came next.
In 2019, Google stopped using dessert names publicly and began calling releases by number alone, starting with Android 10. Newer versions simply continue the count.
Milestones that changed how apps work
Some releases mattered more to app users than others.
- Marshmallow introduced runtime permissions. Instead of accepting a long list when installing, you were asked for access such as the camera or location at the moment an app needed it, and you could change your mind later.
- Oreo added notification channels, which let you silence one kind of notification from an app without turning off all of them.
- Pie introduced gesture navigation as an option, and Android 10 brought a system-wide dark theme.
- Later versions continued to tighten privacy, limiting what apps can do in the background and how they reach your files.
Why your version number still matters
New Android versions bring new rules, and apps are updated to follow them. An app built for a recent version may not install on a much older phone, and an old app may behave differently on a new phone. That is the reason app pages list the minimum Android version they support. Security fixes also arrive with updates, so a phone that no longer receives them is more exposed over time. Check your own version in Settings, under About phone (the exact menu name differs by brand).
Common misunderstandings
- A higher number is not automatically better for you. A phone with limited memory may run an older, lighter version more smoothly.
- The dessert names were nicknames used by the project. The numbers were always the real version identifiers.
- Every maker updates on its own schedule. Two phones on the same Android number can still differ in features.
- A new version does not make older apps unsafe by itself, but apps that are never updated can fall behind on fixes.
Looking ahead
Android's story is one of steady change: from a single phone to billions of devices, and from a few simple apps to a huge range of tools. Knowing the broad shape of that history helps you read compatibility notes and choose apps that suit your phone. For more practical guides, visit the BoldAPK home page.
Comments
Loading comments…