Also an honourable mention goes to touchscreen widgets that look like a left/right slidey switch but are activated by a tap and not a drag.
Also an honourable mention goes to touchscreen widgets that look like a left/right slidey switch but are activated by a tap and not a drag.
In their defense that's how most UI toggles[2] work but they are using a 'phone' metaphor and it's implemented backwards from how you would usually expect a phone call UI to work.
[0] https://www.jetbrains.com/help/img/idea/2019.2/php.icons.deb...
[1] https://www.jetbrains.com/help/img/idea/2019.2/php.icons.deb...
[2] https://www.jqueryscript.net/images/jQuery-Plugin-For-Slidin...
This comment being right next to this one shows the joy of designing UIs:
> I never understood why one would make a control show the state that it isn't in.
UI is hard indeed.
It's blue when on, gray when off. The tooltip describes the completely opposite state to the one that's currently active.
The icon is the same in both state, the color means nothing (since when the blue means on?), tooltip is wrong. Bah.
Wait, that's a bad thing? I can only imagine how pissed off I'd be when using an interface that insisted on me using my mouse to click and drag a switch to turn it "on" or "off" instead of, you know, just clicking. I don't even do the left/right swipe thing on mobile, either; way more convenient to just tap instead of drag.
It is an attempt at communicating state and action at the some time, but I think disconnecting look and behavior is a mistake. Don't use a skeuomorphic slider to represent a push button switch, especially if selling the realism of a touch interface is the goal.
I guess it goes back to my other post about "intuitive" not actually being a real thing, and the actual factor being "what you're used to".