9 Basic principles for Easy-to-use user UI interface design

There is no great mystery to design a really great user interface, so keep it simple and easy to use. ' Keep simple and easy to use ' means not to distract the user. A good UI allows users to achieve goals, the corresponding training and maintenance costs will be reduced, while achieving more happy, satisfied and efficient users.

When you face a brand new interface design, don't forget the most basic principles above.

The following is a detailed introduction to the 9 Principles of Interface design: (there were 10 but ten cards that could be reduced to 9)

1. Know your users "focus on the User: If you are looking for a competitor or a choice between users, the answer is always the latter." The job always starts with the user first. "--jeff Bezos

Understand the user, because the user's goal is your goal. Try to restate the user, understand their skill level and experience, and what they need. Find out what kind of interface the user prefers, and see how they operate in the interface. Don't be obsessed with updating design trends or adding new features. The first task is to focus on your users so that you can create an interface that allows users to achieve goals.

2. Pay attention to the model in the System software users most of the time consumed in the interface operation (data entry, data modification, data lookup, etc.), this and browse-oriented site Class page user operation is completely different. We do not need to gild the lily, users want to see in the newly created interface, the existing, similar functions, or follow the basic operating methods of the software interface. So taking advantage of the established UI model will make users feel as familiar as they are at home.

3. Maintain consistency "the more users expect to be properly validated, the more they feel that the system is in their control and that they are more likely to love it (the system)." "--jakob Nielson

Users need consistency. The consistency of the operation and the consistency of the page style. Users need to know that once they learn to do something, the next operation is equally feasible. Language, layout and design are several interface elements that require consistency. A consistent interface gives users a better understanding of how to operate, thereby improving efficiency.

4. The use of visual hierarchy "designers to find unity in the chaos, through the organization to manipulate the text, pictures, so as to clearly communicate the design intent." "--jeffery Veen

Design, let the user focus on the most important place. The size, color, and position of each element provide a common path for understanding the interface. A clear hierarchical relationship will play an important role in reducing the complexity of the appearance and operations.

5. Provide feedback interface to always maintain communication with users, regardless of whether their behavior is right or wrong. prompt the user's behavior at any time: state change, error or exception information. Visual cues or simple text reminders can tell users whether their actions can achieve the desired results.

6. Interface to maintain tolerance no matter how clear the design interface, users will make mistakes. so when designing an interface, you should consider how to allow and tolerate user errors. For example, to provide users with the means to undo the behavior and access, to the different input data as much as possible (no one would like to just fill in the wrong birthday format and start again). In addition, if the user's behavior causes an error, use the information at the right time to show what behavior is wrong and make sure that he or she knows how to prevent this error from happening again.

7. Encourage users to inform the User (pop-up dialog box, etc.) as soon as the user completes the key operation.

It is worth noting that splitting a complex process task into several simple steps will be more complex and distracting. So no matter how complex and lengthy the task is executing, it is necessary to maintain the continuity of the process in the interface.

8. Integrate into the user's language "If you want to think twice about each pixel, every icon, every font, then you need to consider each word as well." "--getting Real

All the interfaces have more or less text on them. Make the manuscript as colloquial as possible, reduce the piling up of colorful rhetoric. Provide clear and concise labels for behavior and keep a simple text narrative. Users will appreciate this, as they are no longer dictated by other people's words-they are speaking as friends and even talking to themselves.

9. Keep it simple "creating complex interfaces is easy, but simplifying complex interfaces is difficult"--per Almqvist

Is the so-called: big Sound, elephants invisible. Excellent system-Class software pages, you don't see flashy UI decorations, and you don't see those design elements that you don't use. In other words, the elements that must appear are concise and meaningful. So when you think about whether you want to add a new feature or new element to the interface, think again: "Does the user or interface really need this?" "Why do users want to be here when this small dynamic icon?" ”。 Do you add these elements simply because of your own preferences and the beauty of the page? The system-class interface made by a good UI engineer is not gorgeous, and there are no elements in the page that distract users from the user's actions. It should even be achieved when the user is using the system to fully notice the page and the operation of complex problems, everything should be logical.

The ultimate goal of the system-class user interface design is to design the software as it should be.

From: Kyle Sollenberger

Finishing: Ten Cards