Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
User interface design
open-in-new
<h2 id="three-types-of-user-interfaces">Three types of user interfaces</h2> <a href="/facts/Graphical_user_interface/wBlQFWDP">Graphical</a> user interfaces (GUIs) Users interact with visual representations on a computer's screen. The desktop is an example of a GUI. Interfaces controlled through <a href="/facts/Voice_user_interface/jkdI6nGy">voice</a> Users interact with these through their voices. Most smart assistants, such as <a href="/facts/Siri/wfkBV2dF">Siri</a> on smartphones or Alexa on Amazon devices, use voice control. Interactive interfaces utilizing <a href="/facts/Gesture_recognition/jly3YdnY">gestures</a> Users interact with 3D design environments through their bodies, e.g., in <a href="/facts/Virtual_reality/0psDGsxT">virtual reality</a> (VR) games. <p>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 interactions yet also require some unique skills and knowledge. As a result, designers tend to specialize in certain types of projects and have skills centered on their expertise, whether it is <a href="/facts/Software_design/61rGr5Ej">software design</a>, user research, <a href="/facts/Web_design/1uNCN7qE">web design</a>, or <a href="/facts/Industrial_design/6oBprKds">industrial design</a>. </p><p>Good user interface design facilitates finishing the task at hand without drawing unnecessary attention to itself. <a href="/facts/Graphic_design/CJu4SYuG">Graphic design</a> and <a href="/facts/Typography/byx4sANl">typography</a> are utilized to support its <a href="/facts/Usability/zuAnqu9Q">usability</a>, influencing how the user performs certain interactions and improving the <a href="/facts/Aesthetics/FSD8f7oF">aesthetic</a> appeal of the design; design aesthetics may enhance or detract from the ability of users to use the functions of the interface.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> The design process must balance technical functionality and visual elements (e.g., <a href="/facts/Mental_model/ErV8WY6h">mental model</a>) to create a system that is not only operational but also usable and adaptable to changing user needs. </p> <h2 id="ui-design-vs-ux-design">UI design vs. UX design</h2> <p>Compared to <a href="/facts/User_experience_design/wYjvMsf8">UX design</a>, UI design is more about the surface and overall look of a design. User interface design is a craft in which designers perform an important function in creating the user experience. UI design should keep users informed about what is happening, giving appropriate feedback in a timely manner. The visual look and feel of UI design sets the tone for the user experience.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> On the other hand, the term UX design refers to the entire process of creating a user experience. </p> <p><a href="/facts/Don_Norman/QFfnA2m4">Don Norman</a> and <a href="/facts/Jakob_Nielsen_(usability_consultant)/faoYR7ku">Jakob Nielsen</a> said: </p><blockquote><p>It's important to distinguish the total user experience from the user interface (UI), even though the UI is obviously an extremely important part of the design. As an example, consider a website with movie reviews. Even if the UI for finding a film is perfect, the UX will be poor for a user who wants information about a small independent release if the underlying database only contains movies from the major studios.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a></p></blockquote> <h2 id="design-thinking">Design thinking</h2> <p>User interface design requires a good understanding of user needs. It mainly focuses on the needs of the platform and its user expectations. There are several phases and processes in the user interface design, some of which are more demanded upon than others, depending on the project.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> The modern <a href="/facts/Design_thinking/8a481c2b">design thinking</a> framework was created in 2004 by <a href="/facts/David_M._Kelley/2PKLeMbs">David M. Kelley</a>, the founder of Stanford’s d.school, formally known as the <a href="/facts/Hasso_Plattner_Institute_of_Design/SmlTcBpR">Hasso Plattner Institute of Design</a>.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> EDIPT is a common acronym used to describe Kelley’s design thinking framework—it stands for empathize, define, ideate, prototype, and test.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> Notably, the EDIPT framework is non-linear, therefore a UI designer may jump from one stage to another when developing a user-centric solution. Iteration is a common practice in the design thinking process; successful solutions often require testing and tweaking to ensure that the product fulfills user needs.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> </p> <h3>EDIPT</h3> Empathize Conducting user research to better understand the needs and pain points of the target audience. UI designers should avoid developing solutions based on personal beliefs and instead seek to understand the unique perspectives of various users. Qualitative data is often gathered in the form of <a href="/facts/Semi-structured_interview/UXnWGBaa">semi-structured interviews</a>.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> <p>Common areas of interest include: </p> <ul><li>What would the user want the system to do?</li> <li>How would the system fit in with the user's normal workflow or daily activities?</li> <li>How technically savvy is the user and what similar systems does the user already use?</li> <li>What interface aesthetics and functionalities styles appeal to the user?</li></ul> Define Solidifying a <a href="/facts/Problem_statement/ockXc4Dw">problem statement</a> that focuses on user needs and desires; effective problem statements are typically one sentence long and include the user, their specific need, and their desired outcome or goal. Ideate Brainstorming potential solutions to address the refined problem statement. The proposed solutions should ideally align with the stakeholders' feasibility and viability criteria while maintaining user desirability standards. Prototype Designing potential solutions of varying fidelity (low, mid, and high) while applying user experience principles and methodologies. Prototyping is an iterative process where UI designers should explore multiple design solutions rather than settling on the initial concept. Test Presenting the prototypes to the target audience to gather feedback and gain insights for improvement. Based on the results, UI designers may need to revisit earlier stages of the design process to enhance the prototype and <a href="/facts/User_experience/0GF3UETu">user experience</a>. <h2 id="usability-testing">Usability testing</h2> <p>The <a href="/facts/Nielsen_Norman_Group/w0peCv6E">Nielsen Norman Group</a>, co-founded by <a href="/facts/Jakob_Nielsen_(usability_consultant)/faoYR7ku">Jakob Nielsen</a> and <a href="/facts/Don_Norman/QFfnA2m4">Don Norman</a> in 1998, promotes user experience and interface design education. Jakob Nielsen pioneered the interface <a href="/facts/Usability/zuAnqu9Q">usability</a> movement and created the "10 Usability Heuristics for User Interface Design."<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> Usability is aimed at defining an interface’s quality when considering ease of use; an interface with low usability will burden a user and hinder them from achieving their goals, resulting in the dismissal of the interface. To enhance usability, user experience researchers may conduct <a href="/facts/Usability_testing/prsYgc00">usability testing</a>—a process that evaluates how users interact with an interface. Usability testing can provide insight into user pain points by illustrating how efficiently a user can complete a task without error, highlighting areas for design improvement.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> </p> Usability inspection Letting an evaluator inspect a user interface. This is generally considered to be cheaper to implement than usability testing (see step below), and can be used early on in the development process since it can be used to evaluate prototypes or specifications for the system, which usually cannot be tested on users. Some common usability inspection methods include <a href="/facts/Cognitive_walkthrough/YrkHJ01d">cognitive walkthrough</a>, which focuses the simplicity to accomplish tasks with the system for new users, <a href="/facts/Heuristic_evaluation/1VzbMCmJ">heuristic evaluation</a>, in which a set of heuristics are used to identify usability problems in the UI design, and <a href="/facts/Pluralistic_walkthrough/2FYEQSrW">pluralistic walkthrough</a>, in which a selected group of people step through a task scenario and discuss usability issues. Usability testing Testing of the prototypes on an actual user—often using a technique called <a href="/facts/Think_aloud_protocol/IN3N3jhm">think aloud protocol</a> where the user is asked to talk about their thoughts during the experience. User interface design testing allows the designer to understand the reception of the design from the viewer's standpoint, and thus facilitates creating successful applications. <h2 id="requirements">Requirements</h2> <p>The dynamic characteristics of a system are described in terms of the dialogue requirements contained in seven principles of part 10 of the ergonomics standard, the <a href="/facts/ISO_9241/G1TIdbCW">ISO 9241</a>. This standard establishes a framework of ergonomic "principles" for the dialogue techniques with high-level definitions and illustrative applications and examples of the principles. The principles of the dialogue represent the dynamic aspects of the interface and can be mostly regarded as the "feel" of the interface. </p> <h3>Seven dialogue principles</h3> Suitability for the task The dialogue is suitable for a task when it supports the user in the effective and efficient completion of the task. Self-descriptiveness The dialogue is self-descriptive when each dialogue step is immediately comprehensible through feedback from the system or is explained to the user on request. Controllability The dialogue is controllable when the user is able to initiate and control the direction and pace of the interaction until the point at which the goal has been met. Conformity with user expectations The dialogue conforms with user expectations when it is consistent and corresponds to the user characteristics, such as task knowledge, education, experience, and to commonly accepted conventions. Error tolerance The dialogue is error-tolerant if, despite evident errors in input, the intended result may be achieved with either no or minimal action by the user. Suitability for individualization The dialogue is capable of individualization when the interface software can be modified to suit the task needs, individual preferences, and skills of the user. Suitability for learning The dialogue is suitable for learning when it supports and guides the user in learning to use the system. <p>The concept of usability is defined of the <a href="/facts/ISO_9241/G1TIdbCW">ISO 9241</a> standard by effectiveness, efficiency, and satisfaction of the user. </p><p>Part 11 gives the following definition of usability: </p> <ul><li>Usability is measured by the extent to which the intended goals of use of the overall system are achieved (effectiveness).</li> <li>The resources that have to be expended to achieve the intended goals (efficiency).</li> <li>The extent to which the user finds the overall system acceptable (satisfaction).</li></ul> <p>Effectiveness, efficiency, and satisfaction can be seen as quality factors of usability. To evaluate these factors, they need to be decomposed into sub-factors, and finally, into usability measures. </p><p>The information presented is described in Part 12 of the <a href="/facts/ISO_9241/G1TIdbCW">ISO 9241</a> standard for the organization of information (arrangement, alignment, grouping, labels, location), for the display of graphical objects, and for the coding of information (abbreviation, colour, size, shape, visual cues) by seven attributes. The "attributes of presented information" represent the static aspects of the interface and can be generally regarded as the "look" of the interface. The attributes are detailed in the recommendations given in the standard. Each of the recommendations supports one or more of the seven attributes. </p> <h3>Seven presentation attributes</h3> Clarity The information content is conveyed quickly and accurately. Discriminability The displayed information can be distinguished accurately. Conciseness Users are not overloaded with extraneous information. Consistency A unique design, conformity with user's expectation. Detectability The user's attention is directed towards information required. Legibility Information is easy to read. Comprehensibility The meaning is clearly understandable, unambiguous, interpretable, and recognizable. <h3>Usability</h3> <p>The user guidance in Part 13 of the <a href="/facts/ISO_9241/G1TIdbCW">ISO 9241</a> standard describes that the user guidance information should be readily distinguishable from other displayed information and should be specific for the current context of use. </p><p>User guidance can be given by the following five means: </p> <ul><li>Prompts indicating explicitly (specific prompts) or implicitly (generic prompts) that the system is available for input.</li> <li>Feedback informing about the user's input timely, perceptible, and non-intrusive.</li> <li>Status information indicating the continuing state of the application, the system's hardware and software components, and the user's activities.</li> <li>Error management including error prevention, error correction, user support for error management, and error messages.</li> <li>On-line help for system-initiated and user-initiated requests with specific information for the current context of use.</li></ul> <h2 id="research">Research</h2> <p>User interface design has been a topic of considerable research, including on its <a href="/facts/Aesthetics/FSD8f7oF">aesthetics</a>.<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> Standards have been developed as far back as the 1980s for defining the usability of software products. One of the structural bases has become the IFIP user interface reference model. </p><p>The model proposes four dimensions to structure the user interface: </p> <ul><li>The input/output dimension (the look)</li> <li>The dialogue dimension (the feel)</li> <li>The technical or functional dimension (the access to tools and services)</li> <li>The organizational dimension (the communication and co-operation support)</li></ul> <p>This model has greatly influenced the development of the international standard <a href="/facts/ISO_9241/G1TIdbCW">ISO 9241</a> describing the interface design requirements for usability. The desire to understand application-specific UI issues early in software development, even as an application was being developed, led to research on GUI rapid prototyping tools that might offer convincing simulations of how an actual application might behave in production use.<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a> Some of this research has shown that a wide variety of programming tasks for GUI-based software can, in fact, be specified through means other than writing program code.<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a> </p><p>Research in recent years is strongly motivated by the increasing variety of devices that can, by virtue of <a href="/facts/Moore%2527s_law/90CSekhl">Moore's law</a>, host very complex interfaces.<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a> </p> <h2 id="see-also">See also</h2> Wikiversity has learning resources about <i>User interfaces</i> <ul><li><a href="/facts/Chief_experience_officer/G6vufaa0">Chief experience officer</a> (CXO)</li> <li><a href="/facts/Cognitive_dimensions/QS2s13sr">Cognitive dimensions</a></li> <li><a href="/facts/Discoverability/DgccltrA">Discoverability</a></li> <li><a href="/facts/Experience_design/wYjvMsf8">Experience design</a></li> <li><a href="/facts/Gender_HCI/pVMrkFmY">Gender HCI</a></li> <li><a href="/facts/Human_interface_guidelines/U9WBXEQo">Human interface guidelines</a></li> <li><a href="/facts/Human-computer_interaction/EkmIxGCx">Human-computer interaction</a></li> <li><a href="/facts/Icon_design/kv2NvgxJ">Icon design</a></li> <li><a href="/facts/Information_architecture/xhAHVzA7">Information architecture</a></li> <li><a href="/facts/Interaction_design/6aKgJFNW">Interaction design</a></li> <li><a href="/facts/Interaction_design_pattern/YPFY8SzN">Interaction design pattern</a></li> <li><a href="/facts/Interaction_Flow_Modeling_Language/KzUH1flw">Interaction Flow Modeling Language</a> (<a href="/facts/IFML/KzUH1flw">IFML</a>)</li> <li><a href="/facts/Interaction_technique/HICbePyA">Interaction technique</a></li> <li><a href="/facts/Knowledge_visualization/xVfxo6FJ">Knowledge visualization</a></li> <li><a href="/facts/Look_and_feel/Uo3RcETT">Look and feel</a></li> <li><a href="/facts/Mobile_interaction/UacJfYSY">Mobile interaction</a></li> <li><a href="/facts/Natural_mapping_(interface_design)/xnoqDCDH">Natural mapping (interface design)</a></li> <li><a href="/facts/New_Interfaces_for_Musical_Expression/zerI9on4">New Interfaces for Musical Expression</a></li> <li><a href="/facts/Participatory_design/uVIUPDTo">Participatory design</a></li> <li><a href="/facts/Principles_of_user_interface_design/2Q6Vyxqq">Principles of user interface design</a></li> <li><a href="/facts/Process-centered_design/JKfCWDVw">Process-centered design</a></li> <li><a href="/facts/Progressive_disclosure/Uh1dJWI1">Progressive disclosure</a></li> <li><a href="/facts/T_Layout/kAjnU87S">T Layout</a></li> <li><a href="/facts/User_experience_design/wYjvMsf8">User experience design</a></li> <li><a href="/facts/User-centered_design/1qLwIbSw">User-centered design</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Norman, D. A. (2002). "Emotion & Design: Attractive things work better". Interactions Magazine, ix (4). pp. 36–42. Archived from the original on Mar 28, 2019. Retrieved 20 April 2014 – via jnd.org. <a href="https://web.archive.org/web/20190328233305/https://jnd.org/emotion_design_attractive_things_work_better/" target="_blank">https://web.archive.org/web/20190328233305/https://jnd.org/emotion_design_attractive_things_work_better/</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Roth, Robert E. (April 17, 2017). "User Interface and User Experience (UI/UX) Design". Geographic Information Science & Technology Body of Knowledge. 2017 (Q2). doi:10.22224/gistbok/2017.2.5. <a href="https://doi.org/10.22224%2Fgistbok%2F2017.2.5" target="_blank">https://doi.org/10.22224%2Fgistbok%2F2017.2.5</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>"The Definition of User Experience (UX)". Nielsen Norman Group. Retrieved 13 February 2022. <a href="https://www.nngroup.com/articles/definition-user-experience/" target="_blank">https://www.nngroup.com/articles/definition-user-experience/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Wolf, Lauren (23 May 2012). "6 Tips for Designing an Optimal User Interface for Your Digital Event". INXPO. Archived from the original on 16 June 2013. Retrieved 22 May 2013. <a href="https://archive.today/20130616121623/http://web.inxpo.com/casting-calls/bid/105506/6-Tips-for-Designing-an-Optimal-User-Interface-for-Your-Digital-Event" target="_blank">https://archive.today/20130616121623/http://web.inxpo.com/casting-calls/bid/105506/6-Tips-for-Designing-an-Optimal-User-Interface-for-Your-Digital-Event</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Dam, Rikke Friis; Siang, Teo Yu (2024-10-01). "The History of Design Thinking". The Interaction Design Foundation. Retrieved 2024-10-01. <a href="https://www.interaction-design.org/literature/article/design-thinking-get-a-quick-overview-of-the-history" target="_blank">https://www.interaction-design.org/literature/article/design-thinking-get-a-quick-overview-of-the-history</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"The Stanford Design Thinking Process – Make:Iterate". 2022-12-15. Retrieved 2024-10-10. <a href="https://makeiterate.com/the-stanford-design-thinking-process/" target="_blank">https://makeiterate.com/the-stanford-design-thinking-process/</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>Dam, Rikke Friis (2024-10-01). "The 5 Stages in the Design Thinking Process". The Interaction Design Foundation. Retrieved 2024-10-01. <a href="https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process" target="_blank">https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>Ann Blandford. "Semi-structured qualitative studies". The Encyclopedia of Human-Computer Interaction, 2nd Ed. Interaction Design Foundation. Retrieved 20 April 2014. <a href="http://www.interaction-design.org/encyclopedia/semi-structured_qualitative_studies.html" target="_blank">http://www.interaction-design.org/encyclopedia/semi-structured_qualitative_studies.html</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>"10 Usability Heuristics for User Interface Design". Nielsen Norman Group. Retrieved 2024-10-09. <a href="https://www.nngroup.com/articles/ten-usability-heuristics/" target="_blank">https://www.nngroup.com/articles/ten-usability-heuristics/</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>"Usability 101: Introduction to Usability". Nielsen Norman Group. Retrieved 2024-10-09. <a href="https://www.nngroup.com/articles/usability-101-introduction-to-usability/" target="_blank">https://www.nngroup.com/articles/usability-101-introduction-to-usability/</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>"The role of context in perceptions of the aesthetics of web pages over time". International Journal of Human–Computer Studies. 2009-01-05. Retrieved 2009-04-02. <a href="http://portal.acm.org/citation.cfm?id=1464532.1465384&coll=GUIDE&dl=GUIDE&CFID=27731682&CFTOKEN=18425618" target="_blank">http://portal.acm.org/citation.cfm?id=1464532.1465384&coll=GUIDE&dl=GUIDE&CFID=27731682&CFTOKEN=18425618</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>"The HUMANOID model of interface design". Proceedings CHI'92. 1992. <a href="http://citeseer.ist.psu.edu/old/szekely92facilitating.html" target="_blank">http://citeseer.ist.psu.edu/old/szekely92facilitating.html</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>"Creating user interfaces using programming by example, visual programming, and constraints". ACM. 1990-04-11. Retrieved 2009-04-02. <a href="http://portal.acm.org/citation.cfm?id=78942.78943&coll=GUIDE&dl=GUIDE&CFID=27731682&CFTOKEN=18425618" target="_blank">http://portal.acm.org/citation.cfm?id=78942.78943&coll=GUIDE&dl=GUIDE&CFID=27731682&CFTOKEN=18425618</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>"Past, present, and future of user interface software tools". ACM. 2000-03-01. Retrieved 2009-04-02. <a href="http://portal.acm.org/citation.cfm?id=344949.344959&coll=GUIDE&dl=GUIDE&CFID=27731682&CFTOKEN=18425618" target="_blank">http://portal.acm.org/citation.cfm?id=344949.344959&coll=GUIDE&dl=GUIDE&CFID=27731682&CFTOKEN=18425618</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> </ol>