# Android Marshmallow Runtime Permissions: UX Guidelines and Implementation Tips

DevFeed: [Android Marshmallow Runtime Permissions: UX Guidelines and Implementation Tips](<https://devfeed.tech/articles/may-i-have-some-marshmallows-please-25838.md>)

Original publisher: [Read original article](<https://segunfamisa.com/posts/marshmallow-permissions>)

Author: Segun Famisa

Published: 2016-01-28T03:05:30Z

Content type: tutorial

Language: en

Sources: [Segun Famisa](<https://devfeed.tech/sources/segun-famisa.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [User experience (UX)](<https://devfeed.tech/topics/ux.md>), [App](<https://devfeed.tech/topics/app.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [code](<https://devfeed.tech/tags/code.md>), [developers](<https://devfeed.tech/tags/developers.md>), [feature](<https://devfeed.tech/tags/feature.md>), [permission](<https://devfeed.tech/tags/permission.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [qr-code](<https://devfeed.tech/tags/qr-code.md>), [tips](<https://devfeed.tech/tags/tips.md>), [ux](<https://devfeed.tech/tags/ux.md>)

## AI overview

A developer guide to Android Marshmallow runtime permissions, covering privacy, permission timing, user context, and UX practices for requesting access based on how critical and clear a feature is.

## Source excerpt

After a long wait, my AndroidOne finally got it's Marshmallow update yesterday. I finally got a hands on experience of the not-so-new OS, and I must confess, I love it! I love the 'Now on tap', the 'DND' mode, and one of my favourite parts of the update - the new permissions feature. With the new permissions, users now have more control over permissions that apps have. Like in iOS, users can specifically turn off certain permissions like access to contacts, locations etc. So, if you've built your app previously to request for permission to use the camera for example, if users turn off that permission for your app, that functionality will fail. Check here if you want to see more about the 'new' permissions in Android M. This has been out for a while now and, but I thought to put out some tips here for developers yet to update their apps for Android Marshmallow. According to Nick Butcher in this video, the primary purpose of permission, is to protect your users' privacy. Runtime permissions allow you to choose the right time to ask for permission when the user has more context about why you're asking and why they need to grant it. He also described the UX best practices with runtime permissions. I suggest that you check out the video. He talked about determining your permission requirements by how important (critical or not) the permission is to your app, and how clear the need for that permission is. Critical and clear: e.g SMS permission in an SMS app, or Camera permission in a Camera app. This is critical to app functionality and hence, it's good to request for this permission at the beginning. Critical and unclear: when the feature is important, but not immediately obvious. You should educate the users upfront before requesting for permission. Secondary and not clear: offer some explanation and then allow the users opt-in and then should you request. Secondary and clear: If a secondary feature that is clear, you should ask in context. No need to ask too early. Bet