ux-research checked
Nielsen Norman Group: 3 Design Considerations for Effective Mobile-App Permission Requests
Documents request copy, timing, decision reversal, informed choice, user benefit framing, contextual asks, and avoidance of dark patterns for permission and consent-like requests.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Consent prompt | Choose consent prompt when the user must actively opt in to a specific optional data use, communication, study, sharing arrangement, personalization feature, AI training use, or sensitive-data processing purpose. | The prompt appears before optional processing begins and states exactly what agreeing enables. | Supports contextual timing, clear request copy, informed choice, decision reversal, and dark-pattern avoidance. |
| Dark-pattern consent | Flag this anti-pattern when accepting optional consent is one click but declining, customizing, or withdrawing requires extra pages, hidden links, confusing labels, or repeated confirmation. | Acceptance, rejection, customization, and withdrawal must be reachable with comparable effort for optional purposes. | Supports informed choice, decision reversal, contextual timing, and avoiding dark patterns in permission and consent-like requests. |
| Disabled controls without recovery | Flag this anti-pattern when a disabled control blocks a task and the surrounding UI does not provide a reachable next step. | Users can discover the cause of unavailability without activating or hovering the disabled control itself. | Permission request guidance supports contextual recovery paths when access or device capability is gated. |
| Permission prompt with no context | Flag this anti-pattern when a permission prompt appears before the user starts a resource-dependent feature or before the interface explains why the resource is needed now. | The product must not invoke the platform prompt from page load, app launch, passive onboarding, timers, or unrelated navigation. | Supports contextual timing, clear request copy, user benefit framing, informed choice, reversal, and dark-pattern avoidance. |
| Permission request | Choose permission request when the user is authorizing an OS, browser, or device resource such as camera, microphone, location, photos, contacts, notifications, clipboard, Bluetooth, motion sensors, storage access, or another powerful feature. | The product evaluates whether permission is truly needed before declaring or requesting the platform permission. | Supports contextual timing, clear request copy, user benefit framing, informed choice, reversal, and dark-pattern avoidance. |
Evidence Role
This source is treated as ux-research evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: Nielsen Norman Group. Last checked: .