Image by: Nuno Pinheiro Following posts on specific work being done on Oxygen, this post is going to try to go beyond the manifest work and look at the bigger picture driving it. The motivation for…
Eh? What do radio buttons have to do with anything?
The styling of a UI element - whether it’s a box that gets an X or tick in it, versus a little thingy that moves left and right - is wholly unrelated to any aspects of implementation, including whether the effect happens immediately or not.
I was trying to make the point that the way a control looks gives you some information on how it will behave, because software has generally been consistent with associating those looks with those behaviours.
So if you see multiple options with a circle in front of them, selecting one, then selecting another will usually deselect the first one.
On the other hand, if those options have squares in front of them, selecting one, then selecting another will usually result in both of them being selected.
And in both cases, usually they will be part of a form and will only take effect when you submit that form using a button.
On the other hand, something that looks like a toggle usually takes effect immediately on toggling.
Of course it is technically always possible to have each of those behave like any of the others, but you will be breaking conventions if you do so. Styling is an affordance to inform the user about the behaviour.
Taking effect instantly is not really indicated by the control shape; it’s indicated by whether or not the form has a button equivalent to “apply”. Settings pages with checkboxes that applied immediately have been common for years; this distinction is not nearly as clear cut as you make out. I suspect what is going on is that both toggle switches and the removal of a separate apply step has gone on gradually at the same time.
But a good thing to think about is all the other controls: drop downs, text entry boxes, date pickers - these have no second version which might apply instantly or not! So it’s a mistake to think that information is conveyed by the look of the control.
Eh? What do radio buttons have to do with anything?
The styling of a UI element - whether it’s a box that gets an X or tick in it, versus a little thingy that moves left and right - is wholly unrelated to any aspects of implementation, including whether the effect happens immediately or not.
I was trying to make the point that the way a control looks gives you some information on how it will behave, because software has generally been consistent with associating those looks with those behaviours.
So if you see multiple options with a circle in front of them, selecting one, then selecting another will usually deselect the first one.
On the other hand, if those options have squares in front of them, selecting one, then selecting another will usually result in both of them being selected.
And in both cases, usually they will be part of a form and will only take effect when you submit that form using a button.
On the other hand, something that looks like a toggle usually takes effect immediately on toggling.
Of course it is technically always possible to have each of those behave like any of the others, but you will be breaking conventions if you do so. Styling is an affordance to inform the user about the behaviour.
Taking effect instantly is not really indicated by the control shape; it’s indicated by whether or not the form has a button equivalent to “apply”. Settings pages with checkboxes that applied immediately have been common for years; this distinction is not nearly as clear cut as you make out. I suspect what is going on is that both toggle switches and the removal of a separate apply step has gone on gradually at the same time.
But a good thing to think about is all the other controls: drop downs, text entry boxes, date pickers - these have no second version which might apply instantly or not! So it’s a mistake to think that information is conveyed by the look of the control.