Mobile Onboarding and Permission Prompts Review
Design a first-run experience that explains why permissions are needed.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Design the first-run experience. App purpose: [APP_PURPOSE]. Permissions it may request: [PERMISSIONS]. Account required or optional: [ACCOUNT_REQUIREMENT]. First valuable action: [FIRST_VALUE_ACTION]. Sequence the screens so the user reaches the first valuable action in as few steps as possible. Ask for each permission only at the moment it is needed, with a pre-prompt in plain words stating what the app will do with it and what will not work if it is declined. Write the copy for each pre-prompt under 40 words. Return the flow as numbered steps, the copy, fallback behaviour for refusals, a skip option for non-essential steps and measures: completion rate per step and permission acceptance rate. Mark data collection and consent wording [VERIFY] for [REGION]. Add an alternative path for people who skip onboarding: the app should still work, and the explanations should appear in context the first time each feature is used. Include an accessibility check on the onboarding screens and a test in which three new users complete the flow while thinking aloud. Note which steps could be removed without harming understanding.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.