Aglet

Verify notification defaults across new and returning contexts

Verification should prove that defaults are relevant to the moment, understandable before commitment, and reversible later. Test new and returning contexts, then inspect saved state and settings. Keep platform permission behavior separate from the product copy and event choice being verified.

Check whether the outcome improved

  1. Check a new context

    Open the first-use path and confirm default labels, rationale, optional categories, and skip action. Accept one relevant event and record the resulting saved state. Ensure the choice does not imply more channel delivery than promised.

  2. Check skip and return

    Skip or postpone the choice, return through settings, and enable one category later. Verify the path is discoverable and the saved state matches the person’s action. Test a role or invitation context when its default differs.

  3. Review reversal and copy

    Disable the choice and inspect status feedback, narrow layout, and permission-denied fallback. State tested contexts and channels. Leave a partial pass where platform settings or actual delivery cannot be observed directly.

What to carry forward

Verification passes when contextual defaults are understandable, skipped choices remain available, and reversal changes the documented state. If one role or platform path is untested, record that gap. An enabled checkbox alone does not prove an informed notification choice.

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