Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
User interface
open-in-new
<h2 id="overview">Overview</h2> <p>The user interface or <i>human–machine interface</i> is the part of the machine that handles the human–machine interaction. Membrane switches, rubber keypads and touchscreens are examples of the physical part of the Human Machine Interface which we can see and touch.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> </p><p>In complex systems, the human–machine interface is typically computerized. The term <i>human–computer interface</i> refers to this kind of system. In the context of computing, the term typically extends as well to the software dedicated to control the physical elements used for <a href="/facts/Human%E2%80%93computer_interaction/EkmIxGCx">human–computer interaction</a>. </p><p>The engineering of human–machine interfaces is enhanced by considering <a href="/facts/Ergonomics/prAcGtDW">ergonomics</a> (<a href="/facts/Human_factors/prAcGtDW">human factors</a>). The corresponding disciplines are <a href="/facts/Human_factors_engineering/prAcGtDW">human factors engineering</a> (HFE) and <a href="/facts/Usability_engineering/ntt2N6ET">usability engineering</a> (UE) which is part of <a href="/facts/Systems_engineering/gFwRmkDp">systems engineering</a>. </p><p>Tools used for incorporating human factors in the interface design are developed based on knowledge of <a href="/facts/Computer_science/lN3pEyPz">computer science</a>, such as <a href="/facts/Computer_graphics/lapBE8wv">computer graphics</a>, <a href="/facts/Operating_systems/8XTuvMh2">operating systems</a>, <a href="/facts/Programming_language/cWTYbgWa">programming languages</a>. Nowadays, we use the expression <a href="/facts/Graphical_user_interface/wBlQFWDP">graphical user interface</a> for human–machine interface on computers, as nearly all of them are now using graphics. </p><p><a href="/facts/Multimodal_interface/VFGkgJxm">Multimodal interfaces</a> allow users to interact using more than one <a href="/facts/Modality_(human%E2%80%93computer_interaction)/KzL4uqMm">modality</a> of user input.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p> <h2 id="terminology">Terminology</h2> <p>There is a difference between a user interface and an operator interface or a human–machine interface (HMI). </p> <ul><li>The term "user interface" is often used in the context of (personal) computer systems and <a href="/facts/Electronics/E4JhgISq">electronic devices</a>. <ul><li>Where a network of equipment or computers are interlinked through an MES (Manufacturing Execution System)-or Host to display information.</li> <li>A human–machine interface (HMI) is typically local to one machine or piece of equipment, and is the interface method between the human and the equipment/machine. An operator interface is the interface method by which multiple pieces of equipment, linked by a host control system, are accessed or controlled.</li> <li>The system may expose several user interfaces to serve different kinds of users. For example, a <a href="/facts/Digital_library/aBCP81In">computerized library database</a> might provide two user interfaces, one for library patrons (limited set of functions, optimized for ease of use) and the other for library personnel (wide set of functions, optimized for efficiency).<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a></li></ul></li> <li>The user interface of a <a href="/facts/Machine/wTCxFRfs">mechanical</a> system, a vehicle or an <a href="/facts/Industry_(manufacturing)/3qW7bcdy">industrial</a> installation is sometimes referred to as the human–machine interface (HMI).<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> HMI is a modification of the original term MMI (man–machine interface).<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> In practice, the abbreviation MMI is still frequently used<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> although some may claim that MMI stands for something different now. Another abbreviation is HCI, but is more commonly used for <a href="/facts/Human%E2%80%93computer_interaction/EkmIxGCx">human–computer interaction</a>.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> Other terms used are operator interface console (OIC) and operator interface terminal (OIT).<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> However it is abbreviated, the terms refer to the 'layer' that separates a human that is operating a machine from the machine itself.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> Without a clean and usable interface, humans would not be able to interact with information systems.</li></ul> <p>In <a href="/facts/Science_fiction/d9hE2Lwt">science fiction</a>, HMI is sometimes used to refer to what is better described as a <a href="/facts/Direct_neural_interface/wdXWqFVr">direct neural interface</a>. However, this latter usage is seeing increasing application in the real-life use of (medical) <a href="/facts/Prostheses/odTuXtC0">prostheses</a>—the artificial extension that replaces a missing body part (e.g., <a href="/facts/Cochlear_implants/Cz022Fd5">cochlear implants</a>).<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a><a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> </p><p>In some circumstances, computers might observe the user and react according to their actions without specific commands. A means of <a href="/facts/Positional_tracking/aV3Sy9lm">tracking parts of the body</a> is required, and sensors noting the position of the head, <a href="/facts/Eye_tracking/xHrkQeh6">direction of gaze</a> and so on have been used experimentally. This is particularly relevant to <a href="/facts/Immersive_digital_environment/qS90xlqs">immersive interfaces</a>.<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a><a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a> </p> <h2 id="history">History</h2> <p>The history of user interfaces can be divided into the following phases according to the dominant type of user interface: </p> <h3>1945–1968: Batch interface</h3> <p>In the batch era, computing power was extremely scarce and expensive. User interfaces were rudimentary. Users had to accommodate computers rather than the other way around; user interfaces were considered overhead, and software was designed to keep the processor at maximum utilization with as little overhead as possible. </p><p>The input side of the user interfaces for batch machines was mainly <a href="/facts/Punched_card/44WsPulQ">punched cards</a> or equivalent media like <a href="/facts/Paper_tape/8HI7dThI">paper tape</a>. The output side added <a href="/facts/Line_printer/QyWwtNBJ">line printers</a> to these media. With the limited exception of the system <a href="/facts/System_console/FhWph34D">operator's console</a>, human beings did not interact with batch machines in real time at all. </p><p>Submitting a job to a batch machine involved first preparing a deck of punched cards that described a program and its dataset. The program cards were not punched on the computer itself but on <a href="/facts/Keypunch/vbtX99wD">keypunches</a>, specialized, typewriter-like machines that were notoriously bulky, unforgiving, and prone to mechanical failure. The software interface was similarly unforgiving, with very strict syntaxes designed to be parsed by the smallest possible compilers and interpreters. </p> <p>Once the cards were punched, one would drop them in a job queue and wait. Eventually, operators would feed the deck to the computer, perhaps mounting <a href="/facts/Magnetic_tape_data_storage/qJUpJnk9">magnetic tapes</a> to supply another dataset or helper software. The job would generate a printout, containing final results or an abort notice with an attached error log. Successful runs might also write a result on magnetic tape or generate some data cards to be used in a later computation. </p><p>The <a href="/facts/Turnaround_time/jyTLoWPD">turnaround time</a> for a single job often spanned entire days. If one was very lucky, it might be hours; there was no real-time response. But there were worse fates than the card queue; some computers required an even more tedious and error-prone process of toggling in programs in binary code using console switches. The very earliest machines had to be partly rewired to incorporate program logic into themselves, using devices known as <a href="/facts/Plugboard/fE3HX8tS">plugboards</a>. </p><p>Early batch systems gave the currently running job the entire computer; program decks and tapes had to include what we would now think of as <a href="/facts/Operating_system/8XTuvMh2">operating system</a> code to talk to I/O devices and do whatever other housekeeping was needed. Midway through the batch period, after 1957, various groups began to experiment with so-called "<a href="/facts/Compile_and_go_system/Bw2okmCz">load-and-go</a>" systems. These used a <a href="/facts/Resident_monitor/GXlI7y7j">monitor program</a> which was always resident on the computer. Programs could call the monitor for services. Another function of the monitor was to do better error checking on submitted jobs, catching errors earlier and more intelligently and generating more useful feedback to the users. Thus, monitors represented the first step towards both operating systems and explicitly designed user interfaces. </p> <h3>1969–present: Command-line user interface</h3> <p class="note">Main article: <a href="/facts/Command-line_interface/R9JpGmXQ">Command-line interface</a></p> <p>Command-line interfaces (CLIs) evolved from batch monitors connected to the system console. Their interaction model was a series of request-response transactions, with requests expressed as textual commands in a specialized vocabulary. Latency was far lower than for batch systems, dropping from days or hours to seconds. Accordingly, command-line systems allowed the user to change their mind about later stages of the transaction in response to real-time or near-real-time feedback on earlier results. Software could be exploratory and interactive in ways not possible before. But these interfaces still placed a relatively heavy <a href="/facts/Mnemonic/6HfDn0ks">mnemonic</a> load on the user, requiring a serious investment of effort and learning time to master.<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a> </p><p>The earliest command-line systems combined <a href="/facts/Teleprinter/pn5SQKTf">teleprinters</a> with computers, adapting a mature technology that had proven effective for mediating the transfer of information over wires between human beings. Teleprinters had originally been invented as devices for automatic telegraph transmission and reception; they had a history going back to 1902 and had already become well-established in newsrooms and elsewhere by 1920. In reusing them, economy was certainly a consideration, but psychology and the <a href="/facts/Principle_of_least_astonishment/J15J6u9n">rule of least surprise</a> mattered as well; teleprinters provided a point of interface with the system that was familiar to many engineers and users. </p> <p>The widespread adoption of video-display terminals (VDTs) in the mid-1970s ushered in the second phase of command-line systems. These cut latency further, because characters could be thrown on the phosphor dots of a screen more quickly than a printer head or carriage can move. They helped quell conservative resistance to interactive programming by cutting ink and paper consumables out of the cost picture, and were to the first TV generation of the late 1950s and 60s even more iconic and comfortable than teleprinters had been to the computer pioneers of the 1940s. </p><p>Just as importantly, the existence of an accessible screen—a two-dimensional display of text that could be rapidly and reversibly modified—made it economical for software designers to deploy interfaces that could be described as visual rather than textual. The pioneering applications of this kind were computer games and text editors; close descendants of some of the earliest specimens, such as <a href="/facts/Rogue_(video_game)/4pWC2hM8">rogue</a>(6), and <a href="/facts/Vi_(text_editor)/d8G1PkDh">vi</a>(1), are still a live part of <a href="/facts/Unix/0pNL2seI">Unix</a> tradition. </p> <h3>1985: SAA user interface or text-based user interface</h3> <p>In 1985, with the beginning of <a href="/facts/Microsoft_Windows/bwhAhuSL">Microsoft Windows</a> and other <a href="/facts/Graphical_user_interface/wBlQFWDP">graphical user interfaces</a>, IBM created what is called the <a href="/facts/IBM_Systems_Application_Architecture/C00QJr21">Systems Application Architecture</a> (SAA) standard which include the <a href="/facts/IBM_Common_User_Access/4qhD1WvG">Common User Access</a> (CUA) derivative. CUA successfully created what we know and use today in Windows, and most of the more recent <a href="/facts/DOS/sWwDXNmX">DOS</a> or Windows Console Applications will use that standard as well. </p><p>This defined that a pulldown menu system should be at the top of the screen, status bar at the bottom, shortcut keys should stay the same for all common functionality (F2 to Open for example would work in all applications that followed the SAA standard). This greatly helped the speed at which users could learn an application so it caught on quick and became an industry standard.<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a> </p> <h3>1968–present: Graphical user interface</h3> <p class="note">Main article: <a href="/facts/Graphical_user_interface/wBlQFWDP">Graphical user interface</a></p> <ul><li>1968 – <a href="/facts/Douglas_Engelbart/gHT4dFLS">Douglas Engelbart</a> demonstrated <a href="/facts/NLS_(computer_system)/SCr9PYJF">NLS</a>, a system which uses a <a href="/facts/Computer_mouse/fJpa1tUE">mouse</a>, <a href="/facts/Pointer_(user_interface)/bGhgwPSq">pointers</a>, <a href="/facts/Hypertext/qD8ozxSb">hypertext</a>, and multiple <a href="/facts/Window_(computing)/g39X0vV3">windows</a>.<a class="footnote-ref" id="fnref:16" href="#fn:16"><sup>16</sup></a></li> <li>1970 – Researchers at <a href="/facts/PARC_(company)/fh2Su0k9">Xerox Palo Alto Research Center</a> (many from <a href="/facts/SRI_International/flSHunVK">SRI</a>) develop <a href="/facts/WIMP_(computing)/cJcV8GAA">WIMP</a> paradigm (Windows, Icons, Menus, Pointers)<a class="footnote-ref" id="fnref:17" href="#fn:17"><sup>17</sup></a></li> <li>1973 – <a href="/facts/Xerox_Alto/6pjFTD0A">Xerox Alto</a>: commercial failure due to expense, poor user interface, and lack of programs<a class="footnote-ref" id="fnref:18" href="#fn:18"><sup>18</sup></a></li> <li>1979 – <a href="/facts/Steve_Jobs/fQpja1hx">Steve Jobs</a> and other <a href="/facts/Apple_Inc./oTJYta3k">Apple</a> engineers visit Xerox PARC. Though <a href="/facts/Pirates_of_Silicon_Valley/IycD11hX">Pirates of Silicon Valley</a> dramatizes the events, Apple had already been working on developing a GUI, such as the Macintosh and Lisa projects, before the visit.<a class="footnote-ref" id="fnref:19" href="#fn:19"><sup>19</sup></a><a class="footnote-ref" id="fnref:20" href="#fn:20"><sup>20</sup></a></li> <li>1981 – <a href="/facts/Xerox_Star/MT15wQq1">Xerox Star</a>: focus on <a href="/facts/WYSIWYG/aGmcHWpX">WYSIWYG</a>. Commercial failure (25K sold) due to cost ($16K each), performance (minutes to save a file, couple of hours to recover from crash), and poor marketing</li> <li>1982 – <a href="/facts/Rob_Pike/K5R9UoSH">Rob Pike</a> and others at <a href="/facts/Bell_Labs/fKP5Gk0H">Bell Labs</a> designed <a href="/facts/Blit_(computer_terminal)/zWf3htCY">Blit</a>, which was released in 1984 by AT&T and <a href="/facts/Teletype/pn5SQKTf">Teletype</a> as DMD 5620 terminal.</li> <li>1984 – Apple <a href="/facts/Macintosh_128K/oXlQGVpX">Macintosh</a> popularizes the <a href="/facts/GUI/wBlQFWDP">GUI</a>. <a href="/facts/Super_Bowl_commercials/M2V0P5Pl">Super Bowl commercial</a> shown twice, was the most expensive commercial ever made at that time</li> <li>1984 – <a href="/facts/MIT/Xk49vNA8">MIT</a>'s <a href="/facts/X_Window_System/ac2vRIQL">X Window System</a>: hardware-independent platform and networking protocol for developing GUIs on UNIX-like systems</li> <li>1985 – <a href="/facts/Windows_1.0/SfHQ6bIE">Windows 1.0</a> – provided GUI interface to MS-DOS. No overlapping windows (tiled instead).</li> <li>1985 – Microsoft and IBM start work on OS/2 meant to eventually replace MS-DOS and Windows</li> <li>1986 – Apple threatens to sue <a href="/facts/Digital_Research/9bYQl2pI">Digital Research</a> because their GUI desktop looked too much like Apple's Mac.</li> <li>1987 – <a href="/facts/Windows_2.0/KceDrznJ">Windows 2.0</a> – Overlapping and resizable windows, keyboard and mouse enhancements</li> <li>1987 – Macintosh II: first full-color Mac</li> <li>1988 – <a href="/facts/OS/2/uVBl6ItP">OS/2</a> 1.10 Standard Edition (SE) has GUI written by Microsoft, looks a lot like Windows 2</li></ul> <h2 id="interface-design">Interface design</h2> <p class="note">Main article: <a href="/facts/User_interface_design/bHpLP1ae">User interface design</a></p> <p>Primary methods used in the interface design include prototyping and simulation. </p><p>Typical human–machine interface design consists of the following stages: interaction specification, interface software specification and prototyping: </p> <ul><li>Common practices for interaction specification include <a href="/facts/User-centered_design/1qLwIbSw">user-centered design</a>, <a href="/facts/Persona/lMy54oWx">persona</a>, activity-oriented design, scenario-based design, and resiliency design.</li> <li>Common practices for interface software specification include <a href="/facts/Use_cases/8pNHjsIr">use cases</a> and constrain enforcement by <a href="/facts/Interaction_protocol/8HLLfbAj">interaction protocols</a> (intended to avoid use errors).</li> <li>Common practices for prototyping are based on libraries of interface elements (controls, decoration, etc.).</li></ul> <h3>Principles of quality</h3> <p>In broad terms, interfaces generally regarded as user friendly, efficient, intuitive, etc. are typified by one or more particular qualities. For the purpose of example, a non-exhaustive list of such characteristics follows: </p> <ol><li>Clarity: The interface avoids ambiguity by making everything clear through language, flow, hierarchy and metaphors for visual elements.</li> <li><a href="/facts/Concision/KPaPwdaw">Concision</a>:<a class="footnote-ref" id="fnref:21" href="#fn:21"><sup>21</sup></a> However ironically, the over-clarification of information—for instance, by labelling the majority, if not the entirety, of items displayed on-screen at once, and regardless of whether or not the user would in fact require a visual indicator of some kind in order to identify a given item—can, and, under most normal circumstances, most likely will lead to the obfuscation of whatever information.</li> <li>Familiarity:<a class="footnote-ref" id="fnref:22" href="#fn:22"><sup>22</sup></a> Even if someone uses an interface for the first time, certain elements can still be familiar. Real-life metaphors can be used to communicate meaning.</li> <li><a href="/facts/Responsiveness/80sDpDoI">Responsiveness</a>:<a class="footnote-ref" id="fnref:23" href="#fn:23"><sup>23</sup></a> A good interface should not feel sluggish. This means that the interface should provide good feedback to the user about what's happening and whether the user's input is being successfully processed.</li> <li>Consistency:<a class="footnote-ref" id="fnref:24" href="#fn:24"><sup>24</sup></a> Keeping your interface consistent across your application is important because it allows users to recognize usage patterns.</li> <li><a href="/facts/Aesthetics/FSD8f7oF">Aesthetics</a>: While you do not need to make an interface attractive for it to do its job, making something look good will make the time your users spend using your application more enjoyable; and happier users can only be a good thing.</li> <li><a href="/facts/Efficiency/azCNkIzY">Efficiency</a>: Time is money, and a great interface should make the user more productive through shortcuts and good design.</li> <li><a href="/facts/Forgiveness/UPm7rS8A">Forgiveness</a>: A good interface should not punish users for their mistakes but should instead provide the means to remedy them.</li></ol> <h3>Principle of least astonishment</h3> <p>The <a href="/facts/Principle_of_least_astonishment/J15J6u9n">principle of least astonishment</a> (POLA) is a general principle in the design of all kinds of interfaces. It is based on the idea that human beings can only pay full attention to one thing at one time,<a class="footnote-ref" id="fnref:25" href="#fn:25"><sup>25</sup></a> leading to the conclusion that novelty should be minimized. </p> <h3>Principle of habit formation</h3> <p>If an interface is used persistently, the user will unavoidably develop <a href="/facts/Habit/qISaGCqe">habits</a> for using the interface. The designer's role can thus be characterized as ensuring the user forms good habits. If the designer is experienced with other interfaces, they will similarly develop habits, and often make unconscious assumptions regarding how the user will interact with the interface.<a class="footnote-ref" id="fnref:26" href="#fn:26"><sup>26</sup></a><a class="footnote-ref" id="fnref:27" href="#fn:27"><sup>27</sup></a> </p> <h3>A model of design criteria: User Experience Honeycomb</h3> <p>Peter Morville of <a href="/facts/Google/GT9Sugza">Google</a> designed the User Experience Honeycomb framework in 2004 when leading operations in user interface design. The framework was created to guide user interface design. It would act as a guideline for many web development students for a decade.<a class="footnote-ref" id="fnref:28" href="#fn:28"><sup>28</sup></a> </p> <ol><li>Usable: Is the design of the system easy and simple to use? The application should feel familiar, and it should be easy to use.<a class="footnote-ref" id="fnref:29" href="#fn:29"><sup>29</sup></a><a class="footnote-ref" id="fnref:30" href="#fn:30"><sup>30</sup></a></li> <li>Useful: Does the application fulfill a need? A business's product or service needs to be useful.<a class="footnote-ref" id="fnref:31" href="#fn:31"><sup>31</sup></a></li> <li>Desirable: Is the design of the application sleek and to the point? The aesthetics of the system should be attractive, and easy to translate.<a class="footnote-ref" id="fnref:32" href="#fn:32"><sup>32</sup></a></li> <li>Findable: Are users able to quickly find the information they are looking for? Information needs to be findable and simple to navigate. A user should never have to hunt for your product or information.<a class="footnote-ref" id="fnref:33" href="#fn:33"><sup>33</sup></a></li> <li><a href="/facts/Accessibility/hp9gz5GK">Accessible</a>: Does the application support enlarged text without breaking the framework? An application should be accessible to those with disabilities.<a class="footnote-ref" id="fnref:34" href="#fn:34"><sup>34</sup></a></li> <li>Credible: Does the application exhibit trustworthy security and company details? An application should be transparent, secure, and honest.<a class="footnote-ref" id="fnref:35" href="#fn:35"><sup>35</sup></a></li> <li>Valuable: Does the end-user think it's valuable? If all 6 criteria are met, the end-user will find value and trust in the application.<a class="footnote-ref" id="fnref:36" href="#fn:36"><sup>36</sup></a></li></ol> <h2 id="types">Types</h2> <ol><li><i><a href="/facts/Attentive_user_interface/fxfUUHR0">Attentive user interfaces</a></i> manage the user <a href="/facts/Attention/pleJPaeQ">attention</a> deciding when to interrupt the user, the kind of warnings, and the level of detail of the messages presented to the user.</li> <li><i>Batch interfaces</i> are non-interactive user interfaces, where the user specifies all the details of the <i>batch job</i> in advance to <a href="/facts/Batch_processing/hKY2rX3N">batch processing</a>, and receives the output when all the processing is done. The computer does not prompt for further input after the processing has started.</li> <li><i><a href="/facts/Command_line_interface/R9JpGmXQ">Command line interfaces</a></i> (CLIs) prompt the user to provide input by typing a <a href="/facts/Command_(computing)/zUrvQbFy">command string</a> with the computer keyboard and respond by outputting text to the computer monitor. Used by programmers and system administrators, in engineering and scientific environments, and by technically advanced personal computer users.</li> <li><i><a href="/facts/Conversational_interfaces/Dba3y06I">Conversational interfaces</a></i> enable users to command the computer with plain text English (e.g., via text messages, or chatbots) or voice commands, instead of graphic elements. These interfaces often emulate human-to-human conversations.<a class="footnote-ref" id="fnref:37" href="#fn:37"><sup>37</sup></a></li> <li><i>Conversational interface agents</i> attempt to personify the computer interface in the form of an animated person, robot, or other character (such as Microsoft's Clippy the paperclip), and present interactions in a conversational form.</li> <li><i><a href="/facts/Crossing-based_interface/6NT5cLW5">Crossing-based interfaces</a></i> are graphical user interfaces in which the primary task consists in crossing boundaries instead of pointing.</li> <li><i><a href="/facts/Direct_manipulation_interface/XvzG3fQq">Direct manipulation interface</a></i> is a general class of user interfaces that allow users to manipulate objects presented to them, using actions that correspond to the physical world, at least loosely.</li> <li><i><a href="/facts/Gesture_recognition/jly3YdnY">Gesture interfaces</a></i> are graphical user interfaces which accept input in a form of hand <a href="/facts/Gesture/fs7HV1Y6">gestures</a>, or <a href="/facts/Mouse_gesture/D5Psb3hN">mouse gestures</a> sketched with a computer mouse or a <a href="/facts/Stylus_(computing)/j5e1x0vf">stylus</a>.</li> <li><i><a href="/facts/Graphical_user_interface/wBlQFWDP">Graphical user interfaces</a></i> (GUI) accept input via devices such as a computer keyboard and mouse and provide articulated <a href="/facts/Graphical/1V76IF8J">graphical</a> output on the <a href="/facts/Computer_monitor/NRaTDFHc">computer monitor</a>.<a class="footnote-ref" id="fnref:38" href="#fn:38"><sup>38</sup></a> There are at least two different principles widely used in GUI design: <a href="/facts/Object-oriented_user_interface/kovYUlJk">Object-oriented user interfaces</a> (OOUIs) and <a href="/facts/Application_software/YQuj7Kog">application</a>-oriented interfaces.<a class="footnote-ref" id="fnref:39" href="#fn:39"><sup>39</sup></a></li> <li><i>Hardware interfaces</i> are the physical, spatial interfaces found on products in the real world from toasters, to car dashboards, to airplane cockpits. They are generally a mixture of knobs, buttons, sliders, switches, and touchscreens.</li> <li><i>Holographic user interfaces</i> provide input to electronic or electro-mechanical devices by passing a finger through reproduced holographic images of what would otherwise be tactile controls of those devices, floating freely in the air, detected by a wave source and without tactile interaction.</li> <li><i><a href="/facts/Intelligent_user_interfaces/38zS0LMo">Intelligent user interfaces</a></i> are human–machine interfaces that aim to improve the efficiency, effectiveness, and naturalness of human–machine interaction by representing, reasoning, and acting on models of the user, domain, task, discourse, and media (e.g., graphics, natural language, gesture).</li> <li><i><a href="/facts/Motion_capture/vy5ab34S">Motion tracking</a> interfaces</i> monitor the user's body motions and translate them into commands, currently being developed by Apple.<a class="footnote-ref" id="fnref:40" href="#fn:40"><sup>40</sup></a></li> <li><i>Multi-screen interfaces</i>, employ multiple displays to provide a more flexible interaction. This is often employed in computer game interaction in both the commercial arcades and more recently the handheld markets.</li> <li><i><a href="/facts/Natural_language_user_interface/TSsXHy2V">Natural-language interfaces</a></i> are used for search engines and on webpages. User types in a question and waits for a response.</li> <li><i>Non-command user interfaces</i>, which observe the user to infer their needs and intentions, without requiring that they formulate explicit commands.<a class="footnote-ref" id="fnref:41" href="#fn:41"><sup>41</sup></a></li> <li><i><a href="/facts/Object-oriented_user_interface/kovYUlJk">Object-oriented user interfaces</a> (OOUI)</i> are based on <a href="/facts/Object-oriented_programming/TxNMEcao">object-oriented programming</a> metaphors, allowing users to <a href="/facts/Direct_manipulation/XvzG3fQq">manipulate</a> simulated objects and their properties.</li> <li><i>Permission-driven user interfaces</i> show or conceal menu options or functions depending on the user's level of permissions. The system is intended to improve the user experience by removing items that are unavailable to the user. A user who sees functions that are unavailable for use may become frustrated. It also provides an enhancement to security by hiding functional items from unauthorized persons.</li> <li><i>Reflexive user interfaces</i> where the users control and redefine the entire system via the user interface alone, for instance to change its <a href="/facts/Command_verb/gnzzsj19">command verbs</a>. Typically, this is only possible with very rich graphic user interfaces.</li> <li><i>Search interface</i> is how the search box of a site is displayed, as well as the visual representation of the search results.</li> <li><i><a href="/facts/Tangible_user_interface/PmbEvkEb">Tangible user interfaces</a></i>, which place a greater emphasis on touch and physical environment or its element.</li> <li><i><a href="/facts/Task-focused_interface/V8b6epmu">Task-focused interfaces</a></i> are user interfaces which address the <a href="/facts/Information_overload/MopSX9bN">information overload</a> problem of the <a href="/facts/Desktop_metaphor/kWQQNlxu">desktop metaphor</a> by making tasks, not files, the primary unit of interaction.</li> <li><i><a href="/facts/Text-based_user_interface/bngNtqIY">Text-based user interfaces</a></i> (TUIs) are user interfaces which interact via text. TUIs include <a href="/facts/Command-line_interface/R9JpGmXQ">command-line interfaces</a> and text-based <a href="/facts/WIMP_(computing)/cJcV8GAA">WIMP</a> environments.</li> <li><i><a href="/facts/Touchscreen/zpSKDFpe">Touchscreens</a></i> are displays that accept input by touch of fingers or a <a href="/facts/Stylus/71P3StMj">stylus</a>. Used in a growing amount of <a href="/facts/Mobile_device/cNS1Rhvg">mobile devices</a> and many types of <a href="/facts/Point_of_sale/DwUHVn2v">point of sale</a>, industrial processes and machines, self-service machines, etc.</li> <li><i><a href="/facts/Touch_user_interface/kvoawM0g">Touch user interface</a></i> are graphical user interfaces using a <a href="/facts/Touchpad/5BptytYa">touchpad</a> or touchscreen display as a combined input and output device. They supplement or replace other forms of output with <a href="/facts/Haptic_communication/IkXD4hHr">haptic</a> feedback methods. Used in computerized <a href="/facts/Simulator/Q4QJV1oI">simulators</a>, etc.</li> <li><i><a href="/facts/Voice_user_interface/jkdI6nGy">Voice user interfaces</a></i>, which accept input and provide output by generating voice prompts. The user input is made by pressing keys or buttons, or responding verbally to the interface.</li> <li><i><a href="/facts/Web_application/BLkF3BIN">Web-based user interfaces</a></i> or <i>web user interfaces</i> (WUI) that accept input and provide output by generating <a href="/facts/Web_page/5JK7xQLe">web pages</a> viewed by the user using a <a href="/facts/Web_browser/2pfyymLs">web browser</a> program.</li> <li><i>Zero-input interfaces</i> get inputs from a set of sensors instead of querying the user with input dialogs.<a class="footnote-ref" id="fnref:42" href="#fn:42"><sup>42</sup></a></li> <li><i><a href="/facts/Zooming_user_interface/xWFvDtYh">Zooming user interfaces</a></i> are graphical user interfaces in which information objects are represented at different levels of scale and detail, and where the user can change the scale of the viewed area in order to show more detail.</li></ol> <h2 id="gallery">Gallery</h2> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Adaptive_user_interfaces/e7m1EybY">Adaptive user interfaces</a></li> <li><a href="/facts/Brain%E2%80%93computer_interface/wdXWqFVr">Brain–computer interface</a></li> <li><a href="/facts/Computer_user_satisfaction/a7jKU9NJ">Computer user satisfaction</a></li> <li><a href="/facts/Direct_voice_input/PYl1y7es">Direct voice input</a></li> <li><a href="/facts/Distinguishable_interfaces/1rYns3TI">Distinguishable interfaces</a></li> <li><a href="/facts/Ergonomics/prAcGtDW">Ergonomics</a> and <a href="/facts/Human_factors/prAcGtDW">human factors</a> – the study of designing objects to be better adapted to the shape of the human body</li> <li><a href="/facts/Flat_design/Jc2SJFaq">Flat design</a></li> <li><a href="/facts/History_of_the_GUI/K2NXGuGh">History of the GUI</a></li> <li><a href="/facts/Icon_design/kv2NvgxJ">Icon design</a></li> <li><a href="/facts/Information_architecture/xhAHVzA7">Information architecture</a> – organizing, naming, and labelling information structures</li> <li><a href="/facts/Information_visualization/DSHteV85">Information visualization</a> – the use of sensory representations of abstract data to reinforce cognition</li> <li><a href="/facts/Interaction_design/6aKgJFNW">Interaction design</a></li> <li><a href="/facts/Interaction_technique/HICbePyA">Interaction technique</a></li> <li><a href="/facts/Kinetic_user_interface/jly3YdnY">Kinetic user interface</a></li> <li><a href="/facts/Knowledge_visualization/xVfxo6FJ">Knowledge visualization</a> – the use of visual representations to transfer knowledge</li> <li><a href="/facts/Multiple_frames_interface/sfJgM9kS">Multiple frames interface</a></li> <li><a href="/facts/Natural_user_interface/0xVkq916">Natural user interfaces</a></li> <li><a href="/facts/Organic_user_interface/ev36xfr2">Organic user interface</a></li> <li><a href="/facts/Post-WIMP/4UYPWXNK">Post-WIMP</a></li> <li><a href="/facts/Tangible_user_interface/PmbEvkEb">Tangible user interface</a></li> <li><a href="/facts/Unified_Code_for_Units_of_Measure/qF8tqubR">Unified Code for Units of Measure</a></li> <li><a href="/facts/Usability/zuAnqu9Q">Usability links</a></li> <li><a href="/facts/User_assistance/bNC7dIG2">User assistance</a></li> <li><a href="/facts/User_experience/0GF3UETu">User experience</a></li> <li><a href="/facts/User_experience_design/wYjvMsf8">User experience design</a></li> <li><a href="/facts/User_interface_design/bHpLP1ae">User interface design</a></li> <li><a href="/facts/User_interface_specification/Cs32fx7H">User interface specification</a></li> <li><a href="/facts/Useware/s1yrgLB9">Useware</a></li> <li><a href="/facts/Virtual_artifact/2YvneGna">Virtual artifact</a></li> <li><a href="/facts/Virtual_user_interface/e9sPEWVD">Virtual user interface</a></li></ul> <h2 id="external-links">External links</h2> Look up <i>user interface</i> in Wiktionary, the free dictionary. Wikimedia Commons has media related to User interfaces. <ul><li><a href="https://www.interaction-design.org/literature/conference_series/overview">Conference series</a> – covering a wide area of user interface publications</li> <li><a href="http://www.catb.org/~esr/writings/taouu/html/ch02.html">Chapter 2. History: A brief history of user interfaces</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"Eurotherm Parker SSD Link Hardware L5392 | Automation Industrial". l5392.com. Retrieved 11 January 2024. <a href="https://l5392.com/blog" target="_blank">https://l5392.com/blog</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Cohen, Philip R. (1992). "The role of natural language in a multimodal interface". Proceedings of the 5th annual ACM symposium on User interface software and technology - UIST '92. pp. 143–149. doi:10.1145/142621.142641. ISBN 0897915496. S2CID 9010570. <a href="0897915496" target="_blank">0897915496</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>"The User Experience of Libraries: Serving The Common Good User Experience Magazine". uxpamagazine.org. 7 May 2017. Retrieved 23 March 2022. <a href="https://uxpamagazine.org/the-user-experience-of-libraries/" target="_blank">https://uxpamagazine.org/the-user-experience-of-libraries/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Griffin, Ben; Baston, Laurel. "Interfaces" (Presentation): 5. Archived from the original on 14 July 2014. Retrieved 7 June 2014. The user interface of a mechanical system, a vehicle or an industrial installation is sometimes referred to as the human–machine interface (HMI). {{cite journal}}: Cite journal requires |journal= (help) <a href="http://peace.saumag.edu/faculty/kardas/Courses/CS/Interfaces2007_files/Interfaces2007.ppt" target="_blank">http://peace.saumag.edu/faculty/kardas/Courses/CS/Interfaces2007_files/Interfaces2007.ppt</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>"User Interface Design and Ergonomics" (PDF). Course Cit 811. NATIONAL OPEN UNIVERSITY OF NIGERIA: SCHOOL OF SCIENCE AND TECHNOLOGY: 19. Archived (PDF) from the original on 14 July 2014. Retrieved 7 June 2014. In practice, the abbreviation MMI is still frequently used although some may claim that MMI stands for something different now. <a href="http://www.nou.edu.ng/NOUN_OCL/pdf/SST/CIT%20811.pdf" target="_blank">http://www.nou.edu.ng/NOUN_OCL/pdf/SST/CIT%20811.pdf</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"User Interface Design and Ergonomics" (PDF). Course Cit 811. NATIONAL OPEN UNIVERSITY OF NIGERIA: SCHOOL OF SCIENCE AND TECHNOLOGY: 19. Archived (PDF) from the original on 14 July 2014. Retrieved 7 June 2014. In practice, the abbreviation MMI is still frequently used although some may claim that MMI stands for something different now. <a href="http://www.nou.edu.ng/NOUN_OCL/pdf/SST/CIT%20811.pdf" target="_blank">http://www.nou.edu.ng/NOUN_OCL/pdf/SST/CIT%20811.pdf</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"User Interface Design and Ergonomics" (PDF). Course Cit 811. NATIONAL OPEN UNIVERSITY OF NIGERIA: SCHOOL OF SCIENCE AND TECHNOLOGY: 19. Archived (PDF) from the original on 14 July 2014. Retrieved 7 June 2014. In practice, the abbreviation MMI is still frequently used although some may claim that MMI stands for something different now. <a href="http://www.nou.edu.ng/NOUN_OCL/pdf/SST/CIT%20811.pdf" target="_blank">http://www.nou.edu.ng/NOUN_OCL/pdf/SST/CIT%20811.pdf</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"Introduction Section". Recent advances in business administration. [S.l.]: Wseas. 2010. p. 190. ISBN 978-960-474-161-8. Other terms used are operator interface console (OIC) and operator interface terminal (OIT) <a href="978-960-474-161-8" target="_blank">978-960-474-161-8</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>"User Interface Design and Ergonomics" (PDF). Course Cit 811. NATIONAL OPEN UNIVERSITY OF NIGERIA: SCHOOL OF SCIENCE AND TECHNOLOGY: 19. Archived (PDF) from the original on 14 July 2014. Retrieved 7 June 2014. In practice, the abbreviation MMI is still frequently used although some may claim that MMI stands for something different now. <a href="http://www.nou.edu.ng/NOUN_OCL/pdf/SST/CIT%20811.pdf" target="_blank">http://www.nou.edu.ng/NOUN_OCL/pdf/SST/CIT%20811.pdf</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>Cipriani, Christian; Segil, Jacob; Birdwell, Jay; Weir, Richard (2014). "Dexterous control of a prosthetic hand using fine-wire intramuscular electrodes in targeted extrinsic muscles". IEEE Transactions on Neural Systems and Rehabilitation Engineering. 22 (4): 828–36. doi:10.1109/TNSRE.2014.2301234. ISSN 1534-4320. PMC 4501393. PMID 24760929. Neural co-activations are present that in turn generate significant EMG levels and hence unintended movements in the case of the present human machine interface (HMI). <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4501393" target="_blank">https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4501393</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>Citi, Luca (2009). "Development of a neural interface for the control of a robotic hand" (PDF). Scuola Superiore Sant'Anna, Pisa, Italy: IMT Institute for Advanced Studies Lucca: 5. Retrieved 7 June 2014. {{cite journal}}: Cite journal requires |journal= (help)[permanent dead link] <a href="https://7c4745ab-a-cdf32725-s-sites.googlegroups.com/a/neurostat.mit.edu/lciti/publications_files/LCitiPhD.pdf?attachauth=ANoY7cpwRib4-7KUnST5NrulgpbLiT3r10hOeyap9QXEgv64E1VioXR7n1pQYsNBNMZggwnI2V4KbZLgxVeKLcOgxz4XfJFAkqvddyQUnGqn4Mm5iLq9vDR02cHmYi6ULrK8IxWK150SirIt9acjMFcDon0dbnRwgYicc-2GeKZZCqtflZc4ZhEBORg8AzWE31XDAgoFFAfNtUxTcNR8IcJlsM7NYCGxY4M3Vn8WY6bsO1MEuyYIjmU%3D&attredirects=0" target="_blank">https://7c4745ab-a-cdf32725-s-sites.googlegroups.com/a/neurostat.mit.edu/lciti/publications_files/LCitiPhD.pdf?attachauth=ANoY7cpwRib4-7KUnST5NrulgpbLiT3r10hOeyap9QXEgv64E1VioXR7n1pQYsNBNMZggwnI2V4KbZLgxVeKLcOgxz4XfJFAkqvddyQUnGqn4Mm5iLq9vDR02cHmYi6ULrK8IxWK150SirIt9acjMFcDon0dbnRwgYicc-2GeKZZCqtflZc4ZhEBORg8AzWE31XDAgoFFAfNtUxTcNR8IcJlsM7NYCGxY4M3Vn8WY6bsO1MEuyYIjmU%3D&attredirects=0</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>Jordan, Joel. "Gaze Direction Analysis for the Investigation of Presence in Immersive Virtual Environments" (Thesis submitted for the degree of Doctor of Philosophy). University of London: Department of Computer Science: 5. Archived (PDF) from the original on 14 July 2014. Retrieved 7 June 2014. The aim of this thesis is to investigate the idea that the direction of gaze may be used as a device to detect a sense-of-presence in Immersive Virtual Environments (IVE) in some contexts. {{cite journal}}: Cite journal requires |journal= (help) <a href="http://www0.cs.ucl.ac.uk/staff/j.jordan/thesis-jj-2011.pdf" target="_blank">http://www0.cs.ucl.ac.uk/staff/j.jordan/thesis-jj-2011.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>Ravi (August 2009). "Introduction of HMI". Archived from the original on 14 July 2014. Retrieved 7 June 2014. In some circumstance computers might observe the user, and react according to their actions without specific commands. A means of tracking parts of the body is required, and sensors noting the position of the head, direction of gaze and so on have been used experimentally. This is particularly relevant to immersive interfaces. <a href="http://ravi-softwares.blogspot.com/2009/08/introduction-of-hmi.html" target="_blank">http://ravi-softwares.blogspot.com/2009/08/introduction-of-hmi.html</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>"HMI Guide". Archived from the original on 20 June 2014. <a href="http://www.anaheimautomation.com/manuals/forms/hmi-guide.php#sthash.2McqS5xo.dpbs" target="_blank">http://www.anaheimautomation.com/manuals/forms/hmi-guide.php#sthash.2McqS5xo.dpbs</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>Richard, Stéphane. "Text User Interface Development Series Part One – T.U.I. Basics". Archived from the original on 16 November 2014. Retrieved 13 June 2014. <a href="http://www.petesqbsite.com/sections/express/issue21/tuiseriespart1.htm" target="_blank">http://www.petesqbsite.com/sections/express/issue21/tuiseriespart1.htm</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> <li id="fn:16"><p>McCown, Frank. "History of the Graphical User Interface (GUI)". Harding University. Archived from the original on 8 November 2014. {{cite journal}}: Cite journal requires |journal= (help) <a href="https://www.harding.edu/fmccown/gui/history-gui.pptx" target="_blank">https://www.harding.edu/fmccown/gui/history-gui.pptx</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></p></li> <li id="fn:17"><p>McCown, Frank. "History of the Graphical User Interface (GUI)". Harding University. Archived from the original on 8 November 2014. {{cite journal}}: Cite journal requires |journal= (help) <a href="https://www.harding.edu/fmccown/gui/history-gui.pptx" target="_blank">https://www.harding.edu/fmccown/gui/history-gui.pptx</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></p></li> <li id="fn:18"><p>McCown, Frank. "History of the Graphical User Interface (GUI)". Harding University. Archived from the original on 8 November 2014. {{cite journal}}: Cite journal requires |journal= (help) <a href="https://www.harding.edu/fmccown/gui/history-gui.pptx" target="_blank">https://www.harding.edu/fmccown/gui/history-gui.pptx</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></p></li> <li id="fn:19"><p>"The Xerox PARC Visit". web.stanford.edu. Retrieved 8 February 2019. <a href="https://web.stanford.edu/dept/SUL/sites/mac/parc.html" target="_blank">https://web.stanford.edu/dept/SUL/sites/mac/parc.html</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></p></li> <li id="fn:20"><p>"apple-history.com / Graphical User Interface (GUI)". apple-history.com. Retrieved 8 February 2019. <a href="https://apple-history.com/gui" target="_blank">https://apple-history.com/gui</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></p></li> <li id="fn:21"><p>Raymond, Eric Steven (2003). "11". The Art of Unix Programming. Thyrsus Enterprises. Archived from the original on 20 October 2014. Retrieved 13 June 2014. <a href="http://homepage.cs.uri.edu/~thenry/resources/unix_art/ch11s03.html" target="_blank">http://homepage.cs.uri.edu/~thenry/resources/unix_art/ch11s03.html</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></p></li> <li id="fn:22"><p>C. A. D'H Gough; R. Green; M. Billinghurst. "Accounting for User Familiarity in User Interfaces" (PDF). Retrieved 13 June 2014. {{cite journal}}: Cite journal requires |journal= (help) <a href="https://www.researchgate.net/publication/220998465" target="_blank">https://www.researchgate.net/publication/220998465</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></p></li> <li id="fn:23"><p>Sweet, David (October 2001). "9 – Constructing A Responsive User Interface". KDE 2.0 Development. Sams Publishing. Archived from the original on 23 September 2013. Retrieved 13 June 2014. <a href="http://openbooks.sourceforge.net/books/kde20devel/ch09.html" target="_blank">http://openbooks.sourceforge.net/books/kde20devel/ch09.html</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></p></li> <li id="fn:24"><p>John W. Satzinger; Lorne Olfman (March 1998). "User interface consistency across end-user applications: the effects on mental models". Journal of Management Information Systems. Managing virtual workplaces and teleworking with information technology. 14 (4). Armonk, NY: 167–193. doi:10.1080/07421222.1998.11518190. <a href="http://dl.acm.org/citation.cfm?id=1189510" target="_blank">http://dl.acm.org/citation.cfm?id=1189510</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></p></li> <li id="fn:25"><p>Raskin, Jef (2000). The human interface : new directions for designing interactive systems (1. printing. ed.). Reading, Mass. [u.a.]: Addison Wesley. ISBN 0-201-37937-6. <a href="0-201-37937-6" target="_blank">0-201-37937-6</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></p></li> <li id="fn:26"><p>Raskin, Jef (2000). The human interface : new directions for designing interactive systems (1. printing. ed.). Reading, Mass. [u.a.]: Addison Wesley. ISBN 0-201-37937-6. <a href="0-201-37937-6" target="_blank">0-201-37937-6</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></p></li> <li id="fn:27"><p>Udell, John (9 May 2003). "Interfaces are habit-forming". Infoworld. Archived from the original on 4 April 2017. Retrieved 3 April 2017. <a href="http://www.infoworld.com/article/2681144/application-development/interfaces-are-habit-forming.amp.html" target="_blank">http://www.infoworld.com/article/2681144/application-development/interfaces-are-habit-forming.amp.html</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></p></li> <li id="fn:28"><p>Wesolko, Dane (27 October 2016). "Peter Morville's User Experience Honeycomb". Medium. Retrieved 19 November 2019. <a href="https://medium.com/@danewesolko/peter-morvilles-user-experience-honeycomb-904c383b6886" target="_blank">https://medium.com/@danewesolko/peter-morvilles-user-experience-honeycomb-904c383b6886</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></p></li> <li id="fn:29"><p>Wesolko, Dane (27 October 2016). "Peter Morville's User Experience Honeycomb". Medium. Retrieved 19 November 2019. <a href="https://medium.com/@danewesolko/peter-morvilles-user-experience-honeycomb-904c383b6886" target="_blank">https://medium.com/@danewesolko/peter-morvilles-user-experience-honeycomb-904c383b6886</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></p></li> <li id="fn:30"><p>"User Interface & User Experience Design | Oryzo | Small Business UI/UX". Oryzo. Retrieved 19 November 2019. <a href="https://oryzo.com/user-interface-design/" target="_blank">https://oryzo.com/user-interface-design/</a> <a href="#fnref:30" class="footnote-back-ref">↩</a></p></li> <li id="fn:31"><p>"User Interface & User Experience Design | Oryzo | Small Business UI/UX". Oryzo. Retrieved 19 November 2019. <a href="https://oryzo.com/user-interface-design/" target="_blank">https://oryzo.com/user-interface-design/</a> <a href="#fnref:31" class="footnote-back-ref">↩</a></p></li> <li id="fn:32"><p>"User Interface & User Experience Design | Oryzo | Small Business UI/UX". Oryzo. Retrieved 19 November 2019. <a href="https://oryzo.com/user-interface-design/" target="_blank">https://oryzo.com/user-interface-design/</a> <a href="#fnref:32" class="footnote-back-ref">↩</a></p></li> <li id="fn:33"><p>"User Interface & User Experience Design | Oryzo | Small Business UI/UX". Oryzo. Retrieved 19 November 2019. <a href="https://oryzo.com/user-interface-design/" target="_blank">https://oryzo.com/user-interface-design/</a> <a href="#fnref:33" class="footnote-back-ref">↩</a></p></li> <li id="fn:34"><p>"User Interface & User Experience Design | Oryzo | Small Business UI/UX". Oryzo. Retrieved 19 November 2019. <a href="https://oryzo.com/user-interface-design/" target="_blank">https://oryzo.com/user-interface-design/</a> <a href="#fnref:34" class="footnote-back-ref">↩</a></p></li> <li id="fn:35"><p>"User Interface & User Experience Design | Oryzo | Small Business UI/UX". Oryzo. Retrieved 19 November 2019. <a href="https://oryzo.com/user-interface-design/" target="_blank">https://oryzo.com/user-interface-design/</a> <a href="#fnref:35" class="footnote-back-ref">↩</a></p></li> <li id="fn:36"><p>"User Interface & User Experience Design | Oryzo | Small Business UI/UX". Oryzo. Retrieved 19 November 2019. <a href="https://oryzo.com/user-interface-design/" target="_blank">https://oryzo.com/user-interface-design/</a> <a href="#fnref:36" class="footnote-back-ref">↩</a></p></li> <li id="fn:37"><p>Errett, Joshua. "As app fatigue sets in, Toronto engineers move on to chatbots". CBC. CBC/Radio-Canada. Archived from the original on 22 June 2016. Retrieved 4 July 2016. <a href="http://www.cbc.ca/news/canada/toronto/toronto-chatbots-1.3581791" target="_blank">http://www.cbc.ca/news/canada/toronto/toronto-chatbots-1.3581791</a> <a href="#fnref:37" class="footnote-back-ref">↩</a></p></li> <li id="fn:38"><p>Martinez, Wendy L. (23 February 2011). "Graphical user interfaces: Graphical user interfaces". Wiley Interdisciplinary Reviews: Computational Statistics. 3 (2): 119–133. doi:10.1002/wics.150. S2CID 60467930. <a href="https://onlinelibrary.wiley.com/doi/10.1002/wics.150" target="_blank">https://onlinelibrary.wiley.com/doi/10.1002/wics.150</a> <a href="#fnref:38" class="footnote-back-ref">↩</a></p></li> <li id="fn:39"><p>Lamb, Gordana (2001). "Improve Your UI Design Process with Object-Oriented Techniques". Visual Basic Developer magazine. Archived from the original on 14 August 2013. Table 1. Differences between the traditional application-oriented and object-oriented approaches to UI design. <a href="https://web.archive.org/web/20130814153652/http://msdn.microsoft.com/en-us/library/aa227601(v=vs.60).aspx" target="_blank">https://web.archive.org/web/20130814153652/http://msdn.microsoft.com/en-us/library/aa227601(v=vs.60).aspx</a> <a href="#fnref:39" class="footnote-back-ref">↩</a></p></li> <li id="fn:40"><p>appleinsider.com Archived 2009-06-19 at the Wayback Machine <a href="http://www.appleinsider.com/articles/09/06/18/apple_exploring_motion_tracking_mac_os_x_user_interface.html" target="_blank">http://www.appleinsider.com/articles/09/06/18/apple_exploring_motion_tracking_mac_os_x_user_interface.html</a> <a href="#fnref:40" class="footnote-back-ref">↩</a></p></li> <li id="fn:41"><p>Jakob Nielsen (April 1993). "Noncommand User Interfaces". Communications of the ACM. 36 (4). ACM Press: 83–99. doi:10.1145/255950.153582. S2CID 7684922. Archived from the original on 10 November 2006. <a href="/wiki/Jakob_Nielsen_(usability_consultant)" target="_blank">/wiki/Jakob_Nielsen_(usability_consultant)</a> <a href="#fnref:41" class="footnote-back-ref">↩</a></p></li> <li id="fn:42"><p>Sharon, Taly, Henry Lieberman, and Ted Selker. "A zero-input interface for leveraging group experience in web browsing Archived 2017-09-08 at the Wayback Machine." Proceedings of the 8th international conference on Intelligent user interfaces. ACM, 2003. <a href="https://www.researchgate.net/profile/Ted_Selker/publication/221607708_A_zero-input_interface_for_leveraging_group_experience_in_Web_browsing/links/0912f50876bda91a5b000000/A-zero-input-interface-for-leveraging-group-experience-in-Web-browsing.pdf" target="_blank">https://www.researchgate.net/profile/Ted_Selker/publication/221607708_A_zero-input_interface_for_leveraging_group_experience_in_Web_browsing/links/0912f50876bda91a5b000000/A-zero-input-interface-for-leveraging-group-experience-in-Web-browsing.pdf</a> <a href="#fnref:42" class="footnote-back-ref">↩</a></p></li> </ol>