Aglet

Investigate notification defaults through first-use paths

An investigation should show how the first-run context leads to a default and whether the choice survives into normal settings. Replay new, invited, and returning paths, compare enabled events, and test one user-driven alternative without treating acceptance as proof of value.

Build a useful investigation brief

  1. Build the onboarding matrix

    List entry context, role, event category, channel, default, rationale, skip action, permission state, and saved preference. Include a path with no prompt. Record what is known before the first event is delivered.

  2. Trace the choice forward

    Accept, skip, and revisit the settings path; compare later event visibility and channel state. Check whether a platform permission denial changes the in-app choice. Record a reversible path so the investigation includes recovery.

  3. Write the default brief

    State the context that justifies the default, the first ambiguity, and competing explanations such as copy, timing, or category scope. Recommend one bounded experiment with a pass condition based on informed choice and predictable reversal.

What to carry forward

The investigation is complete when each selected first-use path has a reproducible default and later consequence, or the unknown boundary is explicit. Stop with one context experiment. Do not infer notification value from acceptance alone; preserve skipped and reversed choices.

Technical background: Apple 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