Aglet

Learn from notification badge drift and unread mistrust

A badge lesson should preserve what the number promised and why it disagreed with the inbox. Compare later item, group, tab, and device behavior with the original count matrix, then improve one review question about unread meaning, refresh, grouping, or accessible status.

Keep the lesson for the next incident

  1. Keep the count evidence

    Record badge, unread items, groups, filters, read action, tab, device, refresh, and list result. State what the person inferred. This keeps a later count fix tied to a specific trust failure.

  2. Compare later surfaces

    Review an item-level list, grouped view, filtered link, second tab, and device after the change. Look for a new mismatch or a count that changes only after a hidden action. Preserve a reconciled baseline.

  3. Refine one count check

    Require future reviews to state count meaning, test read transition, and compare another surface and zero state. Assign ownership and revisit date. Define the observation that would show the check restored predictable unread navigation.

What to carry forward

The learning record connects one badge mismatch to later evidence and a reusable count reconciliation. Stop when another reviewer can apply it to item and group views. Carry forward uncertainty where sync or platform badge behavior remains 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