An operating system often provides only one good opportunity to request permission. If an app asks for access on first launch without visible value, users reasonably decline and trust decreases.
Request permission at the relevant action
Show the request when the user activates a feature requiring the camera, location or notifications. The reason immediately becomes understandable.
Explain the exact use
Use a pre-permission message explaining what will happen and what benefit it offers. Avoid vague wording about a better experience.
Prefer the smallest scope
Use approximate instead of precise location, selected photos instead of the whole library and one-time access where sufficient. Do not ask for a possible future need.
Design the experience after refusal
Provide manual input, upload or limited functionality. Do not trap users in repeated prompts or a dead end.
Review use and retention
Record which features use the permission, when that use stops and when data is deleted. Remove a permission when it is no longer necessary.
This framework is an original editorial methodology developed by DigitalNow.