Google’s Internal Name For Android M Is Macadamia Nut Cookie

First and foremost, Memorial Day is a U.S. federal holiday in which Americans pay tribute to all who have fallen while serving in the country's armed forces, a day of solemn remembrance and reflection. Curiously, Memorial Day is also a day of celebratory ingestion, involving burgers, barbecue, beer, baked beans...and this year, all thanks to Google, Macadamia Nut Cookies. 

macadamianutcookies

On Saturday we learned that the successor to Android Lollipop has been saddled with the internal code name "Macadamia Nut Cookie" (or MNC, for those looking to save on syllables). The name, which is already being referred to in the Android Open Source Project (AOSP, again for those looking to save on syllables) and which is already in common use by the good folks at Google, adheres to the same scrumptious naming convention employed for the last two name Android releases, Key Lime Pie (KLP) and Lemon Meringue Pie (LMP).

The tasty moniker isn't expected to make it through to the inevitable official release of the product (Key Lime Pie became KitKat at release, while Lemon Meringue Pie morphed into Lollipop), but that doesn't make it any less enticing as far as sweet-to-eat treats go. 

 Recipe: Macadamia Nut Cookies (courtesy of Taste of Home)

Macadamia Nut Cookie — heretofore mostly referred to simply as 'Android M' — is set to make its public debut on Thursday at Google I/O (May 28 and 29 at Moscone West Convention Center in San Francisco), with the new Android flavor specifically mentioned in the May 28 2:30-3:00PM Android for Work Update slot. 

It was at its I/O event last year that Google first revealed Lemon Meringue Pie...er, what it called 'Android L' at the time. In the case of 'L' the company didn't get all sticky with the 'Lollipop' branding until November, and this year's sweet offering is expected to follow a similar path. As such, now is the prime time to offer WAGs as to the eventual official name of 'Android M'. 

Android Muffin, anyone?


Show comments blog comments powered by Disqus