Android runtime permissions: how a well-behaved app asks, and what to check
Plan Android permission requests in context, handle refusals gracefully and test the features that need sensitive access.
When an Android app asks to use your camera, location or notifications, that request follows rules Google documents for developers. If you are commissioning an app, these rules give you something concrete to check in a build. This article summarises Google's "Request runtime permissions" page as read on 15 November 2026 (the page says it was last updated 2026-10-28). It covers Android only; iOS works differently. Read the page itself before you build.
When a request is needed
The page says that if an app declares any "dangerous" permissions and runs on Android 6.0 (API level 23) or higher, it must request them at runtime. Without dangerous permissions, or on Android 5.1 and lower, they are granted automatically. It adds that some especially sensitive permissions use a different, special process. It also says many use cases, such as taking photos, pausing media playback and showing relevant ads, can work without declaring any permission, so first ask whether you need one.
The principles Google gives
- Ask in context, when the user starts the feature that needs it.
- Do not block the user. Any explanation screen must be cancellable.
- If the user denies or revokes a permission, degrade gracefully, for example by turning off only the feature that needs it.
- Do not assume system behaviour. Permission groups exist to reduce the number of system dialogs, and an app should not rely on which group a permission is in.
The workflow in the page, in plain words
The app declares the permissions in its manifest, ties each to a specific user action, waits for that action, checks whether the permission is already granted (every time, not once), decides whether to show a rationale, requests it, then checks the answer and degrades gracefully if refused.
- The system dialog says what the app wants but not why, and the app cannot customise it. The page recommends explaining why before asking, and says research shows users are more comfortable when they know the reason. If an app uses only part of a permission group, such as coarse location only, the page suggests saying so.
- If the check returns denied, the app calls a method that tells it whether to show an educational screen. That screen should include a cancel or "no thanks" option.
- The page recommends the AndroidX RequestPermission contract where possible over managing request codes yourself.
- Since Android 12 (API level 31), privacy indicators appear when apps use the microphone or camera.
Location is split into foreground and background
The page separates foreground location (a feature that shares or receives location once or for a defined time, for example turn-by-turn directions) from background location (continuous sharing, or using the Geofencing API). On Android 10 (API level 29) and higher, background location needs its own manifest permission, and a foreground service that uses location must declare a location service type. The page notes that Google Play has a location policy restricting background location to apps that need it for core functionality and meet its requirements. Our Google Play and geofencing articles cover related ground.
When the user says no
Google's guidance is to minimise functionality loss, point out the specific limited part of the screen, say exactly which feature is unavailable, avoid full-screen blocking messages, and not nag. The page says that after a user taps Deny more than once for a permission on a device, the system no longer shows the dialog for it, which it treats as a permanent denial, so asking at the wrong moment can cost the chance to ask again. It also warns against assuming anything about automatic grants or denials and says to check on each use. In the code sample's comments it says not to link users to system settings to try to change their decision.
Newer behaviours the page lists
- One-time permission (Android 11, API 30 and higher): for location, microphone and camera, the dialog includes "Only this time". The app can access the data while its activity is visible, for a short time after it moves to the background, and, if it started a foreground service while visible, until that service stops. If the user revokes it, the app's process is terminated.
- Removing access (Android 13, API 33 and higher): an app can drop runtime permissions it no longer needs, using revokeSelfPermissionOnKill, and the page suggests telling users on next launch.
- Auto-reset: for apps targeting Android 11 or higher that are not used for a few months, the system resets sensitive runtime permissions the user had granted.
- Call logs and SMS: to publish on Google Play with those permissions, the app must first prompt the user to make it the default handler for a core function.
Testing tips on the page
The page shows an adb command to inspect whether a permission was denied once or permanently, and one to reset those flags so testers see the dialog again. It also shows an install option that grants all runtime permissions on a test device. Granting everything hides what a real user sees, so test the denial path too (our advice).
Omnistu advice for an app project (not from the source)
- List every permission the app declares and ask the developer for the feature that needs each one. A permission with no feature is a question to answer before launch.
- Ask to see the app with every permission denied. Each core flow should still work or explain itself.
- Agree who writes the "why we ask" text, since the system dialog will not.
- Match the permission list to the Google Play Data safety form and the privacy policy; our articles on those cover who owns each.
- Re-check the list at every release.
Limits
One Android Developers page, read in full on 15 November 2026. We did not test any code or adb command, and we did not read the permissions reference, the special permissions pages or the default handler guide. Android only. Platform and Play policy details change. This article is not legal or privacy-law advice.
By Omnistu.