Radio button vs. toggle switch (on multiple binaries page) #2644
-
|
Hi, We're updating a settings page for Authy that has 11 binary settings. (see "current" section in the screenshot) Using Y/N radio buttons, the page gets pretty long with many floating yes/no radios. Is it possible to use a single toggle switch instead? What do you recommend?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
This type of use case seems totally reasonable for a switch! The only thing I'd caution against is that the use of Switches is usually in conjunction with instant on / off configuration and persistence. Think about how switches work on a phone in settings. There's no "save" action, they are just "on" or "off". So if the API you're working with doesn't support asynchronous saving per field, and you have to rely on a save button for the entire form, then you might create an unfamiliar interaction for the user. In that instance, you would be better off using Radio's, even if they do create longer pages, because it's a much more familiar interaction pattern. Hope that helps! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much Simon, this is super helpful! |
Beta Was this translation helpful? Give feedback.
Hi @cgolankotter
This type of use case seems totally reasonable for a switch!
The only thing I'd caution against is that the use of Switches is usually in conjunction with instant on / off configuration and persistence. Think about how switches work on a phone in settings. There's no "save" action, they are just "on" or "off".
So if the API you're working with doesn't support asynchronous saving per field, and you have to rely on a save button for the entire form, then you might create an unfamiliar interaction for the user. In that instance, you would be better off using Radio's, even if they do create longer pages, because it's a much more familiar interaction pattern.
Hope that helps!