Friday, May 29, 2015

Android M is Milkshake - 6.0 revealed today at Google I/O today - Milkshake not Muffins/Mango/Marshmallow/Macaroon

While many Android folks are still using devices based on Ice Cream Sandwich and Jellybean, some on KitKat and a few on Lollipop, Google has today released a Developer edition of Android M.

Android M 6.0 is Milkshake

What does M in Android M stand for ?

There is still no official word on what the M is going to stand for.

But the latest rumor is that it will be Milkshake.
Here's a photo from Google I/O showing an Android Wear watch worn on stage by Google's vice president of engineering, Dave Burke, clearly showed a picture of a glass of milkshake as he demonstrated features during the conference. He even fiddled with the device a few times, almost deliberately drawing attention to it.

Clues to Android M being Milkshake

Previously the name was suspected be Milkshake/Muffins/Marshmallow/Macaroon/Mango or even brand names like Mentos/M&Ms like Google did with Kit-Kat.

CSI : Zoomed image

Here's a poll from a few weeks back which showed the top contenders where the favorite was Marshmallow.

So, hope you all get an update to Android Milkshake when it is available for non-developers.

Android Milkshake will have USB type C support - the reversible, high speed, high powered USB port. (that the new MacBook Air has only 1 port of)

To get the downloads and documentation for Android M go to M developer preview.

The major updates in Android Milkshake are

  • Permissions - Android is giving users control of app permissions in the M release. Apps can trigger requests for permissions at runtime, in the right context, and users can choose whether to grant the permission. Making permission requests right when they’re needed means users can get up and running in your app faster. Also, users have easy access to manage all their app permissions in settings. On M, as a developer, you should design your app to prompt for permissions in context and account for permissions that don’t get granted. As more devices upgrade to M, app permission behavior will be a critical development flow to test.
  • App links - Android is making it even easier to link between apps. Android has always allowed apps to register to natively handle URLs. Now you can add an autoVerify attribute to your app manifest so that users can be linked deep into your native app without any disambiguation prompt. App links, along with App Indexing for Google search, make it easier for users to discover and re-engage with your app.
  • Battery - Google is making Android devices smarter about managing power through a new feature called Doze. With M, Android uses significant motion detection to learn if a device has been left unattended for a while. In this state, Android will exponentially back off background activity, trading off a little bit of app freshness for longer battery life. Consider how this may affect your app; for instance, if you’re building a chat app, you may want to make use of high priority messages to wake your app when the device is dozing.
  • Now on tap - Google is making it even easier for Android users to get assistance with Now on tap -- whenever they need it, wherever they are on their device. For example, if your friend texts you about dinner at a new restaurant, without leaving the app, you can ask Google Now for help. Using just that context, Google can find menus, reviews, help you book a table, navigate there, and deep link you into relevant apps. As a developer, you can implement App Indexing for Google search to let users discover and re-engage with your app through Now on tap.
  • Android Pay & Fingerprint - Google has built on their work with Near Field Communications (NFC) in Gingerbread and Host Card Emulation in Kitkat to develop Android Pay. Android Pay will enable Android users to simply and securely use their Android phone to pay in stores or in thousands of Android Pay partner apps. With M, native fingerprint support enhances Android Pay by allowing users to confirm a purchase with their fingerprint. Moreover, fingerprint on M can be used to unlock devices and make purchases on Google Play. With new APIs in M, it’s easy for you to add fingerprint authorization to your app and have it work consistently across a range of devices and sensors.

To get started with the M Developer Preview and prepare your apps for the full release, just follow these steps:
  1. Update to Android Studio v1.3+ Preview
  2. Visit the M Developer Preview site for downloads and documentation.
  3. Explore the new APIs & App Permissions changes
  4. Explore the Android Design Support Library & Google Play Services APIs
  5. Get the emulator system images through the SDK Manager or download the Nexus device system images.
  6. Test your app with your supported Nexus device or emulator
  7. Give us feedback

Update : Dave Burke has tweeted that this may or may not be wrong.

No comments:

© FunDa of
Subscribe to these websites at
FunDaZone.Com RSS feed

More tips and tricks for softwares and websites !!!

RSS syndication