Aglet

Prioritize notification copy truncation with preserved context

Copy work matters when a person cannot tell who acted, what changed, or where a button leads before opening. Compare title, body, preview, and action limits across widths. A clearer hierarchy may solve more than deleting words from every notification.

Decide where the work belongs

  1. Name the comprehension cost

    Describe what a person cannot decide from the truncated message and whether the destination can recover the missing context. Compare missing event noun, actor, resource, and action. Keep visual density separate from semantic loss.

  2. Compare shortening choices

    Set title rewrite, body excerpt, action label, priority ordering, line limit, and destination context beside one another. Consider localization and accessible names. Prefer a change that protects the essential decision while removing secondary detail.

  3. Choose the first slice

    Record message family, viewport, owner, and revisit evidence. Decide whether to adjust hierarchy, content, layout, or destination. Preserve the original long and short examples for comparison. Call out which word carries the action promise. Tie the queue choice to the smallest readable action cue.

What to carry forward

Prioritize copy changes where truncation causes wrong openings or hides the action a person needs. The decision should name message family and context retained. If copy is clear but dense, queue layout or secondary-detail reduction instead.

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