Programming

17343 readers

430 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Should a toggle button show its current state or the state to which it will change? (ux.stackexchange.com)

submitted 8 months ago by starman@programming.dev to c/programming@programming.dev

49 comments fedilink hide all child comments

cross-posted from: https://programming.dev/post/9907892

you are viewing a single comment's thread
view the rest of the comments

[–] abhibeckert@lemmy.world 5 points 8 months ago* (last edited 8 months ago)

I disagree. I think both the current state and the state it will change to should be clearly labeled.

Also - just because everyone is familiar with something doesn't make it a good user experience. We're used to play/pause but it's honestly not very good.