DEV Community

Discussion on: Should a button communicate the current state, the intended behavior, or both?

Collapse
 
peledzohar profile image
Zohar Peled • Edited

You are confusing two closely related UX elements - A button and a toggle button.

A button doesn't have a state.

It merely provides a way to perform an action - just like a link, or the physical buttons on your mouse - It's there to be clicked and therefor should convey the action it will perform - Just like the "WRITE A POST" button on the top right corner of this page (BTW, I'm not a native English speaker, but shouldn't that be "Write a post"?)

A toggle button, on the other hand, is a different kind of button. It's like the on/off switch and has two distinct modes - but in my humble opinion - it should still convey the action rather then the state.

Let's look at the follow toggle button: Its state is either "following" or "not following" - and I imagine everyone can understand what happens when you click a button entitled "Follow" or "Unfollow", much more intuitive than "following" and "not following" (What the hell should "not following" mean on a button, anyway?)

Conclusion:

In my opinion - If you want to convey state, neither a button nor a toggle button is the way to do it - they should both convey action.

current state should be conveyed by other UX elements - texts, checkboxes and radioboxes comes in mind.