Tag Info

Hot answers tagged

5

The only application I know which puts an additional button there is Display Fusion (a software to improve the experience with multi-monitor setups). That extra button moves the window to the other monitor: In this case I would say this is appropriate since the associated action controls the window in a similar manner as the other buttons and I'm using ...


2

There is a research that shows that designers are over-concerned with consistency. While consistency means that users don't have to relearn things (by that increasing usability), consistency for the sake of it isn't exactly what UX is about - weighing all variables involved. Consistency is not everything. In the case of buttons, the consistency argument ...


2

Her argument isn't necessarily bad, if your modals are properly displaying a name/function the ok/cancel combo will just fine for a cta compared to named buttons. Instead of trying to find studies to win an argument try and ask your product manager why she thinks to use ok and cancel. Providing a consistent functionality throughout a system is also ...


2

How about a single toggle between EDIT and DONE ? http://codepen.io/run-time/pen/yyJMKQ Hopefully you will be able to inform the user when changing their data soon. For future reference, I like how Google doesn't make the user explicitly commit changes and instead offers an easy way to go back...


1

Mute button at the bottom as this is going to be used less than your standard volume controls, and should also follow a logical flow: Volume up -> Volume down -> Mute. If this is in the middle a user could accidentally press mute which would be annoying. A mute button should follow conventional design so a speaker crossed out would be fine. Check out the ...


1

Consistency is one goal, but it isn't the only goal. It may not be the most important one in this context. (See also: 'Foolish consistency is the hobgoblin of little minds.') The relevant UX principle is: things that look the same should work the same; things that work differently should look different. "OK" is consistent, but it may produce different ...


1

I think there are three big rules that must be taken in to account when identifying the best view/edit paradigm: I want the information to be easy to read (Summary/Print view without edit clutter) I want to prevent unwanted mistakes on important data I want to quickly and easily edit the information The UX solution for View/Edit may be different ...



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