Hot answers tagged

22

Color alone should not be used as an indication of meaning, as Shreyas Tripathy points out. However, there is benefit to having a separate color for actions that change the state of your data, such as save actions, like in your example. In my applications, I tend to implement the following , which is also suggested by common style frameworks as Bootstrap: ...


7

Having too many variations in buttons is a bad idea. What you mentioned is absolutely the best approach i.e. I personally would keep just one style for primary buttons and one for secondary (the gray outlined and the blue one). This is good not just because it eliminates visual clutter, but also because it works without colours. We tend to forget that a ...


5

I have this exact situation in my current role. This is how I'm approaching the problem. Establish a relative hierarchy of the button styles. E.g. Primary, Secondary, Tertiary and as others have said, ensure these are visually distinct in ways other than colour. Ensure this hierarchy is applied properly throughout the app. This can be a problem with legacy ...


1

I just noticed you're also looking for some help, so I figured I'd take a Stab at it :) As a general note: I think we have a relatively "low impact" issue on our hands here, meaning neither approach is likely to pose a major hurdle to the user. However, these type of details do add up, so your question is entirely valid! For starters, you'd ...


1

Be consistent across all screens. Consistency is a key design principle and you can help the users by not forcing them to learn new things in each task or screen.Try with users, choose the best one for them and be consistent with that. good article about consistency https://www.interaction-design.org/literature/article/principle-of-consistency-and-standards-...


Only top voted, non community-wiki answers of a minimum length are eligible