3 ms·
There's an aspect of UX design that is obvious to users and not obvious to programmers: Not all UI elements should have the same visual weight If you have 3 b
by josephg 6y ago
There's an aspect of UX design that is obvious to users and not obvious to programmers:
Not all UI elements should have the same visual weight
If you have 3 buttons, probably one of those buttons will be pressed 80% of the time, and the other buttons pressed less than 10% of the time. How do you style those buttons?
As a programmer, we like to think of the three buttons symmetrically. We want all the buttons to look the same and behave the same, because then they're easier to style and easier to reason about. Our instinct is to make a button class and then place all the buttons next to each other in a nice neat table.
To a user, the three buttons are different, and it should be obvious which one is the button you're expected to press most of the time. From the user's perspective, "Submit form" isn't really the same type of UI element as "reset form". The submit button should be big, bold, colorful and obvious. My eyes should naturally settle on it. The reset form button (if it exists) should be small and non-obvious. Its an advanced feature. It should be out of the way and most people should never notice it.
My email compose window has this problem. It has 3 buttons - "Send", "Save Draft" and "Discard". When I'm writing an email, I'm not choosing between 3 equivalent options. I hit send about 80% of the time I type an email. Once I've written an email, if I visually hunt for the obvious button on the screen, my eyes should naturally settle on "Send". Styling should make that obvious. But no - there are 3 buttons I have to choose from. They're all next to each other, and they're all styled in an identical manner. The interface makes users actively hunt for the "Send" action. This is bad UX.
- antihero 6y agoPretty much every web UI toolkit ever has the concept of primary and secondary buttons.