Interaction Engineering · 6 / 10

Did You Pick the Right Control: Radio, Checkbox, Toggle & Dropdown

The first four lessons covered flow and states. This one drills into the smallest UI parts. Controls are the shared language between user and product — pick wrong, and users click once more and guess once more. Selection rules fit in four sentences. AI doesn't know them; you gatekeep.

Four rulesScene match-upDropdown costShould it pop?
When AI picks controls, it rolls dice

Ask AI for a form and controls are usually grabbed at random: three options stuffed into a dropdown, radio vs checkbox by mood, plus a popup for every action. Each flaw alone is small — stacked in one form, users pay extra effort every step.

Typical bugOn the sceneExtra cost users pay
Three options still in a dropdownOnly three invoice types, buried under "Please select"One extra click before options appear; can't compare side by side
Radio vs checkbox by chanceMutually exclusive options get checkboxes; multi-select gets radiosContradictory data, or can't multi-select — users hit the wall once
Everything pops a dialogSave success pops one; switching tabs pops anotherEvery dialog is an interrupt — hands on page, mind yanked away

Cooper walks these parts one by one in About Face 4 Chapter 21 — rules clear enough to memorize. This lesson: memorize the rules, drill with match-ups, then paste the rules into a prompt.

Four rules: each control to its home

Chapter 21 draws a sharp line among choice controls. Radio buttons take their name from old car radios: press one station key and the previous pops up — eyes stay on the road. Mutually exclusive, must pick one: that's their turf. Four rules map to four controls — face first, then rules.

VAT special VAT general E-invoice
Mutually exclusive pick-one → radio button
Pick one and the others spring up — wrong combinations are physically impossible. Only meaningful in a group; a lone radio can't uncheck, and Chapter 21 calls that meaningless.
Product updates Events Weekly digest
Multi-select → checkbox
Check to mark, tap again to clear — several side by side allow multi-select. Square is the face it earned over decades; don't round it or it collides with radios.
Dark mode Sound
Instant effect → toggle
Flip it and it changes now — no Save. Chapter 21 says it's great on mobile settings; conversely, don't use toggles for options that submit with a form — users will think it already took effect.
Guangdong 34 options tucked inside
Overflow one screen → then consider dropdown
A dropdown's initial state shows only the current pick — everything else is hidden. One glance at options costs a click. It's a compromise when the screen can't hold them; don't waste the quota on three options.
"Links for navigation, buttons for action."
Alan Cooper, About Face 4 Chapter 21: every control has a job — make one do another's work and users relearn.
Hands-on · Six scenes, seat each control

Rules memorized — now feel them. Six scenes from real forms: pick the best of four controls for each. Wrong picks get corrections; keep going until right.

Match scenes to controls 0 / 6
Tap a control chip under each scene. Six correct = the rules are in your hands
1Expense form: pick invoice type — VAT special / general / e-invoice; only one
Right. Three options, mutually exclusive, must pick one — radios laid flat let you compare invoice types at a glance. AI will usually hand you a dropdown and hide three options behind two clicks.
Checkboxes allow multi-select. Check special and general together and finance alarms instantly. Mutually exclusive scenes need one pick to displace another.
A toggle only holds on/off. Three invoice types don't fit two states — toggles handle instant-effect settings.
Only three options and already a dropdown — hid too early. Chapter 21's bar: options overflow one screen before it earns a turn.
2Subscription: "which emails do you want" — product updates, event notices, weekly picks; check freely
Radios are mutually exclusive. Pick Events and Product updates drops — users who want both are stuck. Coexisting options belong to checkboxes.
Right. Three independent, coexisting options — checkboxes one-by-one fit. Chapter 21 also has an advanced use: markers — a checkbox per list row so multi-select state is visible at a glance.
Close. Three toggles could limp along, but these choices submit with Save. A toggle promises instant effect on flip — semantics don't match.
A dropdown shows one item at a time. To see what you checked, open and count — multi-select state stays hidden.
3Settings "Dark mode" — change and the UI recolors now, no Save
Two radios for On/Off double the footprint. A toggle is two compressed radios — binary and instant effect; use the toggle.
Checkboxes grew up in forms — users instinctively hunt for Save. Instant-effect settings use toggles; the "it took" feeling is designed.
Right. Flip and it recolors now — the toggle's shape itself promises instant effect. Chapter 21 names it best for settings pages; when AI generates settings, give it that word.
Two options as a dropdown — users click twice to switch once, and can't see what the other option is.
4Shipping address: pick province — 34 options
34 radios laid flat turn the form into a wall. Radios eat screen; Chapter 21 says they fit few, infrequently used options.
Province is pick-one — checkboxes fail semantically first; 34 of them is a disaster.
A toggle can't hold 34 states. It only has on and off.
Right. Options overflow one screen — now the dropdown earns its keep; hiding saves the screen. Fancier still: typeahead, two characters to land.
5Checkout: pick payment — WeChat Pay, Alipay, UnionPay; pay with one
Right. Mutually exclusive, must pick one, only three — flat radios let users glance and tap. Real checkouts use three big cards: a radio variant, same rule.
One payment can't take two rails — checkbox multi-select semantics are a trap here.
Three payment methods don't fit one toggle. It only has two states.
Payment is the last place to add friction — three options in a dropdown put an extra door before checkout.
6Signup: "I've read and agree to the terms" — must check to register
A lone radio is meaningless — once on, you can't clear it. Chapter 21's near-verbatim conclusion. Binary non-exclusive marks belong to checkboxes.
Right. Check to agree, tap again to undo — a single checkbox covers check/unchecked. That's the use it was invented for.
Toggles take effect immediately — but agreeing to terms submits with signup. A toggle makes users think flipping equals signing.
Agree / Disagree as a dropdown — users must open to see options: two steps bolted onto one.
Dropdown accounting: every look at options costs a click

Among four controls, dropdown is the one AI abuses most — worth its own ledger. Chapter 21 on list controls names the birth defect: initial state shows only the last pick; other options stay invisible. Invisible options mean no comparison and no estimate of how long this step takes. Same food-delivery checkout below — tap the one you'd use.

Pick delivery time: dropdown vs flat A/B duel
Tap a card to vote; verdict after you pick
Plan A
waimai.example.com/checkout
Confirm orderTotal ¥ 42.5
Delivery time
Please select delivery time
Place order
Three slots buried in a dropdown — none visible until open
Plan B
waimai.example.com/checkout
Confirm orderTotal ¥ 42.5
Delivery time
Send now~35 min
Around 18:00 todaySkip lunch rush
Around 19:00 todayReceive after you're home
Place order
Three slots laid flat, each with a note, default on the most common

The flat plan quietly uses one more move: "Send now" as default. Visible options plus a sensible default — most users clear this step in a second. That's last chapter's error-prevention trio "default as safety net" at the control layer.

Dialogs interrupt — skip them when you can

Chapter 21 situates dialogs with a kitchen metaphor: the app is the kitchen, the dialog is the pantry — it advances the plot but can't star. Primary interaction stays in the main window; dialogs hold what's outside the main flow: dangerous, rare, or needing one topic gathered in one place. An easy-to-miss detail: functional dialog titles use verbs so users see what they're confirming at a glance.

AI's habit is the opposite: success pops, tips pop, confirms pop. Five scenes below — judge one by one whether it should pop.

Should the dialog pop? Five in a row 0 / 5
For each scene tap "Should pop" or "Shouldn't" — the verdict explains why
User taps "Empty trash" — 200 records gone for good; product can't undo yet
Should pop — but it's a spare tire. Irreversible and undo isn't ready; the confirm dialog is the last line. Title with a verb: "Empty these 200 records?" Lesson 3 said: prefer reversible when you can; dialogs only cover when undo is absent.
Every successful save pops a "Saved successfully" dialog for the user to tap OK
Shouldn't. Finishing normal work and asking for a praise click is the software fishing for credit. Success feedback = non-modal light cues: a corner checkmark, a two-second toast — peripheral vision is enough.
One form field still empty; user taps submit; a dialog says "Information incomplete"
Shouldn't. Lesson 3 staged this: error prevention goes first — disable submit while incomplete and say what's missing. Let users hit the wall then hand a dialog bandage, and you've turned prevention into error reporting.
User taps "Export all data" — must pick format, range, and whether to include attachments in one go
Should pop. Export sits outside the main flow, is rare, and needs several settings for one topic in one place — exactly Chapter 21's job for dialogs: gather related info so users don't hunt the whole UI.
User is typing; background sync finishes; a dialog says "Sync complete"
Shouldn't. Hands on the keyboard — a dialog steals focus and half a sentence lands in the OK button. Background status updates quietly via a corner icon or status bar. Cooper calls that rich visual non-modal feedback; Chapter 15 is how it kills dialogs.
Cheat sheet · Paste into the prompt so AI stops rolling dice

Rules in your head don't help — write them into the brief for AI. First a cheat sheet, then one-click copy the constraint line below; paste it at the end of any form-UI prompt.

ControlWhen to useAI's common misuse
Radio buttonMutually exclusive, must pick one, options fit one screenGives dropdown or checkbox where radio belongs
CheckboxMulti-select, or a single check/unchecked markGives checkbox to mutually exclusive options → contradictory data
ToggleBinary settings that take effect immediatelyUsed on fields that submit with a form
DropdownOptions overflow one screen — compromise when space runs outHides three–five options too, adding a free click
DialogOutside main flow: dangerous, rare, gather one topicSuccess tips and routine confirms also pop — everything pops
Control constraints — straight into the prompt Copyable
Tap copy top-right; paste at the end of your UI-generation prompt
Constraint line
Control selection constraints: when mutually exclusive and ≤5 options, lay out radio buttons — no dropdown; multi-select uses checkboxes; toggles only for instant-effect settings; dropdown only when options overflow one screen, with typeahead. Dialogs only for outside-main-flow work (dangerous ops, rare settings, gathering one topic); functional dialog titles use verbs; success uses non-modal toast — no "success" dialogs; validate forms up front (disable + missing-field notes) — no post-submit "incomplete" dialogs.
Bonus · The case of the merged button

Chapter 21 also names a control to avoid: the state-toggle button. The music player's merged Play/Pause is the poster child — triangle showing, you tap, music starts, icon becomes two bars. Where does Cooper say the bug sits?

Merged Play/Pause — what's the root bug? Single choice
Wrong answers still get explanations — keep going until you hit right
ATwo functions crammed into one button — hit target too small, easy mis-taps
BUsers can't tell if the icon shows current state or what will happen on tap
CIcon without text — beginners can't learn it
DSwitch is too fast — animation can't finish
Key Takeaways

Four rules: mutually exclusive pick-one → radio; multi-select → checkbox; instant effect → toggle; overflow one screen → then dropdown (Cooper, About Face 4 Chapter 21).

Dropdown is a compromise: it starts showing one item; looking costs a click. Three–five options: lay flat first with a sensible default — most users clear in a second.

Dialogs interrupt: primary interaction in the main window; popups only hold outside-flow danger, rarity, or gathered topics; success uses non-modal light feedback; functional dialog titles use verbs.

Write the rules for AI: paste the cheat-sheet constraints into the prompt and controls stop relying on dice rolls. Controls speaking right isn't enough — copy must speak human too. Next lesson: how the UI talks.

Source: Original to Xiaoshan Academy's Interaction Engineering series; some interaction principles adapted from About Face 4: The Essentials of Interaction Design.