Aglet

Triage notification permission timing before showing a prompt

A permission prompt shown before a person understands its value can end a communication path before it begins. Triage the trigger as a user-intent question. Capture the feature context, gesture, rationale, allow or decline result, and later settings path without assuming permission was granted.

Establish what is happening

  1. Capture the trigger

    Record page or feature, user gesture, event context, rationale copy, prompt timing, allow, deny, dismiss, and later settings path. Include a page-load path and a user-requested path. Keep platform permission state separate from in-app choice.

  2. Compare informed context

    Ask what the person had just chosen or tried to do and whether the prompt explained the notification type. Compare generic onboarding with a specific request. A delayed prompt can still be unclear if its benefit is not stated.

  3. Set a permission boundary

    State when to ask, what remains useful after denial, and how a person can revisit the choice. Preserve a no-prompt control. Stop when another reviewer can explain the trigger and recovery without relying on an assumed allow.

What to carry forward

The triage output is a permission trigger and recovery boundary with user intent, rationale, result, and settings path. Stop when informed request and surprise prompt are distinguishable. If platform state is unknown, keep the product flow conservative and record the gap.

Technical background: Chrome developer documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow