Earlier quoted context omitted.
... just the one adjective?
I don't follow - what do you think is missing?
Something other than muted; both your options are the same.
Should toggle button show its current state or the state to which it'll change? (2010)
261–270 of 303 posts
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#262I once worked on an Optical Image Stabilisation system for mobile phones. I'd updated the stock Android camera app to show some icons from marketing for when the shake compensation was on / off. The icon for when compensation was on was a shaky camera. When it was off, it was a shaky camera with a line through it... Except, we asked, wouldn't the other way round make more sense? Doesn't line through shaky camera sugg…
This is why this kind of thing should have text (with or without an icon). Just tell me what you're trying to communicate. Yeah I know you have to translate it for other languages, but Microsoft, Samsung, et cetera should be able to afford that.
I hate that Windows 11 has regressed on this.
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#263I don't know how developers manage to make simple toggle switches confusing and it makes me scared of their code but sometimes I think it's done on purpose as a dark pattern (when you unsubscribe to spam for example)
Unsubscribe....lol
Inbox rule: body:"unsubscribe" -> move to Delete.
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#264Earlier quoted context omitted.
The interfaces you are talking about require years of training, study and passing multiple tests to demonstrate proficiency. In software UX we are talking about discoverability and approachability for the untrained operator.
Most of the training is to know which ones need to be on and which ones need to be off. Not how to read various buttons as on or off. And the point there is they are able to rapidly scan a dashboard to know what is on and off at a glance. Similarly, sliders and levers help you see which ones are maxed out and which ones are set at a rough 50% or similar.
> Not how to read various buttons as on or off.
That may not be explicitly trained, but it's heavily trained becasue they must get that right to pass the tests. If they misunderstand at first, they won't for long. Also, the user is highly motivated - they don't want to crash the plane.
Consumers are often looking at UIs for the first time, and are highly motivated to go back to their feed and see what they missed.
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#265The absolute worst example of this I have seen is the Tesla dashboard screen UI. It shows a car with labels on it, not buttons, that say "Open". That unambiguously means that the particular part is open. But that's not what it means. The labels are in fact buttons to open the parts, and you have no way of knowing.
I hate that damn "open" thing. The first time I saw it I thought I had left my boot open.
All it needs is "Closed - tap to open"
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#266I agree with the conclusion, but would like to add that it should be obvious what the current state is, and what the state will change to when the toggle is changed; too often I have to change it in order to work out that I didn't need to change it. The point about play/pause is really interesting because it goes against the conclusion. However, it's following physical precedent that's well understood. It's also (usu…
> Give me labels. If labels don't fit your motif then get better designers. That's unhelpful and unreasonable, particularly on mobile. There's no room on Spotify for labels behind every button, for instance. Not if you want room to show the cover art, which I do. It's not a question about "better designers" -- space constraints are real, and sometimes you really need things available at a single tap. I don't want shu…
There is plenty of room on Spotify for labels on every button. Plenty.
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#267Why not just use a checkbox? Is anyone here a designer with a serious answer to this?
No such thing as a "designer." They are less credentialed than a "software engineer."
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#268We should use the world's national emergency alert systems to conduct a poll of as large a percentage of the world population as possible, and whichever option wins the poll, we should go with that one.
Of course, no one will agree about which state is which,...
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#269There doesn't need to be an either/or if you give the toggle twice the space, just like a physical toggle. With the added space, you can show the states are related, which state is currently selected, and which alternate state will become current after the change. The real problem seems to be nobody cares about actual ui-design for human use but something that'll look good when you show the boss.
Re: Should toggle button show its current state or the state to which it'll change? (2010)
#270Earlier quoted context omitted.
I don't follow - what do you think is missing?
Something other than muted; both your options are the same.
I see! Those were two 'screenshots' of the same setting, one in selected state and one in unselected state, following the example of a post upthread. They were not two different settings - yes, that would probably be poor UI design! I've seen worse.