Every permission your app asks for is a small question to the user: do I trust this app with this? Ask for too much and some people tap Deny, some uninstall, and Google may ask you to justify it in review. Ask for exactly what you need, at the moment you need it, and most people say yes without thinking about it.
This guide covers how Android permissions work, how to ask well, and how to cut the list down before you publish.
Part 1: How permissions work
Android groups permissions by how risky they are. Some, like internet access, are granted when the app is installed. Others, like the camera, location or reading contacts, are called runtime permissions: the app must ask while it is running, and the user can allow or deny. The full list and the rules are in the Android documentation on app permissions.
Part 2: Ask at the right moment
- Wait until it is needed. Ask for the camera when the user taps Scan, not on the first screen.
- Say why, briefly. One sentence before the system dialog, such as "To scan a barcode we need to use the camera."
- Respect the answer. If the user denies, offer an alternative, such as typing the code by hand, and do not nag with repeated prompts.
- Point to settings kindly. If the user denied permanently, explain how to change it in settings only if they try the feature again.
Part 3: Check what your app really asks for
Open your final merged manifest in Android Studio and read every permission line. Third-party libraries, especially for ads or analytics, can add their own. If you see one you did not expect, find out why it is there. You can sometimes remove it in the manifest or choose a lighter library.
| Question | What to do |
|---|---|
| Is the feature core to the app? | Keep the permission |
| Is it used by one rarely used feature? | Ask only when that feature is used |
| Did a library add it? | Check if you can remove it or the library |
| Can the task be done with a system picker instead? | Use the picker and skip the permission |
Part 4: Sensitive permissions and Google Play
Some permissions, such as reading SMS or call logs, background location or access to all files, are restricted on Google Play. You may have to fill out a declaration and explain the core use of the app. Check the current rules in Play Console Help before you build a feature around one of them.
Part 5: Test the unhappy paths
- Deny every permission and use the app.
- Allow once, then revoke it in settings while the app is running.
- Test on an older and a newer Android version, since the behaviour differs.
- Read the permission list in the installed app's settings as a user would.
Frequently asked questions
Do I need a permission for internet access?
Yes, it is declared in the manifest, but it is a normal permission granted at install.
Why does my app show permissions I never added?
Probably a library did. Check the merged manifest.
Can I ask again after the user says no?
Android limits repeated prompts. Explain the value in your own screen, and let the user decide.
Do fewer permissions help my ranking?
Not directly, but they build trust and make the review process smoother.
Related reading
- What every Android app privacy policy must include: describe what you collect
- How to write a Google Play store listing that gets installs: keep the listing consistent
- Why I build offline-first apps: fewer permissions, fewer failure points
The best permission list is a short one that you can explain in a sentence each.