Aglet

Triage notification copy truncation before shortening messages

Short notification copy can be readable yet omit the event or action context that makes it useful. Triage truncation before rewriting every message. Capture title, body, labels, preview, line wrapping, localization, and destination so brevity does not become ambiguity. Review the shortest surface first because it sets expectations.

Establish what is happening

  1. Capture the rendered copy

    Record title, body, event noun, actor, resource, action, destination, character or line limit, viewport, and accessible name. Include a desktop, narrow, and preview state. Keep a message that is already concise as a control.

  2. Find the essential context

    Ask which noun, state, actor, or action lets a person decide whether to open. Compare truncating decoration with truncating the event or destination. A short title that hides the resource can be less useful than a longer one.

  3. Set a copy hierarchy

    State what stays in title, body, action, preview, and accessible name, plus what happens when localization expands. Preserve an intentional fallback. Stop when another reviewer can shorten the message without removing the decision context.

What to carry forward

The triage output is a copy hierarchy with essential context, truncation boundary, layout, and destination. Stop when readable brevity and missing meaning are distinguishable. If the event itself is unclear, route content definition before adjusting length.

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