Asking for camera and photo access in your app
Short answer: Ask for camera or photo access at the moment someone taps the feature that needs it, explain the reason in one specific sentence, and make sure the app still works if they say no. Where you only need people to pick a few existing photos, a system photo picker can avoid asking for broad library access at all. Most permission problems come from asking too early, asking vaguely or leaving users stuck after a refusal.
Apps for trades, insurance claims, property inspections, deliveries, repairs and retail often need photos: proof of work, damage reports, receipts, product shots. The permission prompt is a small moment that decides whether the feature gets used. Here's a checklist for getting it right on iOS and Android.
What the platforms expect
Apple's documentation on requesting access to protected resources says to provide a purpose string (also called a usage description) explaining why you need access. The system generates the prompt's title, including your app's name, and shows your message beneath it. Apple notes that if access is granted, the system remembers and doesn't ask again; if it's denied, that attempt and any further attempts fail in a resource-specific way. It also stresses accessing only what your app needs to do its job, and shows an App Store submission error that appears when a required purpose string is missing from the app's Info.plist.
Android's guide to requesting runtime permissions sets out basic principles: ask for a permission in context, when the user starts interacting with the feature that needs it; don't block the user, and always allow them to cancel an explanatory screen; and if a permission is denied or revoked, gracefully degrade the app so the user can continue, possibly by disabling just that feature. It also notes that choosing "Deny" twice marks a permission as permanently denied.
Android's photo picker documentation describes a system picker for choosing photos and videos, available on Android 11 (API level 30) and higher with Google System Updates, with a backported version for older devices (Android 4.4 to 10) that support Google Play services.
Checklist: before you ask
- [ ] Do you need the permission at all? If users only choose existing photos, a system picker may give access to just the items they select. Use broad library access only for features that genuinely need it, such as browsing the whole library inside your app.
- [ ] Camera or library, or both? Many upload flows need either "Take photo" or "Choose from library". Treat them as separate decisions.
- [ ] List every feature that triggers a request so purpose strings are written for each.
Checklist: timing
- [ ] No permission prompts on first launch. Ask when the user taps "Add photo", "Scan receipt" or "Photograph damage", following Android's "in context" principle.
- [ ] Optional pre-prompt screen. For features where the reason isn't obvious, a short screen of your own before the system dialog can help, but it must include a way to cancel.
- [ ] One request at a time. Don't stack camera, location and notifications in a row.
Checklist: wording
The purpose string is your one sentence on the system dialog. Make it:
- [ ] Specific to the feature: "Take photos of completed work to attach to the job report" rather than "This app needs camera access".
- [ ] Clear about what happens to the photo: where it goes, who sees it.
- [ ] Free of pressure: no "required for the app to work" if it isn't.
- [ ] Consistent with your app's language (British English for UK users, translated where your app is localised).
Hypothetical examples:
| Weak | Better |
|---|---|
| "Allow camera access?" | "Take a photo of your receipt so we can add it to your expense claim." |
| "We need your photos." | "Choose photos of the damage to include with your claim. Only the photos you select are uploaded." |
| "Camera required." | "Scan the barcode on the parcel to confirm delivery." |
Checklist: after a refusal
- [ ] The rest of the app still works. Android's guidance is explicit: degrade gracefully.
- [ ] Offer an alternative: choose from library instead of camera, enter a code manually instead of scanning, or upload later from a computer.
- [ ] Explain how to change it. If the user tries the feature again after denying, show a short message explaining it can be enabled in the phone's settings, with a button that opens your app's settings page.
- [ ] Don't nag. Repeated custom prompts after a clear "no" annoy users and rarely change minds.
Checklist: privacy and data
- [ ] Upload only what's needed. Resize images and strip location metadata if you don't need it.
- [ ] Say where photos are stored and for how long, in your privacy information.
- [ ] Match your store disclosures. App Store and Google Play listings ask about data your app collects; make sure your answers reflect the photo features. Check each store's current requirements.
Checklist: testing
- [ ] Fresh install, permission granted
- [ ] Permission denied once, then requested again
- [ ] Permission permanently denied (Android) or denied (iOS), feature retried
- [ ] Permission revoked from settings while the app is running
- [ ] Photo picker on an older Android device
- [ ] Limited or selected-photos access on iOS, if your app supports the library
FAQ
When is the best time to ask for camera permission?
When the user starts the feature that needs it, such as tapping "Take photo". Android's documentation recommends asking in context, and asking at launch tends to get refusals because the reason isn't clear yet.
Can I ask again after someone says no?
On iOS, the system won't show the dialog again after a denial; the user must change it in settings. On Android, repeated denials can make the denial permanent. Explain and link to settings instead.
Do I need photo library permission to let users upload a photo?
Not always. System photo pickers let users choose specific images, which may avoid broad library access. Check the platform docs for the picker you use.
Will a vague purpose string get my app rejected?
Apple's documentation shows that a missing purpose string blocks submission. Beyond that, clear, specific wording is good practice for users and reviewers alike.
Building a photo or scanning feature into your app and want users to actually allow it? Describe the feature and we'll help you design the permission flow.