Limited system-prompt space requires a pre-prompt
Aliases: pre-permission dialog · permission education screen · contextual primer
What it is
A permission pre-prompt is a product-owned explanation of function, data scope, and alternatives shown before the operating-system permission sheet. It supplements constrained system copy but must not impersonate system authorization, preselect for the person, or label its own action “Allow” before a second real decision. The product supplies context; the system grants the protected capability.
Why it happens
System sheets need consistency across applications and therefore expose a permission class with limited purpose text, not the product's full task context. A pre-prompt can establish necessity through a feature preview and alternatives before the platform confirms capability scope. When it only adds an acceptance step or hides exit, the second layer creates fatigue and commitment pressure to remain consistent with the first click.
Studying it
Experiments can compare a direct system sheet, contextual primer, and promotional pre-prompt on purpose comprehension, system choice, task success, later withdrawal, and perceived manipulation. Actions at each layer must be logged separately; a pre-prompt click is not permission. Recall tasks can test whether people distinguish application explanation from operating-system control. Confusion about which layer authorized access is a role-signaling failure.
Where it stops holding
Not every request needs a primer. When the initiating action makes intent clear and system text is sufficient, an added page is friction. Platform policies may constrain re-prompting after refusal or manipulative primers and must be checked for the current system. A pre-prompt cannot promise granularity the platform lacks or loop-block a feature after decline.
Applying it
- Use a primer only when the system sheet cannot establish product context, showing the feature, requested scope, and permission-free alternative.
- Name the primary action with process semantics such as “Continue to system settings,” explicitly saying the next layer decides.
- Provide an equally visible exit or not-now route and collect no protected data in the primer.
- Test whether users identify the authorizing layer, exercising continue, cancel, and system-decline branches; correct loops, authorization misconceptions, and post-decline flows.