Live data from Hacker News

Should toggle button show its current state or the state to which it'll change? (2010)

ux.stackexchange.com

31–40 of 303 posts

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#31

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.

That sounds like an interface feature found on "smart" devices - I'm only familiar with TP-Link Kasa switches, but I think I remember their app UI having a similar feature where a color icon had multiple states, the most "on" of which is "confirmed with the switch it turned on".

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#32

Earlier quoted context omitted.

Really? For me this always made intuitive sense reading it as one and zero, where zero would be off.

It always seemed backwards to me, since a circle should represent a closed circuit

An open circuit would then be a C not a |

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#33

Earlier 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.

It's also quite common to have a light indicator that goes away when the device is turned on. TVs often do this - they have an indicator LED to show that they are plugged in, but turn that LED off when the screen is turned on, because it can be distracted, and is anyway no longer needed.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#34

Earlier 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.

The standby light on a TV in on for standby and off when viewing because a) it could be distracting and annoying for the extra LED to be shining while viewing in a darkened room, and b) the "on" state should be pretty obvious because of the stuff on the screen.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#35
post #15

Using 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?

It takes 1 day to learn, to avoid years of extra clutter on the screen. But an option or a long press tooltip would be nice for special cases.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#36

In 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 )

People are aware.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#37
I just want it to mimic the physical thing if it's going to mimic something at all.

A 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)

#38
post #28

A 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.

"Mute" "Unmute"

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)

#39
post #15

Using 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?

Sometimes called “Mystery meat navigation”.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#40

Earlier quoted context omitted.

Really? For me this always made intuitive sense reading it as one and zero, where zero would be off.

You probably also work in IT and might even now what binary is not to mention what boolean means.

fair point
Post reply on HN