A button group is a row of buttons treated as one control, sharing a container and answering a single question between them. Three different things ship under that name and they are not interchangeable: a row of peers where exactly one cell is the answer, an ordered walk where the ends outrank the middle, and one or two actions welded to a field they only make sense against.
The join is not decoration. Connected cells share one border and read as a single object, which is what makes the choice exclusive: press another and the first goes off. Separated cells are pills with a gap between them, and that gap is what tells a reader more than one can be on at once, which is why filter rows are built that way. Changing the join changes what the row means rather than how it looks, and a group drawn connected but behaving as a multi-select will be mis-pressed for as long as it exists.
Grid or list, day or week, source or preview. Connected cells, one answer, nothing emphasised: the row exists to show the alternatives as much as it exists to show the current choice.
Separated pills above a result set, with several on at once. The gap does the explaining, telling the reader these toggle independently before anyone has to click one and find out.
Copy beside a share link, a calendar beside a date, a currency beside an amount. The buttons share the field's border and inherit its header, hint and error, so the whole thing reads as one control.
A billing or workspace panel where a field group sits among switches and a footer that commits. The group is the input; the footer's primary action is the only emphasised thing on the panel.
Not in a row of peers. Emphasising one cell answers the question the reader was asked to answer, and the group stops reading as a set of equals. The exception is a group that walks an ordered set, where the ends really do outrank the middle: moving forward is the expected action, and the numbers between are a way of skipping rather than a choice.
Around six before the labels begin fighting for room. Past that, a dropdown carries the options without widening the row. When a group does run out of space, let it wrap onto a second line rather than scroll, since a scrolling group hides its own options behind a gesture, and a set that has become two rows should lose the full pill radius that only made sense as one.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
A button group is a row of buttons treated as one control, sharing a container and answering a single question between them. Three different things ship under that name and they are not interchangeable: a row of peers where exactly one cell is the answer, an ordered walk where the ends outrank the middle, and one or two actions welded to a field they only make sense against.
The join is not decoration. Connected cells share one border and read as a single object, which is what makes the choice exclusive: press another and the first goes off. Separated cells are pills with a gap between them, and that gap is what tells a reader more than one can be on at once, which is why filter rows are built that way. Changing the join changes what the row means rather than how it looks, and a group drawn connected but behaving as a multi-select will be mis-pressed for as long as it exists.
Grid or list, day or week, source or preview. Connected cells, one answer, nothing emphasised: the row exists to show the alternatives as much as it exists to show the current choice.
Separated pills above a result set, with several on at once. The gap does the explaining, telling the reader these toggle independently before anyone has to click one and find out.
Copy beside a share link, a calendar beside a date, a currency beside an amount. The buttons share the field's border and inherit its header, hint and error, so the whole thing reads as one control.
A billing or workspace panel where a field group sits among switches and a footer that commits. The group is the input; the footer's primary action is the only emphasised thing on the panel.
Not in a row of peers. Emphasising one cell answers the question the reader was asked to answer, and the group stops reading as a set of equals. The exception is a group that walks an ordered set, where the ends really do outrank the middle: moving forward is the expected action, and the numbers between are a way of skipping rather than a choice.
Around six before the labels begin fighting for room. Past that, a dropdown carries the options without widening the row. When a group does run out of space, let it wrap onto a second line rather than scroll, since a scrolling group hides its own options behind a gesture, and a set that has become two rows should lose the full pill radius that only made sense as one.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Showing Weekends, holidays
Week 45 · 6 items
Ship the tabs refresh on Friday; the thumb now slides between views, and every list is one tab stop.
Selection: Bold · left · medium
Showing Weekends, holidays
Week 45 · 6 items
Ship the tabs refresh on Friday; the thumb now slides between views, and every list is one tab stop.
Selection: Bold · left · medium