"Because it's often better to use radio buttons. But students often say "But it'll make the page too long". Yep, but that doesn't necessarily mean it's bad UX. See the page I designed to let users select a course. Huge list of radio buttons. But no issues in user research whatsoever. Does this mean you should always use radio buttons? No. But most designers would balk at a design like this even though it worked perfectly well for users."
"I've worked with quite a few product managers and designers who suggest testing multiple versions. It sounds sensible, right? But more work does not always mean a better result. Here's why (according to UX expert, Caroline Jarrett who wrote about it in "Designing comparative evaluations"): Reason #1: You won't get a clear answer You're hoping for \"Version A wins!\" but what you'll actually get is: Parts of A are better, parts of B are better, and there's probably a Version C that would beat them"
Radio buttons can be preferable to select boxes for presenting options. Long pages with many radio buttons can still produce good usability and show no issues in user research. A common testing approach is to consider many options but test one solution at a time, switching only if the tested solution fails. Comparative testing of multiple versions introduces pitfalls: it often fails to deliver a single clear winner, participants can learn and contaminate results if exposed to multiple versions, and comparative tests typically require about three times as many participants and careful balancing.
Read at Adamsilver.io
Unable to calculate read time
Collection
[
|
...
]