Radio groups are sets of options where exactly one can be chosen, and choosing one clears whatever was chosen before. The five here show how far the row stretches: a frequency list giving each option a sub-label and a description, a plan selector whose cards hold a badge, a feature list and a price with the billing period as a separate toggle, a settings screen with several independent single choices in labelled sections, a payment list marking the current default, and the option drawn as a card with an avatar and a trailing radio.
The behaviour people notice is the keyboard. A radio group is one tab stop rather than one per option, and the arrow keys move focus and the selection together inside it, which is why a group assembled out of plain buttons feels subtly broken to anyone not using a mouse. The other thing worth knowing is that radios have no route back to nothing. A choice can only be changed, never undone, unless you supplied a none-of-these option or a clear action.
An upgrade screen where each plan is a card with its price and what it includes, and the billing period is a toggle above them, because period and plan are two choices rather than one list of four.
A list of saved cards with one marked current. The radio marks intent and the footer actions commit it, so nothing moves until the person confirms and a misclick cannot redirect a charge.
A settings section asking how often a digest should arrive. Immediate, daily and weekly cannot all be true at once, so radios encode a rule that already exists in the data rather than imposing one.
A single-answer question whose options need a sentence each to be understood. A dropdown would hide those sentences behind an interaction; radios keep every option and its explanation on the page together.
Use a radio group when the options are meant to be compared before one is chosen and there are few enough to sit on screen together. A select hides everything but the current value, which suits long familiar lists such as countries, and works against you when the differences between options, like price or limits or what is included, are the reason a choice is being made.
Pre-select a default when one option is clearly safe and most people want it, since it saves a click and communicates the expected answer. Leave the group empty when the choice carries consequences the person should make deliberately, such as billing or data sharing, because a pre-selected option tends to be accepted without being read. If nothing is safe, mark the group required instead.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Radio groups are sets of options where exactly one can be chosen, and choosing one clears whatever was chosen before. The five here show how far the row stretches: a frequency list giving each option a sub-label and a description, a plan selector whose cards hold a badge, a feature list and a price with the billing period as a separate toggle, a settings screen with several independent single choices in labelled sections, a payment list marking the current default, and the option drawn as a card with an avatar and a trailing radio.
The behaviour people notice is the keyboard. A radio group is one tab stop rather than one per option, and the arrow keys move focus and the selection together inside it, which is why a group assembled out of plain buttons feels subtly broken to anyone not using a mouse. The other thing worth knowing is that radios have no route back to nothing. A choice can only be changed, never undone, unless you supplied a none-of-these option or a clear action.
An upgrade screen where each plan is a card with its price and what it includes, and the billing period is a toggle above them, because period and plan are two choices rather than one list of four.
A list of saved cards with one marked current. The radio marks intent and the footer actions commit it, so nothing moves until the person confirms and a misclick cannot redirect a charge.
A settings section asking how often a digest should arrive. Immediate, daily and weekly cannot all be true at once, so radios encode a rule that already exists in the data rather than imposing one.
A single-answer question whose options need a sentence each to be understood. A dropdown would hide those sentences behind an interaction; radios keep every option and its explanation on the page together.
Use a radio group when the options are meant to be compared before one is chosen and there are few enough to sit on screen together. A select hides everything but the current value, which suits long familiar lists such as countries, and works against you when the differences between options, like price or limits or what is included, are the reason a choice is being made.
Pre-select a default when one option is clearly safe and most people want it, since it saves a click and communicates the expected answer. Leave the group empty when the choice carries consequences the person should make deliberately, such as billing or data sharing, because a pre-selected option tends to be accepted without being read. If nothing is safe, mark the group required instead.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Choose how often we email you. You can change this anytime.
Choose how often we email you. You can change this anytime.
Choose how often we email you. You can change this anytime.
Choose how often we email you. You can change this anytime.
Choose how often we email you. You can change this anytime.
Choose how often we email you. You can change this anytime.