- Android 16 will be codenamed "Baklava," breaking the traditional alphabetical dessert-naming sequence.
- The shift from a "W" dessert to "Baklava" for Android 16 reflects changes in how Google builds Android, making alphabetical order obsolete.
- With the entire alphabet now in play, future Android versions could feature a wider variety of dessert names, beyond alphabetical constraints.
For years, Google’s Android versions have been named after sweet treats, from Jelly Bean to Lollipop, with each codename following an alphabetical sequence. Although the dessert-themed names became less public in recent updates, the tradition has quietly continued behind the scenes. The latest Android 15, for instance, carries the internal codename “Vanilla Ice Cream.” But things are taking a surprising turn with Android 16.
Android’s sweet history: From Cupcake to Baklava as Android 16
The Android naming tradition started in 2009 with Android 1.5, known as Cupcake, and continued through various dessert names like KitKat, Marshmallow, and Oreo. However, each new Android version was alphabetically aligned with the alphabet letter corresponding to the dessert name. So, it looks like an exception for Android 16. Google, according to a recent leak, dropped the “W” dessert letter and settled on Baklava as the codename for Android 16.
The significance of ‘Baklava’ and new naming trends
Choosing “Baklava,” a popular layered pastry, signals a shift from the expected alphabetical sequence. So, why did Google go back to a “B” dessert for Android 16 instead of sticking with the traditional order? One explanation lies in Google’s evolving development approach. Since the introduction of the “trunk stable project” during Android 14 QPR2, Google revamped its naming convention for build IDs. This change moved away from alphabetical order, with build IDs starting with “A,” regardless of the Android version’s codename.
Google’s new development approach: flexibility in naming
Google’s recent changes in Android’s build structure mean that the strict alphabetical naming order is no longer necessary. With the release of Android 15, codenamed “Vanilla Ice Cream,” the build IDs begin with “A,” as seen in the AP1A and AP2A builds. Android 16’s build IDs are expected to start with “B,” which aligns with the choice of “Baklava.” This new flexibility allows Google to break free from the alphabetical constraints, giving the company more freedom to choose fun and unique codenames without sticking to a specific letter.
What’s next for Android codenames?
This means that from the very next version, Google can just select a dessert name without any reference to the alphabetical series. Android 16 brings “Baklava” to the table. It will be interesting to see what sweet surprises Google has up their sleeve for Android 17 and beyond.
