Android Codenames Explained: From Cupcake to Vanilla Ice Cream

Introduction

For a decade, every new Android version came with a dessert name and a statue on Google’s Mountain View campus. Cupcake, Donut, Eclair, Froyo, Gingerbread, Honeycomb, Ice Cream Sandwich, Jelly Bean, KitKat, Lollipop, Marshmallow, Nougat, Oreo, Pie. The alphabetical sequence was as much a part of Android’s identity as the green bugdroid.

Then, in 2019, Google killed it. Android 10 had no public dessert name. The statues stopped. The alphabetical guessing game — “What will Q be? Quiche? Queen Cake? Quince Tart?” — ended without ceremony.

But the codenames didn’t die. They just went underground. Every Android version since 10 has had an internal dessert codename, used by Google engineers in AOSP commits, build strings, and leaked documents. This is the complete story of every Android codename, public and private, from the beginning to today.


The Complete Codenames List

VersionPublic NameInternal CodenameLetterYear
1.0(none)Alpha2008
1.1(none)Petit Four2009
1.5CupcakeCupcakeC2009
1.6DonutDonutD2009
2.0–2.1EclairEclairE2009–2010
2.2FroyoFroyo (Frozen Yogurt)F2010
2.3GingerbreadGingerbreadG2010–2011
3.0–3.2HoneycombHoneycombH2011
4.0Ice Cream SandwichIce Cream SandwichI2011
4.1–4.3Jelly BeanJelly BeanJ2012–2013
4.4KitKatKey Lime Pie → KitKatK2013
5.0–5.1LollipopLemon Meringue Pie → LollipopL2014–2015
6.0MarshmallowMacadamia Nut Cookie → MarshmallowM2015
7.0–7.1NougatNew York Cheesecake → NougatN2016
8.0–8.1OreoOatmeal Cookie → OreoO2017
9PiePistachio Ice Cream → PieP2018
10Android 10Quince TartQ2019
11Android 11Red Velvet CakeR2020
12–12LAndroid 12Snow ConeS2021–2022
13Android 13TiramisuT2022
14Android 14Upside Down CakeU2023
15Android 15Vanilla Ice CreamV2024

The Origin Story

The dessert naming tradition started as an inside joke. According to Dan Morrill, an early Android engineer, the internal builds of Android 1.0 were called “Alpha” and 1.1 was “Petit Four” — a small, sweet confection. When Android 1.5 was in development, the team needed a name. Someone suggested “Cupcake” — a small, sweet update after the rough 1.0 launch. The name stuck, and the alphabetical dessert sequence was born.

The public naming didn’t start until Cupcake. Android 1.0 and 1.1 were never publicly branded with dessert names. But internally, the tradition was already established, and by Donut, the media was eagerly speculating about what “E” would be.


The Branded Partnerships

Two Android versions involved actual corporate partnerships:

KitKat (2013): Google approached Nestlé with the idea of using the KitKat name. Nestlé agreed within 24 hours. The deal involved no money — just cross-promotional marketing. Nestlé produced 50 million Android-branded KitKat bars in 50+ countries. Google got a globally recognized, legally uncomplicated name. Internally, KitKat had been “Key Lime Pie” (KLP) until the Nestlé deal was finalized. References to KLP appeared in early Android 4.4 build strings and leaked ROMs. The switch was kept so secret that most Android engineers learned about it at the public announcement.

Oreo (2017): Google’s second brand partnership, with Mondelez International (owner of Oreo). Similar structure — no money changed hands, just cross-promotion. Oreo cookies featured Android-themed packaging. Internally, Oreo had been “Oatmeal Cookie” before the partnership.


The Internal Codenames That Almost Were

Several internal codenames were changed before public release:

  • Key Lime Pie → KitKat: The Nestlé deal replaced KLP. Key Lime Pie was referenced in AOSP commits and developer previews.
  • Lemon Meringue Pie → Lollipop: LMP appeared in early Lollipop AOSP commits. The switch to Lollipop was reportedly because “Lemon Meringue Pie” was too long and too specific.
  • Macadamia Nut Cookie → Marshmallow: MNC was the internal codename. Marshmallow was simpler and more universally recognized.
  • New York Cheesecake → Nougat: NYC appeared in early Nougat builds. Nougat was shorter and more internationally friendly.
  • Oatmeal Cookie → Oreo: The Mondelez partnership replaced OC.

Why Google Killed the Public Dessert Names

In August 2019, Google announced that Android 10 would simply be “Android 10” — no public dessert name. The official reasons:

  1. Global accessibility: Dessert names aren’t universally recognized. “Lollipop” isn’t a word in every language. “Pie” is an American-centric concept. The alphabetical sequence created confusion about version order in markets where the Latin alphabet isn’t primary.
  2. Inclusivity: Some desserts aren’t globally available or understood. What’s familiar in the US or Europe might be unknown in Asia, Africa, or South America.
  3. Simplicity: “Android 10” is clearer than “Android Quince Tart” for the average consumer. The numbering is unambiguous and works in every language.

The real reason, unstated but obvious: Google was running out of good Q desserts. Quiche isn’t a dessert. Queen Cake is obscure. Quince Tart is unfamiliar to most people. The alphabetical constraint was becoming a liability.


The Statues

From Cupcake through Pie, every Android version got a physical statue on the lawn of Building 44 at Google’s Mountain View campus. The statues became a tourist attraction and a media tradition — tech journalists would make pilgrimages to photograph the latest addition.

The statues included:

  • A giant cupcake with the bugdroid on top
  • A donut with a bugdroid emerging from the hole
  • A long éclair
  • A frozen yogurt cup
  • A gingerbread man
  • A honeycomb with a bee-like bugdroid
  • An ice cream sandwich bugdroid
  • A jar of jelly beans
  • A KitKat bar
  • A giant lollipop (so large it required structural reinforcement)
  • A marshmallow on a stick
  • A nougat bar
  • An Oreo cookie
  • A slice of pie

When Android 10 launched without a dessert name, the statue tradition ended. The Building 44 lawn still has the existing statues, but no new ones have been added since Pie.


The Legacy

The dessert codenames were a brilliant marketing move. They made Android feel playful and approachable at a time when mobile operating systems were sterile and corporate. The alphabetical guessing game generated free media coverage for every release. Tech blogs ran “What will K be?” prediction articles that drove engagement for months.

But the names also created confusion. Consumers didn’t know whether KitKat was newer than Jelly Bean. The alphabetical sequence wasn’t obvious to non-English speakers. And by 2019, the constraints of the format — finding a recognizable dessert for every letter — were becoming a burden.

The internal codenames continue. Google engineers still use dessert names in AOSP commits and internal documentation. The tradition didn’t die — it just went private. Android 16, whenever it arrives, will have an internal “W” dessert name that we’ll discover through leaked build strings and commit messages.

The statues still stand on the Building 44 lawn. The bugdroid still wears his green. And somewhere in Mountain View, a Google engineer is probably eating a waffle and thinking about Android 16.


References

  • Dan Morrill, “A History of Android Codenames” (internal Google presentation, later published)
  • Android Open Source Project commit history and build tags
  • Google Android 10 branding announcement (August 2019)
  • Nestlé S.A. / Google Inc. KitKat partnership documentation
  • Mondelez International / Google Inc. Oreo partnership documentation

Leave a Reply