Principles of Designing user interface
The design of a user interface for web pages and software programs is important in determining user interaction with the computer resources. Usability of user interfaces is defined by the way users relate to the contents and processes that may be taking place (ENDECA, 2012). The principles of human interface design outline the good practices that programmers and designers should follow in designing an effective user interface for websites (Mathis, 2010). Usability is a measure of the extent to which the user is able to interpret the contents, manipulate objects and accomplish tasks.
The user interface should be designed in a manner that portrays its usefulness (Lewis & Rieman, 1994). All the important issues are addressed through the provision of the necessary utilities. In web pages the utilities can be in the form of web links for easy navigation, buttons and guideline information. The interface should only consist of the necessary utilities. All features on an interface should have a purpose to serve in the accomplishment of the intended purpose. For example buttons in a website’s interface should be associated with a certain function that is important in accomplishment of the tasks intended (Skaalid, 1999).
The design of user interfaces should be consistent (Edtech, n.d). The features in an interface should have a uniform standard that is applicable to the application being addressed. In web pages consistency can be applied in related web pages in features like the background color, the fonts used and the mode of presentation (Usability Professionals’ Association, 2010). Real world conventions that are familiar should be applied to ensure the information is presented in a logical way.
The designers should consider the simplicity of user interfaces (Elsevierdirect, n.d). The simplicity can be implemented by considering the visibility of the features and the ease of interpreting the information on the interface. Unnecessary elements should be avoided to make sure that they don’t block the visibility of the important features (Electronic Ink, 2012). The components displayed should be self explanatory in enabling the users to interact with the website with minimal instruction.
Designers should provide a way in which the interface responds to user’s action (Cornell University, n.d). Interfaces that provide feedbacks enable the user to know their position in accomplishing their tasks. In websites that require users to input information, the interface should be designed to give a feedback on whether the information was taken or not. Websites should have a way of providing the user with a way to view the progress of events. For example in a website with music playing software, the interface should display the status of the music being played by showing elements such as the remaining time or by providing a feature that represents the flow of events. In monitoring of events such as during a copying operation, the website should enable the user to view the progress by providing an appropriate interface (Oppedisano, 2002).
The structure of the displayed elements should be organized in groups of related objects to ensure easy accessibility. For example the buttons in a music player should be organized according to their function. In this the buttons for increasing and reducing volume should be close to each other or arranged in a way that portrays their relationship (Einstein, 1997).
Sequencing of events should be done in a manner that follows a simple logic. For example in an interface involving several steps, the bottom for taking the next action should always be on either the right side or left side depending on the users’ logic. Alternating the position for moving forward and that of going back should be avoided (Lanter, n.d).
The website should have a mechanism that prevents the user from making errors (Ian Somerville, 2004). Websites that require user input should have a way of filtering the data to ensure that correct information is provided. For example a website should be able to detect wrong formats for entries such as email and date by prompting the user if the format does not follow the correct standard. Websites should ask for user confirmation before executing on commands that that impact on important issues. Such websites involving critical issues like money transactions should have an interface that ensures the user is fully aware of their actions and the consequences (Martin, n.d). Designers should provide for an error recovery mechanism that is clearly understood by the users. The error recovery messages should be in a clear language with instructions on how to undo or redo certain actions.
The designers should consider the different level of knowledge among the users. Different level of control mechanism should be provided. Shortcuts and styles should be available for the experienced users (Webcredible, 2012). The interface should support automation of certain functions to reduce unnecessary repetition of events for some users. For example in a website with a music player, the interface should provide a mechanism for playing the next song without the user having to click a button after every song.
Well designed interfaces are simple to use, reduce work load and have a level of user satisfaction. Website designers should collaborate with the users in determining how their needs and preferences in website interaction.
References:
Cornell University (n.d). Ergonomic guidelines for user-interface design. Retrieved on April 15, 2012 http://ergo.human.cornell.edu/ahtutorials/interface.html
Edtech (n.d). The Elements of Interface Design. Retrieved on April 15, 2012 http://www.edtech.vt.edu/edtech/id/interface/index.html
Einstein, A. (1997). The Golden Rules of User Interface Design. John Wiley & Sons. Retrieved on April 15, 2012 http://www.theomandel.com/docs/Mandel-GoldenRules.pdf
Electronic Ink (2012). Being Usable Is Nothing to Brag About. Electronic Ink, Inc. Retrieved on April 15, 2012 http://www.electronicink.com/does-usability-equate-to-mediocrity/
Elsevierdirect (n.d). User Interface Design. Retrieved on April 15, 2012 http://www.elsevierdirect.com/companions/9780120884360/casestudies/Chapter_01.pdf
ENDECA (2012). User Interface Design Pattern Library. Oracle Corporation. Retrieved on April 15, 2012 http://patterns.endeca.com/content/library/en/home.html
Ian Summerville (2004). User interface design. Software Engineering, 7th edition. Chapter 16. Retrieved on April 15, 2012 http://www.comp.lancs.ac.uk/computing/resources/IanS/SE7/Presentations/PDF/ch16.pdf
Lanter, D. (n.d). User-Centered Graphical User Interface Design for GIS. Department of Geography University of California at Santa Barbara Santa Barbara, CA 93106. Retrieved on April 15, 2012 http://www.ncgia.ucsb.edu/Publications/tech-reports/91/91-6.pdf
Lewis, C. & Rieman, J. (1994). Task-Centered User Interface Design. Retrieved on April 15, 2012 http://hcibib.org/tcuid/
Mathis, L. (2010). Realism in UI Design. Retrieved on April 15, 2012 http://ignorethecode.net/blog/2010/01/21/realism_in_ui_design/
Martin, S. (n.d). Effective Visual Communication for Graphical User Interfaces. Retrieved on April 15, 2012 http://web.cs.wpi.edu/~matt/courses/cs563/talks/smartin/int_design.html
Oppedisano, E. (2002). Common Principles: A Usable Interface Design Primer. Retrieved on April 15, 2012 http://www.usabilityprofessionals.org/upa_publications/upa_voice/volumes/4/issue_3/common_principles.htm
Skaalid, B. (1999). Human-Computer Interface Design. Retrieved on April 15, 2012 http://www.usask.ca/education/coursework/skaalid/theory/interface.htm
Usability Professionals’ Association (2010). Principles for Usable Design. Usability Body of Knowledge. Retrieved on April 15, 2012 http://www.usabilitybok.org/design/p287
Webcredible (2012). Innovative user interface design. Retrieved on April 15, 2012 http://www.webcredible.co.uk/user-friendly-resources/web-usability/user-interface-design.shtml
