Google’s I/O 2012 kicks off in just a matter of hours — 12:30 PM EST, to be exact — and thanks to a post on the Google Developers Google+ page, the company has all-but-confirmed the debut of the next iteration of Android, codenamed Jelly Bean.
This continues a long-running tradition of Google mixing numerical and dessert-themed names with its OS releases, as we’ve had Cupcake (1.5), Donut (1.6), Eclair (2.0), Froyo (2.2), Gingerbread (2.3), Honeycomb (3.0), and, announced at last year’s I/O, Ice Cream Sandwich (4.0). That same event also brought us Google Music, the company’s rival to iCloud, SkyDrive and Amazon’s Cloud Drive/Player, and Android@Home, which sought to bring an Android standard to home automation.
Google also gave away 5,000 special versions of the Samsung Galaxy Tab 10.1, and if rumors of the upcoming Google Nexus tablet are confirmed at today’s I/O, we may see another giveaway of the new device — rumored to be an Asus-produced, 7″ quad-core device, with a Kindle Fire-rivaling sub-$200 price tag.
Stay tuned to Technocrat for the full lowdown when Google reveals all this afternoon.
As a free LGBTQ publication, Metro Weekly relies on advertising in order to bring you unique, high quality journalism, both online and in our weekly edition. The ongoing coronavirus pandemic has forced many of our incredible advertisers to temporarily close their doors to protect staff and customers, and so we’re asking you, our readers, to help support Metro Weekly during this trying period. We appreciate anything you can do, and please keep reading us on the website and our new Digital Edition, released every Thursday and available for online reading or download.
Rhuaridh Marr is Metro Weekly's managing editor. He can be reached at email@example.com.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.