A checkbox is a control for one independent yes or no. Ticking one says nothing about its neighbours, which is the whole difference between a checkbox and a radio button, and the reason a column of them can be read in any order. The six blocks here run from a single choice on a card up to a table that selects every row at once.
The state people get wrong is the mixed one. Indeterminate is not a third answer anyone can pick. It is what a parent shows when its children disagree, and it exists so a select-all box can be honest about a partial selection. Decide what clicking it does before you draw it; usually it fills the set, and clicking again empties it. The other quiet failure is the hit area. The row or the card is the control, not the little square inside it, and a checkbox that only responds on the box is a miserable thing to tap on a phone.
A settings screen where each row is its own yes or no (a channel, a digest, a mention alert) with a sub-label and a description doing the explaining the label has no room for.
Select some records, select them all from the header, then export or archive what is selected. The header box has to show the mixed state or the reader cannot tell a partial selection from none.
Roles and scopes, where a parent stands for a set of children. Ticking the parent grants the set, clearing one child drops the parent to mixed, and the indent is what makes the relationship readable.
Integrations presented as cards with the brand logo leading, where several are turned on at once and some are already fixed: read-only because an admin set them, or disabled because the plan excludes them.
A checkbox is for a value a form collects and a save commits, and it sits comfortably in a column with other checkboxes. A switch is for a setting that takes effect the moment it is flipped, with no save anywhere. If your checkbox applies instantly, people will still look for a save button; if your switch needs one, they will not.
It means some of the things this box stands for are on and some are not. It is a summary of children, never a value a person picks, so it belongs on a select-all box or a group parent and nowhere else. Clicking it normally selects everything under it, and clicking again clears them. It must be exposed as mixed rather than unchecked.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
A checkbox is a control for one independent yes or no. Ticking one says nothing about its neighbours, which is the whole difference between a checkbox and a radio button, and the reason a column of them can be read in any order. The six blocks here run from a single choice on a card up to a table that selects every row at once.
The state people get wrong is the mixed one. Indeterminate is not a third answer anyone can pick. It is what a parent shows when its children disagree, and it exists so a select-all box can be honest about a partial selection. Decide what clicking it does before you draw it; usually it fills the set, and clicking again empties it. The other quiet failure is the hit area. The row or the card is the control, not the little square inside it, and a checkbox that only responds on the box is a miserable thing to tap on a phone.
A settings screen where each row is its own yes or no (a channel, a digest, a mention alert) with a sub-label and a description doing the explaining the label has no room for.
Select some records, select them all from the header, then export or archive what is selected. The header box has to show the mixed state or the reader cannot tell a partial selection from none.
Roles and scopes, where a parent stands for a set of children. Ticking the parent grants the set, clearing one child drops the parent to mixed, and the indent is what makes the relationship readable.
Integrations presented as cards with the brand logo leading, where several are turned on at once and some are already fixed: read-only because an admin set them, or disabled because the plan excludes them.
A checkbox is for a value a form collects and a save commits, and it sits comfortably in a column with other checkboxes. A switch is for a setting that takes effect the moment it is flipped, with no save anywhere. If your checkbox applies instantly, people will still look for a save button; if your switch needs one, they will not.
It means some of the things this box stands for are on and some are not. It is a summary of children, never a value a person picks, so it belongs on a select-all box or a group parent and nowhere else. Clicking it normally selects everything under it, and clicking again clears them. It must be exposed as mixed rather than unchecked.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Choose which updates reach your inbox.
Choose what reaches you, and where.
Choose what reaches you, and how often.
Choose which updates reach your inbox.
Choose what reaches you, and where.
Choose what reaches you, and how often.