Tag Archives: user interface

#32 Don’t Disable UI Elements

The concept of “disabling” a user interface element seems like a good idea to let users know that a particular action is not available. The problem is that most implementations made a disabled element completely dead and unreactive.  This is a problem for any user learning to use the program.  The dead element gives no indication of why it is dead.  There is no way for the user to find out!  The user just has to “just know” why it is dead.   The most important aspect of a good user interface is that it help people learn how to use it, and that means eliminating things that users have to “just know” ahead of time. Such elements should never be completely dead, instead, they should produce a message explaining why the function can not be used at that time.  Read the rest of this entry »

Leave a comment

Posted by on November 25, 2012 in Design


Tags: , ,

Is the UI Team Broken?

How can you tell if your User Interface (UI) team is broken?  There are some indicators if the programmers implementing the UI are approaching things in a way that is likely to give you a good UI as a result.  This is a real story. Read the rest of this entry »

Leave a comment

Posted by on October 10, 2012 in Design, practice


Tags: , , ,