> 1982: Dragging through a field of check-boxes flips the state of the first and assigns the new state to all other boxes dragged through.
In part it's because I don't like check boxes. They don't have great feedback about what's going to happen. If I designed a UI where someone is likely to check a lot of boxes, I would feel I had done something very wrong.
Sometimes it's unavoidable and so the framework might as well allow it. And as a user, designers often do things I wouldn't have. But I can say I don't miss having that feature.
File choosers usually do something like that, rather than a separate check box component. You select the icon rather than a check box near the icon, so it's slightly clearer what it is you want operated on.
Ideally you'd find other ways to narrow the list. A long list of items is a UX disaster waiting to happen. The more you can categorize your data beforehand, the better off you are. If you can make it all-or-nothing, you're less likely to mis-click.
https://lobste.rs/s/v6mkz6/implementing_one_more_ui_component
The one that drives me crazy is slider based checkboxes. I never know which side is on/off. Bad UI convention.
And speaking of checkboxes, I want an actual tick mark (checkmark), not a X cross. Its called checkbox, not Xbox or crossbox, it has to be a checkmark. Also, its a square, not a box. Disaster.
Those toggles actually mimic real hardware that used to be fairly common. I find those should be preferred over checkboxes for anything that takes immediate effect. If they don't, and you're collecting a bunch of options at once, in a form, then use checkboxes.
For instance, my old stereo has push button toggles, where “in” means “on” (this convention was common because of how those switches work), and three way levers with labels on two of the three positions (there’s no space to label the middle position, and it means “default”.
I can’t imagine how the mechanism would work if each preset knob was a tuning knob.
Some paid services I’ve used for years have started aggressively automatically logging me out while I’m driving (eg when using the CarPlay app, which doesn’t include a login screen).
I really wonder what the PM’s are thinking.
Increase number of app downloads
The checkbox has been a common design element in forms for a long time. But people can of course tick off all boxes.
So when form designers needed to emphasize that you should only select one option, they often used a group of non-boxed options together with instruction copy that read “Circle one” (or similar).
The name “radio button” of course comes from physical buttons, but those were often square. So I think the specific circular shape is actually derived from circling an option on paper.
But also, when you have a dozen monochromatic pixels to work with, 'square' and 'round' are pretty much the only usefully distinct shapes. Checkboxes were square for obvious reasons, so to distinguish a similar set of controls, you pretty much have to use a circle.
I'm pretty sure these concepts moved directly from physical systems to digital ones. Every person alive then knew what an empty square next to a line of text meant, and everyone understood the concept of ganged push-buttons. Just map it onto a pixel grid and you're good to go
https://ux.stackexchange.com/questions/116712/apples-round-checkboxes-where-and-when-are-they-used
(they're not the only offenders in this monstrosity)
Here is a screenshot of what actual checkboxes and radio buttons look like on iOS 26 Beta 2: https://imgur.com/a/TwMRW4X