Expected to go official at Google I/O later this week, “Macadamia Nut Cookie” should first roll out in a developer preview next month.
It’s never wise to have guarantees regarding unreleased hardware or software cooked up by Larry Page’s world-class team of engineers. Nothing’s really certain until it’s certain on the Android, Google Apps, Chrome OS or Nexus fronts.
Not device specifications, not UI design, product names and target audiences, and clearly not timelines. Especially timelines. These are often so random and all over the place that they feel scheduled on a whim after multiple false starts intended to confuse tipsters and “inside sources.”
Remember the LG-made Nexus 5? Rumor has it a direct sequel (unlike the N6 spin-off) will see daylight almost two full years on the heels of the original’s debut. Meanwhile, Android 5.0 Lollipop source code dropped roughly 12 months after 4.4 KitKat, which however launched a good 15 months following 4.1 Jelly Bean. Notice any sort of pattern?
Neither do we, so we probably shouldn’t act too surprised hearing fairly credible speculation of an August Android M rollout. Too soon, you say? Maybe, but given L’s never-ending memory and stability woes, this is most likely what the platform needs – a fresh start.
Centered on battery efficiency improvements and better RAM management, reportedly, which to be frank, rings a few too many bells. Isn’t that what the focus was supposed to be on 5.0 and 4.4? Of course, there’s nothing wrong with admitting your defeats and trying again and again to amend perhaps the operating system’s primary flaws.
But at this point, we feel Google is chiefly about talking the talk, not enough for walking the walk. Good thing at least one altogether new feature is allegedly headed to Android M – native fingerprint recognition.
Back to deadlines, Android Police has it on good authority Macadamia Nut Cookie, aka MNC, aka Marshmallow will be ready for primetime before the weather turns bad, so the dev-centric beta must go out in June. Possibly, just one or two weeks after the I/O conference.