Http://www.blueidea.com/design/doc/2010/7535.asp
Translation: This article was summarized by availability master Jakob Nielsen 10 years ago and is still available today. Through this time span, we can conclude that the availability topic is not the product of a certain era, and some research experience is still worth learning from today. The seemingly short 10 revelations include a large amount of project experience, which will continue to guide designers to create high-quality products under the impetus of new Internet technologies.
Don't take it as a tutorial. It is just the essence of thought. In a variety of projects, you may encounter strange situations, and work with people of various roles to accomplish the goal. Only when consensus is reached can efficiency be improved. These 10 inspirations are the bond.
In fact, this is 10 basic guidelines for interface design. They are called "inspiration" because they come from practical experience rather than boring theoretical knowledge.
- Visibility of system status
Users should always be informed of what is happening and feedback should be given at the right time.
- Matching between systems and the real world
Let's talk about the language that the user can understand, regardless of words, phrases, or concepts, and leave the terms to the machine for reading. Following the principles of the real world, the information can be displayed naturally and logically.
- User Control and freedom of action
It is common for users to make mistakes in feature selection. Therefore, they need to provide an "Emergency Exit" for them, so they do not have to leave the room through additional conversations. Provides the Undo and redo functions.
- Consistency and standards
Do not let users worry about whether different texts, conditions, and actions represent the same thing. Follow the platform idea.
- Error Prevention
A design that can prevent mistakes at the first time is always better than a bunch of beautiful error prompts. Conditions that can lead to mistakes should be eliminated before the user acts and the user should be reminded to confirm the operation if necessary. Prevent problems before they occur.
- The system identifies the user rather than making the user remember it.
Minimize users' memory costs for goals, behaviors, and visible options. Do not let them remember the information from which segment to which segment. At the same time, the use instructions of the system should be visible and provide appropriate prompt information when necessary.
- Flexibility and Efficiency
Shortcut Keys -- do not have to explain to novice users -- but they can improve the efficiency of expert-level users. Such interactions take into account experienced and inexperienced users. At the same time, users can customize frequent actions)
- Simple Design Aesthetics
The dialog should not contain irrelevant or unnecessary information. Each additional information unit weakens the relative visibility of the original information unit to a certain extent.
- Helps users identify, diagnose, and recover from errors
The error message should be in a simple language (do not use code or serial numbers, which can only be understood by engineers), clarify the problem in a targeted manner, and provide constructive solutions.
- Help documentation
Even if a system is great and can be used without relying on help, it may still need help documentation. Any information such as the user's key tasks should be easily identified and specific action steps provided.
