Principle of designing effective interface Tognozzi Interface design principle
- Prediction: The system should be able to predict the next step for the user.
- Communication: The interface should be able to communicate the status of any activity initiated by the user. The communication can be obvious, or it can be implied. The interface should also convey the user's State in the content hierarchy.
- Consistency: Throughout the system, the use of navigation controls, menus, icons, and aesthetics (for example, color, shape, and layout) should be consistent. For example, if the underlined blue text represents a navigation link, the content should not contain blue underlined text that does not represent a link. Finally, each feature of the interface should respond in a manner consistent with the expectations of the user.
- Autonomy: The interface should assist the user in moving through the system, but the assisted approach should stick with the navigation habits that have been established for the application. For example, navigation to the security part of the system should be controlled by the user ID and password, and should not provide a navigational mechanism that would allow the user to circumvent these controls.
- Efficiency: The design and interface of the system should optimize the efficiency of the user, and if this goal is to be achieved, it is also the key to achieve close and continuous cooperation, communication and collusion between engineers and HMI designers.
- Flexibility: The interface should be flexible enough to enable some users to complete tasks directly, or to allow other users to browse in a more casual way. In each case, the interface should be able to make the user aware of where they are and provide the user with undo errors and functions returned from the chosen navigation path.
- Focus: The interface (and the content represented by the interface) should remain focused on the user task at hand.
- Fitzer rule: The time to reach the target is a function of the distance to the target and the size of the target. If a user task defines an option or standardizes the order of inputs (options have many different permutations), then the first selection (for example, the mouse selection) should be physically close to the next selection.
- User interface objects: A large number of available HMI object (and type) libraries have been developed for WebApp. Use these object libraries. Some end users can "see, hear, touch, or otherwise perceive" [TOG01] Any interface object can be obtained from a large number of object libraries.
- Shorten the delay: the system should not allow the user to wait for some internal operations to complete (for example, to download a complex graphical image), but should use multitasking so that the user can continue to work, it looks as if the previous operation has been completed. In addition to reducing time, if a delay event occurs, you must inform the user so that the user is aware of what is happening, including: 1) If the system does not respond immediately after the option is selected, you should provide sound feedback (for example, click or ringtone) ; 2) A dynamic clock or progress bar is displayed to indicate that the process is in progress; 3) When a lengthy process occurs, a number of recreational activities are provided (for example, an animated or textual presentation).
- Easy to learn: A WebApp interface should be designed to be the minimum learning time. And once you've learned it, when you visit this webapp again, the time you need to learn again is minimal. In general, the interface should emphasize simple, intuitive design, the content and function classification organization, so for the user intuitive.
- Metaphor: As long as the metaphor is suitable for the application and the user, the interface with interactive metaphor is more easy to learn and use. Metaphors should be user-familiar images and concepts, but not necessarily the exact reproduction of the real world. For example, an e-commerce Web site that automates bill payments for financial institutions, uses checkbook metaphors to help users specify billing payments and schedule billing activities.
- Maintain the integrity of work products: work products (for example, a form that a user fills out, a user-specific list) must be automatically saved so that the information is not lost when an error occurs.
- Legibility: All the information displayed on the interface should be readable, both for the elderly and for the young. The interface designer should focus on selecting easy-to-read fonts, font sizes, and background colors that can enhance the contrast effect.
- Tracking status: When appropriate, the state of user interaction should be tracked and saved, allowing the user to launch the system and return to the place they launched later when returning to the system. In general, cookies can be designed to store state information. However, cookies are a controversial technology, and other design options may be more appropriate for some users.
- Visual navigation: A well-designed WebApp interface provides "an illusion that the user is not moving in the same place and the work is brought before them". When you use this approach, navigation is no longer a concern for the user. Instead, the user retrieves the content object and selects the features that are displayed and executed through the interface.
- These design principles should be applied when creating a preliminary interface design and reviewing the design
Nielsen and Wagner Interface design principles
- The speed of reading a computer screen is about 25% slower than reading a book. Therefore, do not force the user to read a large amount of text information, especially when the content of the text is to explain the webapp operation or auxiliary navigation.
- Avoid the "under construction" mark – users come up with expectations, but seeing such an unnecessary link is certainly disappointing or frustrating.
- Users do not like to use scrolling operations. Important information should be placed within the range that the General browser window can display.
- The design of the navigation menu and title bar must be consistent and should appear on all pages available to the user. The design should not rely on browser functionality to assist navigation (for example, to return arrows).
- Aesthetic effects should never replace functionality. For example, a simple button might be a better navigation option than a nice but ambiguous image or icon.
- Even for some temporary users, the navigation options should be obvious. You should not let users have to search full screen to decide how to link to other content or services.
- A good interface design can improve the user's understanding of the content or service provided by the website, it does not have to have flashing animation, but it should be reasonable structure and sound effect.
- The user interface is a window that accesses WebApp content and functionality. In many cases, the interface shapes the user's perception of the quality of the system. If the "window" is dirty, uneven or damaged. Then the user may reject powerful features and content. In fact, a poorly designed interface could result in a failure of an application with good design and robust implementations.
A number of principles and guidance rules can help designers create effective user interfaces. The following rules can be summarized as follows: 1) Placing the user in control, 2) making the interface easy to interact with, 3) maintaining the artistry and consistency of the interface. An organized design process should be conducted to achieve an interface that adheres to these rules.
Reference: Research methods for Web engineering practitioners
Fifth time Assignment
