User interface design
From Wikipedia, the free encyclopedia
User interface design or user interface engineering is the design of computers, appliances, machines, mobile communication devices, software applications, and websites with the focus on the user’s experience and interaction. Where traditional graphic design seeks to make the object or application physically attractive, the goal of user interface design is to make the user’s interaction as intuitive as possible—what is often called user-centered design. Where good graphic/industrial design is bold and eye catching, good user interface design is to facilitate finishing the task at hand over drawing attention to itself. Graphic design may be utilized to apply a theme or style to the interface without compromising its intuitive usability. The intuitiveness of an interface may depend on symbology from an artistic perspective as much as functionality from a technical engineering perspective. User Interface design is involved in a wide range of projects from computer systems, to cars, to commercial planes; all of these projects involve much of the same basic human interaction yet also require some unique skills and knowledge. As a result, user interface designers tend to specialize in certain types of projects and have skills centered around their expertise, whether that be software design, user research, web design, or industrial design.Processes
There are several phases and processes in the user interface design some of which are more demanded upon than others depending on the project. (note for the remainder of this section the word system is used to denote any project whether it is a web site, application, or device) * Functionality requirements gathering – assembling a list of the functionality required of the system to accomplish the goals of the project and the potential needs of the users.
* User analysis – analysis of the potential users of the system either through discussion with people who work with the users and/or the potential users themselves. Typical questions involve:
o What would the user want the system to do?
o How would the system fit in with the user’s normal workflow or daily activities?
o How technically savvy is the user and what similar systems does the user already use?
o What interface look & feel styles appeal to the user?
* Information architecture – development of the process and/or information flow of the system (i.e. for phone tree systems, this would be an option tree flowchart and for web sites this would be a site flow that shows the hierarchy of the pages).
* Prototyping – development of wireframes, either in the form of paper prototypes or simple interactive screens. These prototypes are stripped of all look & feel elements and most content in order to concentrate on the interface.
* Usability testing – testing of the prototypes on an actual user—often using a technique called talk aloud protocol where you ask the user to talk about their thoughts during the experience.
* Graphic Interface design – actual look & feel design of the final graphical user interface (GUI.) It may be based on the findings developed during the usability testing if usability is unpredictable, or based on communication objectives and styles that would appeal to the user. In rare cases, the graphics may drive the prototyping, depending on the importance of visual form versus function. If the interface requires multiple skins, there may be multiple interface designs for one control panel, functional feature or widget. This phase is often a collaborative effort between a graphic designer and a user interface designer, or handled by one who is proficient in both disciplines.
User interface design needs good understanding of user needs.
Criticism against the termThe term is currently criticized because its focus is more narrow than the overall user experience. Too much concentration on the technical aspects of user interface distracts the designer from the overall activity (see Activity theory) and real goals of users. Nevertheless, while the terms are often discussed in methodological disputes, the activities behind them are much the same.