Back to all posts
App UX6 min read·October 26, 2026

When Should Your App Ask for Device Permissions?

TB
ThynkBlox Apps Team
App Engineering

An app should ask for permissions when someone reaches a feature that clearly needs access. Ask for camera access when they choose to take a photo, microphone access when they start a voice recording, and location access when they request nearby results. Explain the purpose, provide a refusal path, and make it clear how to try again later.

Why should the request follow a user action?

Design the request around a task the person has chosen. Someone tapping “Scan a code” has a clear reason to consider camera access. Someone opening a shopping app for the first time may have no reason to consider microphone access.

Avoid collecting permissions during a general welcome flow just because later features might need them. Introduce each request where its purpose is visible. The same principle applies to onboarding for first-time users.

During planning, write down which feature needs each permission. If you cannot name the action, the benefit and the fallback, reconsider whether that permission belongs in the first release. Our guide to scoping an app MVP can help separate essential tasks from optional additions.

What should the explanation say?

Keep any explanation short and specific. Name the device capability, connect it to the current task, and describe any handling of the captured information that matters to the decision.

For a receipt feature, suggested wording is: “Use your camera to photograph this receipt. You can review the photo before uploading it.” Use that wording only if the feature actually includes that review step.

Avoid vague lines such as “Enable access for the best experience.” They leave the person to guess what will happen.

A separate explanation screen is useful when the purpose needs context. For an obvious action, a clear button label and nearby text may be enough. Do not add an extra screen simply to repeat the same sentence.

Never promise that information stays on the device unless that is true throughout the feature.

When should an app request camera access?

Request camera access after someone chooses an action such as “Take photo”, “Scan code” or “Capture document”. Keep browsing, account setup and unrelated features available without it.

Offer an alternative suited to the task:

Camera taskSuggested request pointAlternative to design
Add a profile photoAfter choosing “Take photo”Keep a default image or choose an existing picture
Scan a product codeAfter choosing “Scan code”Enter the code or search by name
Attach a receiptAfter choosing “Photograph receipt”Attach an existing file or enter the details
Capture a required inspection imageBefore starting captureExplain the requirement and let the user leave

Choosing an existing picture or file is a separate flow. Review its access requirements rather than treating it as automatically covered by camera permission.

Where a fresh image is essential, explain why. Do not present an alternative that cannot complete the task.

When should an app request microphone access?

Request microphone access when someone chooses to record audio or enters a feature where speaking is necessary. Do not request it just because the app contains an optional voice feature.

For a voice note, explain what starts the recording, how to stop it, and whether the person can review or discard it before sending. Make those controls visible in the recording flow.

If voice is an input shortcut, keep typing available. If the task is an audio submission, such as recording a pronunciation exercise, text may not fulfil the same purpose. Explain that requirement and offer a way to leave or return later.

Do not imply that granting microphone access begins a recording. Design permission, recording and sending as distinct decisions, with clear feedback at each step.

When should an app request location access?

Request location access when someone chooses a task such as “Use my location”, “Find nearby” or “Start route”. First decide how much location detail the task actually needs.

For browsing services in a city, consider a city selector or postcode entry. For a delivery address, let the person enter and confirm the address themselves. Treat a suggested position as something to review.

Separate a one-off lookup from a feature intended to follow movement. A person finding nearby shops has chosen a different task from someone starting a journey-tracking feature.

If the product needs location while the person is away from the screen, explain that behaviour separately. Define when collection starts, when it stops and how the person controls it. Confirm the platform requirements before promising any particular access option.

What should happen when someone refuses?

Keep the refusal response local to the feature that needs access. Declining the camera should leave a manual code-entry option available if that option can complete the task.

Use neutral wording. “Camera access is off. Enter the code below or try scanning again” gives the person a next step. Avoid language that blames them or suggests they made a mistake.

Do not immediately reopen the request or ask again every time they visit the screen. Let another deliberate action start a retry.

Preserve work already entered. A person who declines location should not lose a completed address form. Someone leaving a microphone request should return to their draft.

When no alternative exists, explain what cannot continue and provide a clear exit.

How should settings recovery work?

Design recovery for the situation where the app cannot offer the permission request again through the current flow. Confirm the available behaviour on each supported platform before choosing the instructions.

Show a settings route when the person tries to use the affected feature. Explain which access they need to change and why, then offer an “Open settings” action where supported.

Keep a “Continue without access” or “Back” option alongside it.

When the person returns, check the current permission state. If access is available, let them resume the task. If it is still unavailable, keep the explanation and alternative usable. Do not treat opening settings as proof that permission was granted.

Avoid detailed menu directions unless they have been verified for the devices the app supports.

What does a complete permission flow look like?

Consider an illustrative receipt-entry feature:

  • The person opens a new expense and enters a description.
  • They choose “Add receipt”, then “Take photo”.
  • The app explains that the camera is needed to photograph the receipt.
  • If access is granted, they take a photo and review it before attaching.
  • If access is refused, their draft remains available with “Choose file” and “Continue without receipt”, if both are valid choices.
  • If they try the camera again and settings recovery is necessary, the app explains the next step.
  • After returning, they can resume without re-entering their description.

This example makes the permission part of a complete task. The design includes success, refusal, recovery and preservation of earlier work.

What common mistakes should you avoid?

Asking for several permissions together. Give each request its own feature context. Camera access for scanning does not explain a separate request for location.

Making optional access an entry requirement. If manual entry can complete the task, keep it available.

Treating permission as an upload decision. Explain recording, capture, storage and sharing at their relevant steps. A permission explanation should not hide those choices.

Promising platform behaviour without checking it. Specify the intended experience, then verify which prompts, access levels and settings routes are supported.

Testing only approval. Include refusal, changed settings, interrupted flows and retries in your app testing before release.

What should the design checklist include?

Before approving a permission-dependent feature, confirm:

  • The request follows a clear user action.
  • The explanation names the task and matches actual behaviour.
  • The requested access is limited to what the feature needs.
  • Refusal has a useful next step or a clear exit.
  • Existing work survives refusal and settings recovery.
  • Capture, recording and sharing have clear controls.
  • Returning from settings triggers a fresh permission check.
  • Alternatives are tested as complete user journeys.

Keep camera, microphone and location decisions tied to their own tasks. Plan notification requests separately because their purpose and timing need a different discussion; our guide to push notifications that users keep on covers them.

Frequently asked questions

Should an app ask for every permission on first launch?

As a design rule, ask when the relevant feature is reached. If the opening task genuinely requires access, explain that connection before requesting it.

Is an explanation screen always necessary?

No. Use one when it adds information needed for the decision. A clear action label and brief supporting text may be sufficient for a straightforward task.

Should the app ask again after a refusal?

Offer another attempt when the person deliberately returns to the feature. Avoid automatic repeat requests. Provide settings recovery when the supported platform requires it.

Can a feature require permission without an alternative?

Yes, when access is essential to the task. Explain the limitation honestly, provide an exit, and keep unrelated parts of the app available. Features that use the camera or photos are covered in making photo uploads reliable.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.