Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

App design · 17 Nov 2026 · 6 min read

App permissions: asking for camera, location and contacts well

Every permission request is a small negotiation with the user. Here is how to time it, word it and cope with a refusal.

The short answer

App permissions should be requested at the moment the user taps something that needs them, not at first launch. Explain in plain words what the app will do with the access, offer a working alternative if the user refuses, and ask for the narrowest access that does the job. Check each platform's current documentation for how its prompts behave.

App permissions are a decision the user makes in seconds

App permissions are the system prompts that ask to use the camera, the location, the contact list and similar parts of the device. The user sees a short dialog written mostly by the operating system and has a few seconds to decide. Your job is to make that decision easy to say yes to, when yes is justified, and harmless to say no to.

This page is about the craft of asking: timing, wording, fallbacks and testing. For the wider picture of what data an app collects and how to tell users, see our separate guide on privacy basics for founders, which sits alongside this one.

When an app should ask for a permission

Ask when the user does something that obviously needs the access. A scan button asks for the camera. A find-near-me button asks for location. An invite-friends button asks for contacts. The dialog then arrives with its reason attached, because the user has just tapped the thing that explains it.

Asking at first launch, before the user has seen any value, is the usual mistake. The prompt has no context, refusals are common, and on some platforms a refusal is hard to undo. Early screens are better spent on the points covered in designing the first screens of an app.

Some permissions have a natural exception. If the whole product is a map or a camera tool, asking early is reasonable, because the app is useless without it. Say so on the screen before the system dialog appears.

Use your own explanation screen before the system prompt

On iOS the system dialog for a given permission is normally shown once. If the user taps the wrong option, the only route back is through the device settings. Android lets an app ask again in some situations, but the system limits repeated requests, and the details change between versions. Check the current documentation for each platform.

This is why many teams show a short screen of their own first. It says what the app will do with the access and has two buttons: continue, which triggers the system dialog, and not now, which does not. A user who picks not now has not used up the one-time system prompt, so you can ask again later when the need is clearer.

What each common permission is for, and a softer alternative

PermissionTypical reasonA softer option
CameraScan a code, take a photo, video callLet the user choose an existing photo from the library instead
LocationShow nearby results, track a deliveryLet the user type a city or postcode; ask for approximate rather than precise location
ContactsFind friends, invite peopleShare an invite link through the system share sheet, with no contact access at all
PhotosUpload a pictureUse the system photo picker, which lets the user choose individual pictures
NotificationsOrder updates, remindersAsk after the user has done something worth being notified about

The softer option is not a second-best path. For many users it is the better one, and it often means you can drop the permission entirely. Less access also means a shorter privacy form to complete for the store.

How to explain why access is needed

Good explanation copy answers three things in two sentences: what you will use, what for, and what happens if the user declines. For example: the camera is used to scan the code on your parcel, and nothing is saved unless you press the save button. If you say no, you can type the code by hand.

iOS also requires a short purpose text for permissions such as camera and location, written in the app's configuration. A vague or missing text is a common reason for rejection, and a text that does not match what the app really does is worse. The guide to why apps get rejected from app stores lists related causes.

Avoid pressure. Phrases such as you must allow this or the app will not work are rarely true and annoy people. Avoid vague claims too, such as to improve your experience. Name the real feature.

What if the user says no

Plan the refusal before the approval. A user who declines should still be able to use everything that does not strictly need the access, and the feature that does need it should explain itself calmly in place.

  • Show a short message where the feature would have appeared, saying what is missing and why.
  • Offer the alternative path from the table above where one exists.
  • If the access can only be changed in settings, give a button that opens the app's settings page, and say so plainly.
  • Do not ask again on every launch. Ask again only when the user taps the feature again.
  • Do not block the whole app behind one refusal.

Also consider the user who allowed access and later withdrew it in settings. The app should notice the change when it returns to the foreground, not crash or sit on a blank screen.

Ask for less access than you could

Many permissions come in grades. Location may be approximate or precise, and may be allowed only while the app is in use. Photo access may be limited to chosen pictures. Ask for the narrowest grade that does the job, and only upgrade if the feature really needs it.

Review the list of permissions once a quarter and after any library update. Third-party code can add its own permission requests without anyone noticing, and every extra permission lengthens the privacy details you must declare and the questions a reviewer may ask.

Testing permission flows

Permission flows break in quiet ways, so give them their own test pass. The main states to cover are: first request, allowed, declined, declined and asked again, changed in settings while the app is closed, and withdrawn while the app is running. Add a device without the hardware, such as a tablet with no rear camera or a simulator with no location.

Remember language too. Purpose texts and your own explanation screens need translating, and a long German or Finnish sentence may not fit the layout you drew in English. The guide to translating an app for new markets covers that planning.

Deep links add one more case. A link that opens the app straight onto a camera screen skips your onboarding, so the system prompt arrives with no preparation. See deep links and universal links explained for how those entries work. Finally, run the whole set with real testers using the steps in how to test a mobile app before launch.

Getting help with the build

If your project needs several permissions, write down for each one the feature, the moment it is requested, the wording, the fallback and the test. That one-page table is what a developer needs, and it is also what a reviewer will ask about. Liftup Technologies builds apps for iOS and Android, and the mobile app development page explains the kinds of projects it takes on.

Related guides

Questions and answers

When should an app ask for a permission?

Ask at the moment the user taps something that needs it, such as a scan button for the camera. The prompt then arrives with its reason attached. Asking at first launch, before the user has seen any value, usually leads to more refusals.

What if the user says no to a permission?

The app should keep working for everything that does not need it. Show a short message where the feature would be, offer an alternative such as choosing an existing photo, and give a button to open settings if that is the only way to change the answer.

How do I explain why access is needed?

Use two plain sentences: what the app will use, what for, and what happens if the user declines. On iOS the system also needs a short purpose text in the app configuration. Make it specific to the real feature, not a general line about improving the experience.

Can I ask again after a user declines?

Sometimes. iOS normally shows its system dialog once per permission, after which only settings can change it. Android allows repeat requests in some cases but limits them, and the rules vary by version. Check the current documentation for each platform.

Do I need every permission I can think of?

No. Ask for the narrowest access that does the job. Approximate location, a photo picker and a share link often replace precise location, full photo access and contact access, and they give the user less to worry about.

Why do permission wording and behaviour matter for app review?

Store reviewers check that the permissions you request match what the app does. A missing or vague purpose text, or a request with no visible use, can lead to rejection. Keep each request tied to a real feature.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote