Mobile app permission request examples
Building a mobile app and planning an access request? Study how Spotify explains connecting a device, how Revolut presents contact access and how Duolingo separates a data-sharing choice. Compare these references, then plan your explanation, refusal and returning later with a copyable brief. Notes are public; a free account lets you keep references and unlock workflows.
Prepare a brief for your access request
Copy this outline into your project notes and replace the bracketed items. Plan acceptance, refusal and returning later, then connect references to your decisions.
Access request for [my app] Selected action: [what someone wants to accomplish]. Request type: [system permission, in-app explanation or optional sharing]. Requested access or sharing: [specific need and purpose for this action]. Explanation timing: [after which action and before which step]. Message to present: [concrete benefit and available choices]. After acceptance: [return to the task and state to verify]. After refusal or cancellation: [alternative without this access]. When returning: [how to resume the task and check current access]. Separate optional sharing: [independent choice, or none]. States to test on my platforms: [first request, refusal, limited or revoked access where applicable]. References to compare: [saved captures and workflows]. Question to test: [what someone understands and can do without this access].
Design your access requests with concrete references.
Create your free account with GitHub to save references, compare screens in a collection and keep your app’s design decisions together.
One preview workflow per app, with up to 4 visible screenshots. A free account includes 3 complete workflow unlocks per calendar month. No payment card needed. Saving a reference does not unlock its screenshots.
- Open the workflow to understand what precedes the request.
- Save references useful for your explanation and alternative.
- Compare them in a collection and record acceptance and refusal paths.
After signing in, you will return to these examples to save your first reference.
References to explore
Explore these references and follow each app’s available workflows.
![[untitled]](/api/images/_untitled__Flows/logo.webp?thumbnail=1&v=app-preview-1){kind=logo}
![[untitled] interface preview 1](/api/images/_untitled__Flows/Onboarding/screen_1.png?thumbnail=1&v=app-preview-1)
![[untitled] interface preview 2](/api/images/_untitled__Flows/Onboarding/screen_2.png?thumbnail=1&v=app-preview-1)
Connect the request to a selected action
Start with the task someone wants to complete: inviting a person, connecting a device or using an audio feature. Open the workflow before the request to understand what was selected and why access is useful at that moment.
For an MVP, note what actually depends on this access. A secondary feature can have its own entry point; it does not necessarily need to interrupt first use of your app.
Distinguish different kinds of requests
An explanation drawn inside an app is not the system dialog. A sharing choice intended to improve a service is not a hardware permission either. This guide treats these situations separately; imported tags may group different types of requests.
- Before: what use does the app explain?
