OOmnistu

Blog / Engineering Playbooks

Engineering Playbooks

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.

OOmnistu
Reviewed 2026-11-16 · 5 min read

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

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 RUNTIME-PERMISSION REQUEST FLOW, AFTER GOOGLE'S PAGE User starts the featureask in context Already granted?check every time, not once yes Use the feature no Show a rationale?the system method decides yes Cancellable "why" screenincludes cancel / no thanks no System dialogthe app cannot customise it user proceeds user cancels: no request, degrade gracefully Granted? yes Use the feature no Degrade gracefully turn off only the feature that needs it For one specific permission, Deny more than once during the app's installed lifetime on a device: the system stops showing the dialog ("don't ask again"). THE RUNTIME-PERMISSION REQUEST FLOW, AFTER GOOGLE'S PAGE User starts the featureask in context Already granted?check every time, not once yes - use the feature no Show a rationale?the system method decides yes - cancellable "why" screen (includes cancel / no thanks) cancel - degrade gracefully, no request proceed System dialogthe app cannot customise it Granted? yes - use the feature no Degrade gracefullyturn off only the feature that needs it
From Google's "Request runtime permissions" page as summarised above: ask in context, check the grant on every use (not once), and when the system method says to show a rationale, present one the user can cancel - acknowledging it proceeds to the request, cancelling means the feature goes without it. The page's exact condition on repeated denial: for a specific permission, after Deny more than once during the app's lifetime of installation on a device, the system no longer shows the dialog for that permission, treating it as "don't ask again".

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

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)

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.

Sources

Previous
Android App Links: opening your website's links in your app, and what Android 15 changes