Google Announces Android M At Google I/O 2015by Brandon Chester on May 28, 2015 2:00 PM EST
- Posted in
- Google IO
- Android M
Today Google formally announced the next version of their Android operating system at their Google I/O developer conference. Much like how Android Lollipop was originally previewed under the name Android L, the next major release of Android is being referred to as Android M. After the comprehensive redesign and under the hood changes in Lollipop, Android M brings a greater focus on bringing greater polish to Android and improving the user experience. During the keynote Google outlined six major areas that they had targeted for improvement in Android M.
The first area of improvement is permissions. The permissions system on Android has been less than optimal since its earliest days. The big issue has always been that applications have to ask for permissions access at the time of install. This means that if a user wanted to install an application like Skype, but didn't want to give it access to their microphone, then they would not be allowed to install the application at all.
Android M changes the existing permissions system this by breaking down user permissions into specific categories, and having apps ask the user for permission at the time access to a feature is required. You can see an example of this above, where an application like Whatsapp will ask for microphone access when the user tries to do something that requires it. This means that the user can grant applications some permissions but not others, and they can manage permissions access after the fact. It also makes it more clear to the user what an application is asking to do.
The new permissions system in Android M is only available for applications that target Android M with the new version of the Android SDK. Unfortunately, this means that it won't be automatically available to existing applications when users update to Android M.
The next area of improvement in Android M is to the behavior of web views within other applications. This is through a feature called Chrome Custom Tabs. Essentially this feature allows applications to have the Chrome browser run atop their app whenever the user clicks on a link. This means that all of a user's autofill data, passwords, and cache are available when they open links within that application.
The third major improvement Google is making in Android M is to how Android Intents handles web links. Because many web services now have native applications, selecting a link in an application will often bring up a menu asking the user whether they would like to open that link using a web browser, or whether they would like to have an app on the phone handle it. With Android M, app developers can now have the operating system verify that certain types of links are meant to be opened with their app by checking with the web server that those links point to and verifying that it is meant to be opened with that app.
Google's next two areas of focus relate strongly to Android Pay, the mobile payments system they announced at MWC earlier this year. Android Pay is not strictly an addition to Android M, as it will be available on devices that run KitKat or newer. However, Android M will allow a greater degree of security when using Android Pay through a new API to standardize fingerprint sensors on Android devices. This means that users will be able to authorize Android Pay transactions both at stores and in apps using their fingerprint. It also means that app developers will be able to use a user's fingerprint for verification, which is currently not feasible with the various different standards and implementations for fingerprint scanners on Android devices.
The last area of focus in Android M is arguably the most important. It's a focus on power usage, and more specifically, the power that a device uses when it's idle. With an OS like Android which supports multitasking, there's always a delicate balance between managing power and keeping applications running in the background updated. With Android M, Google is introducing a new feature called Doze. Doze uses motion detection to see whether or not a device has been left idle for a long period of time, such as when it's sitting on a table or in a dock. If it has been left idle for a long period, the operating system will greatly scale back background activity in order to reduce idle power usage. According to Google, they've seen up to 2x longer idle battery life on the Nexus 9.
In addition to improvements in power usage, Google is implementing new charging options for future devices that use USB Type C. Type C allows devices to negotiate whether they should be the device being used to charge from, or the device being charged, and this will be supported in Android M. This means that a user can use their tablet's battery to charge their smartphone from.
Android M looks like a more minor release than Android Lollipop was. However, what Google has detailed here is only scratching the surface of the many small improvements and bug fixes that it will bring to Android. Other improvements include changes to how text selection works, and further changes to the not very popular changes to the volume controls that were made in Android Lollipop.
Much like when Android Lollipop was announced at Google I/O last year, this year's release is accompanied by a preview for developers so they can test their apps and give Google feedback on the changes that they are making to Android. The Android M developer preview will be available today for the Nexus 5, the Nexus 6, and the Nexus 9.
Post Your CommentPlease log in or sign up to comment.
View All Comments
webdoctors - Thursday, May 28, 2015 - linkConsidering the extremely slow deployment of Android L, does M really matter? How many phones will actually have it in 2015 or even 2016?
Android 5.x is barely hitting 10% of the market based on dashboard stats: http://developer.android.com/about/dashboards/inde...
theblacklaser - Thursday, May 28, 2015 - linkI agree 100%. I actually chuckled at this line: "Unfortunately, this means that it won't be automatically available to existing applications when users update to Android M."
Users updating? Not likely. There's no incentive for phone makers to update old hardware when they can sell users new hardware. It's a thoroughly broken system. Thank god for projects like cyanogenmod, but even there, unless you have a very very popular device, you're probably not going to see a ton of support.
bplewis24 - Thursday, May 28, 2015 - linklol @ cyanogenmod.
quiksilvr - Thursday, May 28, 2015 - linkIt is a really annoying problem. Phone manufacturers and OEMs need to stop having uninstallable applications on here. Hell, their launcher should be uninstallable. Their keyboard. I wish the Vanilla Settings was just baked into the OS and just have a section for OEM specific functionality they want to add.
The OEM's launcher, settings/notifications, keyboard and apps are really the main things that can become removable apps/additions on top of Vanilla Android. Make those easily removable and bam, Vanilla Android that can be updated in a timely fashion and you just choose what you want from the OEM (or not if it is hindering your update).
Alexvrb - Thursday, May 28, 2015 - linkThat's one really nice thing about WP, you can remove any preinstalled junk you don't want and all WP devices are stock OS.
Anyway the new permissions looks interesting. My dad would love that. Only question is... will compliance be mandatory for future apps and/or updates of existing apps? If it's something developers can ignore/bypass/opt-out of, it's useless.
MonkeyPaw - Thursday, May 28, 2015 - linkThe problem really comes when a security flaw is never patched. I think most people can deal with the fact that their phone's UI never changes. At the very least, they've gotten exactly what they paid for, just nothing more, much like feature phones of yesteryear. Then again, sometimes these upgrades aren't even a benefit when poorly implemented. When my LG G2 finally got Lollipop this month, it lost a couple useful features that it had under KitKat (like when you plug in headphones, it pops up a customizable list of apps that you can launch). Now the phone can be noticeably slower at simple tasks. Occasionally when I hit the home screen, it takes a second or two to load the apps on the screen. I thought Android L was supposed to be faster? No wonder adoption is so terrible after this long.
Android has 2 major problems. The lack of updates, and that OEMs customize the OS. The very thing that Android does best (customization and diverse hardware support) is also it's downfall. No one entity can manage to keep all devices current, and the blame is shifted from Google, to the OEM, to the carriers.
timrichardson - Thursday, May 28, 2015 - linkI disagree with your OEM problem. After HTC, nexus and now my second Samsung, i think many Samsung additions are valuable. Auto switching away from weak WiFi, floating notifications, restricted WiFi networks, adaptive sound equalizer, color control ... And stock keyboard used to be poor; Samsung licensed Swiftkey but added text shortcuts. touch wiz gets a bad rep but in the keynote about M Google admitted Android has been enriched by OEM innovations (a lot of them come from Samsung.)
Security is a fair call although the separate webview app of Lollipop is a breakthrough.
Shidell - Thursday, May 28, 2015 - linkAndroid's progress isn't tied to adoption. It will continue to move forward.
ajp_anton - Thursday, May 28, 2015 - linkIf they are two years behind on L, it just probably means they will be two years behind on M as well, and when that time comes, you'll be happy that two years earlier M was introduced.
(Of course you, and we all, would be even more happy if they eliminated or even reduced those two years...)
bplewis24 - Thursday, May 28, 2015 - linkYeah, I don't think you understand the appeal of Android and how it works for most people.