A dot means presence; a number means quantity
Aliases: unread dot · numeric badge · presence mark
What it is
A dot asserts only that something unhandled is here, not how many somethings. A numeric badge asserts a count. They are not two volumes of the same control; they answer two questions: whether to go in, and how large the pile is. Drawing “3” as a numberless dot withholds the estimate needed to decide whether to handle it now. Writing “new activity” as “99+” puts count-anxiety on a fact that could have been mere presence. Which to use starts with whether the next step needs quantity in order to plan.
Why it happens
Quantity enters the decision when handling has a cost that scales with count: answering three messages and answering thirty are different time boxes. A number lets people rank and chunk. Presence enters the decision when one item is enough to change behavior: someone mentioned you, so you enter that tab; how many can wait until inside. A dot aims attention at an entrance; a number aims it at workload. Misuse distorts motive: social products use numbers to urge opening, tools use dots to mark state; swapped, the tool gets noisy and the social surface starts feeling like a todo list. A corner mark also becomes part of the entrance’s identity; people use “is there a dot” as their unread model. If that model disagrees with the real count, the first mismatch inside the door starts the drop in trust.
Where it stops holding
When the count is huge, a number becomes an unreadable blob. “99+” is a fold in the quantity channel, not a retreat to a dot; the fold still says “many,” the dot only says “some.” At zero there should be neither a “0” nor a dot; disappearance of both marks is what “cleared” looks like. For a stream that cannot be counted (“new activity” that is not discrete items), a number is fake and a dot is right. In an accessible name, a dot should say “has unread,” a number “12 unread”—not both “badge.” Under color-blind viewing the redness of a red dot is not enough; the shape (a solid circle) is the presence channel, color an overlay.
Applying it
- Use a number on entrances whose handling cost scales with count; use a dot where one item is enough to enter and the count has no planning value.
- Do not switch the same entrance from dot to number day by day unless the count has crossed a planning threshold, and make that channel change intelligible.
- A count must match the list seen after entering; if it cannot, do not show a number.
- Verify by hiding the digits and leaving the shape, then asking “how many.” If the task actually needs that number to decide whether to act now, it should not have been a dot.