10 basic guidelines for user interface design

This is the basic principle of 10 user interface design, they are well-known by the Jakob Nielsen and Rolf Molich design rule of thumb, is the most common user interface usability design guidance. As a web designer, it is believed that these rules will lead you to a very positive design.

1. Visibility of System State

The system should always use appropriate feedback at the right time to tell the user what is happening or what will happen. For example, use the progress bar to display page load progress or file upload progress.

2. Combined with the real world

The system should use language, words, terminology, and concepts that are familiar to the user, rather than the language of the system. Systems should follow the habits of the real world and let the information be expressed in natural and logical rules.

3. User Control and freedom

Users may often choose the wrong system function, so the system should have a clear "emergency exit", so that users can leave the unwanted state as soon as possible without the need for additional dialogue. The system should also support cancellation and redo actions.

4. Standards and consistency

Users may not want to know whether two words, situations, or actions represent the same thing. Follow the industry's habits.

5. Error prevention

The first cautious design to prevent errors is better than displaying error messages, eliminating or checking for error-prone states, and then providing a confirmation choice before the user submits the action.

6. Recognizing rather than remembering

With obvious objects, actions, and options to reduce the user's memory burden, the user does not need to memorize information for his use. The system's use instructions should be visible or easy to obtain, when it is primarily appropriate.

7. Flexibility and efficiency of use

The system needs to cater to experienced and inexperienced users, and some accelerators that are not seen by primary users can speed up communication between advanced users and systems. The system should also allow users to adjust their common actions/actions.

8. Aesthetics and minimalist design

The dialogue does not include irrelevant or uncommon information. Any additional information in the conversation conflicts with related information and reduces its visibility.

9. Help the user to recognize, confirm and recover from the error

The error message should be expressed in plain language (rather than code), clearly pointing out the problem and giving constructive advice.

10. Help and documentation

Although it would be even better if the system was used without documentation, providing help and documentation was still necessary. Any such problem should be easy to find, focus on with user tasks, list specific implementation steps, and not too long (cumbersome).

We often see some of the principles of user experience and user interface design or basic principles. I think, as the domestic design industry, we learn foreign things are not enough, although the domestic site also has a great work, but we have no matter from the theory or time there is a big gap. Learning, and beyond. --God Fly