Permission requests

Permission requests determine feature adoption and trust. Without content standards, users face jarring system dialogs with no context, like being suddenly asked for camera access with no explanation why. This aggressive approach leads to reflexive denials, permanently limiting product functionality.

Build permission templates that explain value before asking. Create context formulas: "{Feature} needs {permission} to {specific benefit}." For example: "Video calls need camera access to let teammates see you." Never request permissions on app launch—wait until users try the relevant feature. Context transforms suspicious requests into logical next steps.

Map permissions to user benefits, not technical requirements. Document pre-permission screens that prepare users before triggering system dialogs. Define fallback experiences for denied permissions with gentle re-engagement prompts. Include character limits that work within system constraints. This framework maximizes opt-ins while respecting user choice.