Article6 min readUpdated
App Permission Screen Design: Ask at the Right Time
App permission screen design: when to ask for location and notifications, how to write the why, consent checkboxes and what to show if users say no.
By Tithi Mondal, UI/UX Designer
A food delivery app opens for the first time and immediately shows a system box: "Allow access to your location?" The user has not seen a single restaurant yet. They tap Deny. Now the app cannot find nearby food, and the user thinks the app is broken.
An app permission screen is the moment where an app asks the user to allow access to something on the phone, such as location, camera, contacts or notifications. The system dialog itself is controlled by the phone, and the app cannot change its words. What the designer controls is the moment, the screen before it and the screen after a refusal. This post covers all three, plus consent checkboxes. For first-run flow in general, see app onboarding UX best practices.
When should an app ask for a permission?
An app should ask at the moment the user starts a task that needs the permission, not at launch. People say yes when the reason is in front of them.
Match each permission to its natural moment:
| Permission | Ask when | Not when |
|---|---|---|
| Location | The user taps "Find restaurants near me" | The app opens |
| Camera | The user taps "Scan document" | During sign up |
| Notifications | After the first order is placed | Before any value is shown |
| Contacts | The user taps "Invite friends" | At install |
| Photos | The user taps "Add photo" | At first launch |
Ask for the least that works. If an app needs the city only, ask for approximate location, not precise location, where the platform allows it. Do not ask for permissions you might need later. Each request that is not needed lowers trust for the requests that are.
How do you explain why data is needed?
Explain why data is needed in one sentence that names the benefit to the user. State what you use it for and, where true, what you do not do.
Use this pattern: "We use your [data] to [benefit]." Examples:
- Location: "We use your location to show restaurants that deliver to you."
- Camera: "We use the camera to scan your document. The photo is used only for verification."
- Notifications: "We will tell you when your order is on its way."
- Contacts: "We use your contacts to find friends who already use the app. We do not message anyone."
Only write promises that are true. The business must confirm the real data use, storage and sharing with its legal or compliance adviser, and the wording must match the privacy notice. If you cannot explain why you need the data in one sentence, you may not need the data.
Write for new internet users with short words, as in designing for first-time internet users. Offer the text in the user's language where you can.
What is a pre-permission screen and how is it designed?
A pre-permission screen is your own screen, shown before the system dialog, that explains the reason and lets the user choose to continue. It protects the real request, because a "Deny" on the system dialog is hard to undo.
Layout, top to bottom:
- A simple picture that shows the benefit, such as a map pin over a street.
- A title: "Find food near you".
- One sentence: "We use your location to show restaurants that deliver to you."
- A main button: "Allow location". It opens the system dialog.
- A quiet second button: "Enter my area instead" or "Not now".
The second button matters. If the user taps "Not now", the app must still work. Offer a manual path: a pincode box or a city list. Do not show the system dialog if the user chooses "Not now", and do not show your screen again at every launch. Ask again only at the next natural moment.
How should a location permission prompt and notification permission work?
A location permission prompt should explain the benefit and offer a manual alternative, and a notification permission should be asked after the user has seen value. These two are the most misused.
Location. The user may be asked to choose between precise location, approximate location, only while using the app, or deny. Your pre-permission screen should say what you need: "Your exact location helps the rider find your door." If the user shares less, show the effect honestly: "We will use your area to show restaurants. You can add your exact address at checkout."
Notifications. Ask after something has happened that a notification will help: "Get a message when your order is ready" after the first order, or "Remind me before class" after joining a class. Let the user pick what they want. See notification UX for push, SMS and WhatsApp for the content of messages.
Do not ask for both in the first 10 seconds. Spread the requests over the journey.
How should consent checkboxes and consent screens look?
A consent checkbox should be unticked by default, separate from other agreements, and written in plain words with a link to the full text. Ticking it should be the user's own action.
Good practice:
- One checkbox for one purpose. "I agree to receive offers on WhatsApp" is separate from "I agree to the Terms".
- Unticked by default. Never pre-select consent.
- A label that says what happens: "Send me offers and updates on WhatsApp".
- A link to the full policy that opens in the app, not in a hard-to-leave page.
- Marketing consent is optional. The user can continue without ticking it.
- A way to change the choice later, in Settings. See profile and settings screen design.
Show the consent record the user gave, with a date, if the business keeps one. Which consents are required, and how they must be asked and stored, is a legal question. Ask your legal adviser, and then design the screens to match their list. For long forms, see form design best practices.
What if the user says no?
If the user denies a permission, the app should keep working and offer a calm way to change the decision later. Denial is a normal answer, not an error.
Design a denied state for each permission:
- Message: "Location is off. You can still choose your area by hand."
- Alternative action: a pincode box, a manual upload, an in-app notification list.
- Change-your-mind path: "Turn on in Settings", a button that opens the phone's settings for the app. Show it only when the user taps a feature that needs the permission.
Do not repeat the request in a loop. Do not lock the app behind a permission that is not strictly needed. Where a permission is strictly needed, for example the camera for document scanning, say so on that screen only, and show the settings route.
My accessibility guide is also relevant: give every button a clear label so screen reader users know what "Allow" will do.
If your app needs permission and consent screens that people trust, I can design them as part of a mobile app design project.
Frequently asked questions
Can I change the wording of the system permission dialog?
No. The phone controls that box. You can design the screen before it, and the screen shown if the user says no.
Should the app ask for all permissions at the start?
No. Ask for each permission when the user starts a task that needs it. Early requests without context are more likely to be refused.
Should consent checkboxes be ticked by default?
No. Leave them unticked so that ticking is the user's own action. Confirm the exact consent rules with your legal adviser.
What should happen if a user denies location access?
The app should still work, with a manual option such as entering a pincode or choosing a city. Offer a route to settings only when needed.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.