What are app permissions — and why you only get to ask once

Here's an unpleasant thing. Almost everything in code can be rewritten: a bad button, a broken request, a silly name. A permission request pretty much can't. If someone says "no" once, the system will stop showing you that dialog. Not tomorrow, not after an update.
And here's the annoying part: the AI assistant building your app usually puts the permission request right at the start — on the first screen, "to get it out of the way." That's exactly where people say no. Let's unpack how this works and where to ask instead.
What a permission is, in plain words
A permission is access to something sensitive: camera, microphone, location, contacts, notifications. Anything that could hurt privacy sits behind a separate door.
The important part is who guards that door. Not your app. The "Allow access to camera?" dialog is drawn by the operating system, on top of your interface. You can't restyle it, move the "No" button, or show it twice. All you can do is ask the system to show it.
It works in two layers:
- Declaration. In your app's config file you list up front which kinds of access you intend to ask for. Not declared means you can't ask at all, no matter how badly you need it.
- The runtime request. The user sees the system dialog and decides. The answer is remembered.
That second layer is where beginners lose access forever.
One shot: why a denial is nearly permanent
Android says it plainly. If someone taps "Deny" for a given permission more than once during your app's lifetime on that device, the docs put it this way: the user will no longer see the system permissions dialog when your app requests that permission again — the action implies "don't ask again" and counts as a permanent denial. Internally the system marks that state as USER_FIXED.
On iOS it's stricter still: you don't even get two denials. About location, Apple writes literally that your app can no longer ask for authorization after the user responds to the prompt, and that calling the method again has no effect. It quietly does nothing — no dialog, no error.
Which gives you the one thing worth remembering:
Android warns about this itself: only ask when access is needed for a specific feature — otherwise you may inadvertently lose the ability to ask again.
So the question isn't "how" but "when"
Since you only get one shot, the moment of asking is a product decision, not a line of code. What works:
- Not at launch. On the first screen a person doesn't even know what your app is. A location prompt there reads as "why do you want my location, we just met."
- At the moment of value. They tapped "Find nearby" — now the request is obvious. They already want the result; access is just a step toward it.
- Your screen first, the system's second. Show a one-paragraph explanation of your own: why you need access and what they get. Whoever disagrees closes your screen, and you keep the system prompt for later. Android even gives you a dedicated check for whether you should show a rationale before asking again.
- Plan for "no." The app has to work without access. Someone declining notifications isn't a reason to show an empty screen.
It's the same logic as with a background task: the phone and its owner owe you nothing — you negotiate.
What to do when they already said no
You can't bring the dialog back — but there's a path. When someone taps a feature that needs missing access, show a short message: access is off, you can turn it on in settings — plus a button that opens your app's page in system settings. Don't dump them into general settings; nobody hunts for your app in a list.
There's a nice wrinkle too. On Android, if an app hasn't been used for a few months, the system auto-resets previously granted sensitive permissions. Which means access can vanish for someone who was active yesterday — so check it before every use, not once at install.
And don't ask for extras. Every declared permission shows up on your store page, and a long list scares people off before they even install.
Are permissions the same as the privacy details in the store?
No. Permissions are the technical door: without them your code simply won't get the data. The store's privacy card is a promise to the store and the user about what you collect and where you send it. One doesn't replace the other: you can have camera access and honestly state that photos never leave the device.
Are notifications a permission too?
Yes, and you have to ask for them on both platforms. That's exactly why pushes "don't arrive" on a phone where everything looks configured: there's no permission, and a push token without one is useless.
Why does my app ask for access it doesn't need?
Usually a library. You add an analytics or ads SDK and it drags its declared permissions into your app. Before shipping, look at the final list — there are surprises there, and you're the one who'll have to explain them.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





