You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a small UX/UI request. It would be nice if boolean controls could be visually improved.
Here is their current appearance:
It's blurred to point out the issue.
Describe the solution you'd like
There are a few UX points here:
Visual weight — one side of the control is darker, i.e. "heavier".
Toggle position — is it to the left or to the right?
Direction — which side is "on": left or right?
For 1, it seems that the visual weight should be on the "switch" part of the toggle, not the "track". Visual weight draws attention, and by 2 we see that the main question is which side the toggle switch is on.
3 is more subjective, but I feel like in a LTR culture, the "on" position should be on the right. If you're holding a physical object with physical switches, the rightward position would be outward, and with real protruding switches, this is an "open" state (think of the petals of a flower that has bloomed). This is an "enabled" or "active" state.
Describe alternatives you've considered
N/A
Are you able to assist to bring the feature to reality?
It depends
This is a small UX/UI request. It would be nice if boolean controls could be visually improved.
Here is their current appearance:
It's blurred to point out the issue.
Describe the solution you'd like
There are a few UX points here:
For 1, it seems that the visual weight should be on the "switch" part of the toggle, not the "track". Visual weight draws attention, and by 2 we see that the main question is which side the toggle switch is on.
3 is more subjective, but I feel like in a LTR culture, the "on" position should be on the right. If you're holding a physical object with physical switches, the rightward position would be outward, and with real protruding switches, this is an "open" state (think of the petals of a flower that has bloomed). This is an "enabled" or "active" state.
Describe alternatives you've considered
N/A
Are you able to assist to bring the feature to reality?
It depends
Additional context
Some light UX nerd-sniping:
The text was updated successfully, but these errors were encountered: