I can’t find it but one of my favourite designs was a switch with a “light” beside it that lit up when the state was “on.” The best thing was that it also solved the latency of an async operation. You’d click the switch which toggled, and then some moment later the light came on. It felt incredibly satisfying and gave confidence that yes, this interaction has done something.
Should toggle button show its current state or the state to which it'll change? (2010)
31–40 of 303 posts
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#32Re: Should toggle button show its current state or the state to which it'll change? (2010)
#33Earlier quoted context omitted.
> I can’t find it but one of my favourite designs was a switch with a “light” beside it that lit up when the state was “on.” So when I revisit that page after a long time and see that the light is lit, does it mean that the state is currently ON or does it mean that the state will change to ON when I click it? How can I tell this by instantly looking at the lit light?
On is active. Just like most devices with signal lights — which have been that way for decades. Historically, the lights are signaling power being supplied.
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#34Earlier quoted context omitted.
If the light is beside the switch (rather than being the switch) then I'd say it clearly and unambiguously indicates the current state of whatever the switch operates? (A light also has the advantage of being a skeuomorph - much as those are now out of fashion - we all know how to interpret indicator lights in the real world.)
> A light also has the advantage of being a skeuomorph Unless you’re my TV and it’s completely backwards for some reason.
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#35Using words often works. But let me chime in with some outrage about the icons on an Android tablet - a triangle, circle and square with no discoverability and no ability to add text to icons on the home screen? WTF?
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#36In defense of the ambiguity of digital toggles, I’d like to add that this is unsolved on most, if not all, physical light switches in homes and offices. Despite having existed for more than 50 years and most people are using multiple toggles a day with its labels, most people are unaware of the meaning of power symbol ( https://en.m.wikipedia.org/wiki/Power_symbol )
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#37A push button toggle stays clicked in, or better yet clicked in and illuminated, to indicate that it's on.
a traditional 2 way toggle exposes the state that its' in by the position of the knob relative to center.
I mean anyone can flip states around behind the scenes, but if we're talking about a switch/wires/battery/light it all works out as supposed. Let's follow that example.
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#38A toggle button should show its current state. A checkbox is a good example. Muted [] vs Muted [x] It's pretty obvious. What gets tricky is when designers create UI that does not have as clear a connection between the word used and the visual design, such as: Mute Off [---( )] Mute On [( )---] I have no idea what either of these mean because they include the action in the description of the state.
I want a button to tell me what it does if I click it. If you want to show the current status that is a different thing, not a button. A button exists to be clicked, it should communicate what it will do if you click it.
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#39Using words often works. But let me chime in with some outrage about the icons on an Android tablet - a triangle, circle and square with no discoverability and no ability to add text to icons on the home screen? WTF?