6️⃣ Recognition rather than recall

    Minimize the user's memory load by making objects, actions, and option visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable(可检索的) whenever appropriate.

     WHY?

        - A familiar stimulus(刺激) triggers retrieval(检索) from long-term memory.

        - Recall forces users to recreate the chain of associations themselves, or forcefully learn through elaborative rehearsal. ❓

        - Recall will fail unless remembered actions are frequent, recent, strongly associated.

    DIRECT MANIPULATION    

    Where does recall come up?

7️⃣ Flexibility and Efficiency of Use

    Accelerator - unseen by the novice user - may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

    WHY?

        - Recall is bad for new/infrequent users, but can be fast for experts.

        - Different users have different goals, allow them to customize.

    ACCELERATORS

    SHORTCUTS(捷径) and BOOKMARK

    PERSONALIZE

8️⃣ Aesthetic and Minimalist Design

    Dialogues should not contain irrelevant or useless information. Every extra unit of information competes with the relevant units of information and diminishes their relative visibility. 

    WHY?

        - Visual clutter makes it harder to find and focus on the desired actions.

        - Good use of color, shape, motion, and gestalt(形状) principles guide the eye.

        - The more there is to see, the less of it users will actually see.

    GOOD 🌰： Google homepage

9️⃣ Error Recovery

    Error messages should be expressed in plain language(no codes), precisely indicate the problem, and constructively suggest a solution.

    WHY?

        - 1️⃣Give feedback

        - 2️⃣Speak the user's language

        - 3️⃣Allow users to undo and escape from mistakes

        - 5️⃣Prevent and detect errors

    GOOD 🌰

    BAD 🌰

🔟 Help and documentation

    It may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

    WHY?

        - Your UI might not be as self-explanatory as you thought

        - Structure to support Gulf of Execution.

    GOOD 🌰

    CONTEXTUAL(语境相关的) HELP