GUI Design taboos

This article lists the design principles and taboos that Jeff Johnson mentioned in his book GUI Design prohibitions clearly target web design and the author believes that it has reference significance for web design. When designing a web project, try to refer to the basic principles to avoid design taboos and make the WEB Project Gui A level.

Basic Principles:

1. Focus on users and their tasks, rather than technology

2. Consider the function first, and then represent

3. From the user's perspective, use the user's words to describe the problem

4. Do not expose implementation details to users

5. Simplify common user tasks and avoid extra problems.

6. Maintain consistency and guide the user's usage habits

7. Keep display inertia and transmit information, not just data

8. The design should meet the response requirements

Taboo:

1. The same page contains links or buttons for repeated Functions

2. Use the check box as a single button

3. Select one more setting without an initial value

4. Use the check box in non-On/Off settings

5. Display read-only data in a text box

6. The interval between single-choice buttons is too large.

7. The alignment of attribute tags is inconsistent.

8. The currently invalid controls are not fully dimmed.

9. Display error messages that are meaningless to users

10. Different types of page windows display the same title

11. The title of the window is inconsistent with the called command.

12. The user is required to enter a random number.

13. Similar functions have inconsistent user operation Interfaces

14. The cancel button cannot be canceled.

15. The website structure reflects the company's structure or website upgrade history

16. The return button cannot achieve the expected purpose

17. Too many search options and excessive complexity

18. Use hidden image links that are easy to ignore

19. You must scroll down to view important information on the current page.

20. The image button has no visual changes when you press the mouse.

21. Meaningless false progress bars

22. The mouse pointer is not displayed as a busy status when a task is executed for a long time.

23. Possible Human Error input is not considered.

24. Think that a good UI is a beautiful UI

25. Blind and incorrect use of page Modular Design