4 ms·

Mostly good, except the button examples at the end. It is completely backwards to recommend buttons that don’t even look like buttons and then add gray text to

Mostly good, except the button examples at the end. It is completely backwards to recommend buttons that don’t even look like buttons and then add gray text to make them look even less available!! A list of buttons is just fine.

albedoa 9y ago
No, you want the primary action to look clearly like a button and the others to look like secondary links to minimize cognitive load. A list of button-like shapes that do wildly different things is not good UX.
- makecheck 9y ago
  There is a lot more "cognitive load" when I wonder why something that I need is apparently disabled, or when I can't even find an option because it is being presented in a way that doesn't remotely resemble something that should trigger an action. Consistency counts too. If a button is "dangerous", it can be dealt with in other ways, such as: - More space from other buttons - An ellipsis "..." to indicate to the user that a confirmation will appear (making it more "safe" to experiment with the button) - Adding an icon and/or color
  - albedoa 9y ago
    > I wonder why something that I need is apparently disabled That is also bad. It's not a choice between two bad things. > I can't even find an option because it is being presented in a way that doesn't remotely resemble something that should trigger an action. Then we should not do that either! One solution is obvious links, which are known to trigger events, for secondary and/or tertiary actions. The list of buttons in the examples is not good. - More space doesn't address the problem (and after some amount of space it stops being a single "list of buttons" as opposed to multiple buttons strewn across the interface). - An ellipsis does signal a confirmation, but that is not the problem being addressed. - The buttons already have different colors in the "before" images. That is how the problem is presented.

albedoa 9y ago

No, you want the primary action to look clearly like a button and the others to look like secondary links to minimize cognitive load. A list of button-like shapes that do wildly different things is not good UX.

makecheck 9y ago
There is a lot more "cognitive load" when I wonder why something that I need is apparently disabled, or when I can't even find an option because it is being presented in a way that doesn't remotely resemble something that should trigger an action. Consistency counts too. If a button is "dangerous", it can be dealt with in other ways, such as: - More space from other buttons - An ellipsis "..." to indicate to the user that a confirmation will appear (making it more "safe" to experiment with the button) - Adding an icon and/or color
- albedoa 9y ago
  > I wonder why something that I need is apparently disabled That is also bad. It's not a choice between two bad things. > I can't even find an option because it is being presented in a way that doesn't remotely resemble something that should trigger an action. Then we should not do that either! One solution is obvious links, which are known to trigger events, for secondary and/or tertiary actions. The list of buttons in the examples is not good. - More space doesn't address the problem (and after some amount of space it stops being a single "list of buttons" as opposed to multiple buttons strewn across the interface). - An ellipsis does signal a confirmation, but that is not the problem being addressed. - The buttons already have different colors in the "before" images. That is how the problem is presented.