Aglet

Learn from notification badge meaning and metric confusion

A badge lesson should preserve what the number promised and what the destination revealed. Compare later zero, unread, grouped, and filtered states with the original meaning table, then improve one review question about unread definition, accessible wording, or text-equivalent status.

Keep the lesson for the next incident

  1. Keep the indicator evidence

    Record icon, value, count source, unread records, label, zero state, destination, and nearby metrics. State what a person inferred. This keeps later shell work tied to a semantic mismatch rather than a visual preference.

  2. Compare later states

    Review one and several unread items, grouped lists, filters, and no-visual-badge contexts after the change. Look for a destination that still surprises or a label that counts the wrong thing. Preserve a clear zero control.

  3. Refine one meaning check

    Require future reviews to state count definition, activate the indicator, inspect destination, and verify accessible text. Assign ownership and revisit date. Define the observation that would show the check prevented metric or unread confusion.

What to carry forward

The learning record connects one badge misunderstanding to later evidence and a reusable semantic review. Stop when another reviewer can apply it to a new shell surface. Carry forward uncertainty where platform badging or cross-device count is outside direct control.

Technical background: W3C guidance.

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