App Permissions is one of the key areas where Google has improved core user experience with Android M. In the new model of App Permission, you will get better control of managing what resource an App can have access from your device.
In Android M, you don’t have to ‘Accept Permissions’ for apps during the installation time. Instead, Apps will ask you for permission when they will try to use your system resource for the first time. Don’t worry, this will be a one-time permission and you don’t have to accept them again. You might ask, what kind of permission is being referred here? Well they are simply understandable resources of your phone listed below:
How does App Permission in Android M really works?
Suppose an App wants to access your current location using GPS, it will display a prompt which needs your approval to “Allow” or “Deny” the App access to your location. Once you allow this application to access your location, it won’t ask you again from the next time.
We will take one more example to make this more clear. Let us say we install WhatsApp on Android M, we will not accept any permission during installation time, as we said. Now we want to send a ‘voice message’ in WhatsApp and when we tap mic button, we will be shown a approval prompt where we can “Approve” or “Deny” access to our Microphone. If we grant the permission, we can now send voice message using WhatsApp and if we deny, WhatApp won’t be able to use Microphone from our phone.
What if you want to Redefine Permissions you have granted ?
You can manage your permissions very effectively with Android M. You will go to settings, choose the App and check what permissions it has been granted and can modify them. You can do the other way by choosing permissions like Microphone and check which Apps have access to it, and can manage which Apps you could have access to Microphone.
What App Permissions brings to Developers?
Firstly, developers will need to compile apps with Android M SDK which you can download here. All legacy apps which are not compiled using Android M SDK will behave as before. In old permission model, adding a new permission to your existing app can affect your update adoption but with the new Android M permission model, updates are smooth because user involvement are there at the right time when needed. As you know, your app will be installed without any permissions approval but you can always add new permissions in your app update without any issue. Users won’t have to “Accept” permission during app update but only when they use it.
Well this was all about new App Permission model in Android M. If you think something is missing, let me know.