6 ms·

Checkboxes come from older mouse/cursor UI’s, toggles come from newer touchscreen UI’s.

mikeyla85 4y ago
Checkboxes are just as usable as toggles on touchscreen. It doesn't have to do with the tech, it's just that toggles are newer.
- kevin_thibedeau 4y ago
  Checkboxes are slightly problematic in touch UIs because they are generally scaled to a similar size as text and small enough that they are occluded by a fingertip. Sliders leak information about their state while you touch them.
- scyzoryk_xyz 4y ago
  I wouldn’t dare make comments on what’s more or less usable in an HN thread since everyone here is such an expert on these things. Toggles came along with iOS when the UI was skeumorphic ca. 2008. Don’t know whether it has to do with tech, but that’s when we first got those. As far as actual evidence, I do UX testing of a touchscreen/cursor application and we have both scattered throughout. I haven’t ever seen anyone have any difficulty understanding, using or differentiating between either. In our results this simply isn’t a problem with investigating.
  - barneygale 4y ago
    > I haven’t ever seen anyone have any difficulty understanding, using or differentiating between either. In our results this simply isn’t a problem with investigating. I'm not sure if this was meant as reassuring, but for me it only reinforces my view that UI/UX folks don't have a clue what they're doing.
- boomboomsubban 4y ago
  Checkboxes can be just as usable but they're often smaller and often more tightly spaced, which can be a pain to navigate on a touchscreen. I'm not saying that's a good reason, but it is a reason besides being newer.
flohofwoe 4y ago
Then why has macOS Ventura toggles all over the place, even though it's pointer-driven? (it's actually a wild mix of toggles and checkboxes in the new Settings UI) There seems to be some logic behind it though: Toggles are often used alone to switch things on/off (for instance Wifi or Bluetooth), while checkboxes are often used in groups for "less important things". But maybe I'm just imagining that there's an actual reason behind it ;)
- mpweiher 4y ago
  Because we have to phone-ify everything, whether it makes sense or not. (Narrator: it never does)
- mathieuh 4y ago
  From https://developer.apple.com/design/human-interface-guidelines/components/selection-and-input/toggles https://developer.apple.com/design/human-interface-guideline... Switches -------- Avoid using a switch to control a single detail or a minor setting. A switch has more visual weight than a checkbox, so it looks better when it controls more functionality than a checkbox typically does. For example, you might use a switch to let people turn on or off a group of settings, instead of just one setting. In general, don't replace a checkbox with a switch. If you're already using a checkbox in your interface, it's probably best to keep using it. Checkboxes ---------- A checkbox is a small square button that’s empty when the button is off, contains a checkmark when the button is on, and can contain a dash when the button’s state is mixed. Unless a checkbox appears in a checklist, a descriptive label follows the button. Use a checkbox instead of a switch if you need to present a hierarchy of settings. The visual style of checkboxes helps them align well and communicate grouping. By using alignment — generally along the leading edge of the checkboxes — and indentation, you can show dependencies, such as when the state of a checkbox governs the state of subordinate checkboxes.
  - saagarjha 4y ago
    > In general, don't replace a checkbox with a switch. Someone tell Apple's Settings team

Checkboxes are just as usable as toggles on touchscreen. It doesn't have to do with the tech, it's just that toggles are newer.

kevin_thibedeau 4y ago
Checkboxes are slightly problematic in touch UIs because they are generally scaled to a similar size as text and small enough that they are occluded by a fingertip. Sliders leak information about their state while you touch them.
scyzoryk_xyz 4y ago
I wouldn’t dare make comments on what’s more or less usable in an HN thread since everyone here is such an expert on these things. Toggles came along with iOS when the UI was skeumorphic ca. 2008. Don’t know whether it has to do with tech, but that’s when we first got those. As far as actual evidence, I do UX testing of a touchscreen/cursor application and we have both scattered throughout. I haven’t ever seen anyone have any difficulty understanding, using or differentiating between either. In our results this simply isn’t a problem with investigating.
- barneygale 4y ago
  > I haven’t ever seen anyone have any difficulty understanding, using or differentiating between either. In our results this simply isn’t a problem with investigating. I'm not sure if this was meant as reassuring, but for me it only reinforces my view that UI/UX folks don't have a clue what they're doing.
boomboomsubban 4y ago
Checkboxes can be just as usable but they're often smaller and often more tightly spaced, which can be a pain to navigate on a touchscreen. I'm not saying that's a good reason, but it is a reason besides being newer.

flohofwoe 4y ago

Then why has macOS Ventura toggles all over the place, even though it's pointer-driven? (it's actually a wild mix of toggles and checkboxes in the new Settings UI) There seems to be some logic behind it though: Toggles are often used alone to switch things on/off (for instance Wifi or Bluetooth), while checkboxes are often used in groups for "less important things". But maybe I'm just imagining that there's an actual reason behind it ;)

mpweiher 4y ago
Because we have to phone-ify everything, whether it makes sense or not. (Narrator: it never does)
mathieuh 4y ago
From https://developer.apple.com/design/human-interface-guidelines/components/selection-and-input/toggles https://developer.apple.com/design/human-interface-guideline... Switches -------- Avoid using a switch to control a single detail or a minor setting. A switch has more visual weight than a checkbox, so it looks better when it controls more functionality than a checkbox typically does. For example, you might use a switch to let people turn on or off a group of settings, instead of just one setting. In general, don't replace a checkbox with a switch. If you're already using a checkbox in your interface, it's probably best to keep using it. Checkboxes ---------- A checkbox is a small square button that’s empty when the button is off, contains a checkmark when the button is on, and can contain a dash when the button’s state is mixed. Unless a checkbox appears in a checklist, a descriptive label follows the button. Use a checkbox instead of a switch if you need to present a hierarchy of settings. The visual style of checkboxes helps them align well and communicate grouping. By using alignment — generally along the leading edge of the checkboxes — and indentation, you can show dependencies, such as when the state of a checkbox governs the state of subordinate checkboxes.
- saagarjha 4y ago
  > In general, don't replace a checkbox with a switch. Someone tell Apple's Settings team