Aglet

Triage notification channel language before rewriting settings

“Push,” “alerts,” “activity,” and “email” can describe a technical channel or a user-visible outcome. Triage the vocabulary before adding helper text. Pair each label with event examples, timing, and mute behavior so a person can predict what choosing it changes.

Establish what is happening

  1. Inventory the words

    Record every label, description, category, channel, frequency, and example in the settings surface. Include a term used in navigation and a term used in confirmation. Keep implementation names out of the user-facing comparison unless they are truly meaningful.

  2. Compare the promise

    Ask what a person thinks will happen after selecting or muting the setting, then compare that expectation with event delivery. Distinguish location, timing, urgency, and event type. A familiar word can still be ambiguous without an example.

  3. Set a vocabulary boundary

    Choose one canonical term per channel, define exceptions, and state when the product cannot guarantee delivery. Preserve a known-clear label as a control. Stop when another reviewer can map label to outcome without reading source code.

What to carry forward

The triage output is a channel vocabulary table linking label, event, timing, and outcome. Stop when technical and user-facing meanings are separated. If behavior is inconsistent, route delivery mapping separately from copy cleanup. Preserve the user-facing term for later comparison.

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