Aglet

Investigate notification copy truncation across layouts and previews

An investigation should show where essential meaning disappears from notification copy. Compare source, rendered desktop and narrow states, preview, action label, and destination. Vary one content or width boundary at a time and keep accessibility text in scope. Include one example where the action survives but the context does not.

Build a useful investigation brief

  1. Build the copy matrix

    List event, actor, resource, title, body, action, destination, source length, rendered lines, viewport, locale, preview, and accessible name. Include a short control and a long message with essential context near the end.

  2. Trace the first loss

    Change width, locale, title, body, or action one at a time and compare what remains understandable. Record whether the destination restores context and whether accessible text differs from the visual message.

  3. Write the hierarchy brief

    State first missing context, affected message family, and competing explanations such as source order, layout, or localization. Recommend one bounded copy or rendering experiment with a pass condition. Do not assume character count alone predicts comprehension. Record the line where event identity disappears from view.

What to carry forward

The investigation is complete when the first loss of event, actor, resource, or action context is reproducible across selected layouts, or the unknown is explicit. Stop with one bounded hierarchy experiment. Keep accessible and preview behavior separate from the main visual row.

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