|
|
User Interface Design: Avoiding the Lack of Design in Your User Interface
written by Peter William Lount Whenever we user our computers or other electonic gadgets we are using a user interface of some sort. User Interfaces are our link to our machines, our way of communicating what we want the machine to do. Our ability to control, use, manipulate, and benefit from software applications is directly dependent upon the qualities of its particular user interfaces. Unfortunetly, more often than not these user interfaces are a problem for users in that they are difficult to understand, they are not consistent with "user interface standards", they let the user perform invalid application functions, lock the user into "limited modes" that restrict choices or they contain design errors that prevent the user for operating the application. Whatever the problem a particular interface has its user is the one who suffers with extra work, frustration, ineffectiveness, lost productivity and even anger. Ultimately the software authors also suffer. First we'll refer you to The Interface Hall of Shame which provides an indepth analysis of many minor and major errors made in real applications from software providers of all sizes. Many of these may just be anoyances, but none the less they are significant road blocks in our interactions with our computers, appliances, gadgets, gizmos, and software applications. At best an anoyance. At worst lives could be lost (have you ever looked at an modern airplane's computer screen and how complex its interfaces are?) The Interface Hall of Shame "The Interface Hall of Shame is an irreverent look at ineffective interface design. The site includes a collection of images from commercial, corporate, and shareware applications that illustrate how software should not be designed." So that's how not to design user interfaces. How do you bring good design qualities to your applications user interface design?
THE INMATES ARE RUNNING THE ASYLUM:
What do you get when you cross an airplane with a computer? In December 1995, American Airlines Flight 965 departed from Miami on a regularly scheduled trip to Cali, Columbia. On the landing approach, the pilot of the 757 needed to select the next radio navigation fix, named "ROZO." He entered an "R" into his navigation computer. The computer returned a list of nearby navigation fixes starting with "R" and the pilot selected the first of these, whose latitude and longitude appeared to be correct. Unfortunately, instead of "ROZO," the pilot selected "ROMEO," 132 miles to the northeast. The jet was southbound, descending into a valley that runs north-south, and any lateral deviation was dangerous. Following indications on the flight computer, the pilots began an easterly turn and slammed into a granite peak at 10,000 feet. One hundred and fifty two passengers and all eight crewmembers aboard perished. Four passengers survived with serious injuries. The National Transportation Safety Board investigated, and-- as usual-- declared the problem human error. The navigational aid the pilots were following was valid but not for the landing procedure at Cali. In the literal definition of the phrase, this was indeed human error, because the pilot selected the wrong fix. However, in the larger picture, it wasn't the pilot's fault at all . The front panel of the airplane's navigation computer showed the currently selected navigation fix and a course deviation indicator. When the plane is on course, the needle is centered, but the needle gives no indication whatsoever about the correctness of the selected radio beacon. The gauge looks pretty much the same just before landing as it does just before crashing. The computer told the pilot he was tracking precisely to the beacon he had selected. Unfortunately, it neglected to tell him the beacon he selected was a fatal choice. -- Exerpt from THE INMATES ARE RUNNING THE ASYLUM "The Interface Hall of Fame The Interface Hall of Fame is a collection of images that demonstrate interface design solutions that are both creative and effective." Principles of good GUI Design Graphical user interfaces (GUIs) have become the user interface of choice. Yet despite the GUI's popularity, surprisingly few programs exhibit good interface design. Moreover, finding information explaining what constitutes a good and intuitive interface is exceedingly difficult. In this article, I describe the basic rules for all good interfaces - the cardinal dos and don'ts. Graphical User Interface Design Guidelines Interface design guidelines specify a "common and consistent" use of graphical elements and controls for an application. There are a number of different guidelines, however basic elements and controls are common to all of them. The main interface guidelines that are "standard" are:
Copyright 1 9 9 9 - 2 0 1 0 b y S m a l l t a l k . o r g "! , A l l R i g h t s R e s e r v e d . |
|