Commentary

Google Renames Next Version Of Android

I am not a fan of Flan. Flan is a custardy dessert with which I've had several bad experiences. Given my personal tastes, I cringed a bit when I heard that Google had originally picked the name Flan for its next version of Android. Thankfully that has changed.

I am not a fan of Flan. Flan is a custardy dessert with which I've had several bad experiences. Given my personal tastes, I cringed a bit when I heard that Google had originally picked the name Flan for its next version of Android. Thankfully that has changed.Google has come up with an interesting (OK, maybe amusing) naming scheme for its builds of Android -- they are all the names of desserts and run in alphabetical order. Android 1.5 was Cupcake, Android 1.6 was Donut, Android 2.0 was Eclair and the next named version of Android was supposed to be called Flan.

According to Googler Erik Tseng, Flan is out and Froyo is in. Froyo, of course, is short for frozen yogurt. It follows the alphabetical naming scheme perfectly, and I find it's a much nicer name than Flan. (It tastes better, too.)


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

One thing to keep in mind. Though Android 2.1 is already available on the Nexus One, it is still considered to be part of the Eclair branch of Android. Whatever numerical designation Froyo corresponds with was not revealed by Tseng. It could be anything.

We also have to start guessing what Google will pick next. It has to start with a "G". Thoughts? AndroidAuthority.com suggested ginger, gelatin, gelato, and ganache. I ain't got nothin' beyond that.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links