尼尔森十大可用性原则 https://www.nngroup.com/articles/ten-usability-heuristics/

01状态可见原则

Visibility of system status

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

思考：明确用户所处状态，并对用户的操作进行「即时」反馈

场景1：明确用户所处状态，告知用户完成所需要的步骤。嘀嗒出行在认证车主时，将认证步骤分为了三步，在步骤条里可以告知将要完善哪些资料。

场景2：对操作进行反馈。藏书馆在预约图书后，会告知用户是否预约成功，预约的排队状态。

02贴近现实原则

Match between system and the real world

The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

思考：系统的表达，要符合用户所在的环境（年龄、学历、文化、时代背景），并且不要使用系统的术语。遵循现实世界的逻辑顺序。

场景1：假如设计一个手势的图标，那这个手势在各国可以通用么？

场景2：遵循现实世界的逻辑，手机里面的计算器，和现实中使用的计算器差不多，降低了用户的操作成本。

03用户可控原则

User control and freedom

Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

理解：用户常常会不小心进行一些操作，应该为他们提供可撤回操作，相当于ctrl+z；当用户进行误操作后提供解决办法，可联想到状态可见原则。

微信的消息撤回再编辑流程刚刚好可以说明这个原则

场景1：

当一条消息、语音或者表情不小心发出后，微信的可撤回功能就很贴心了。

场景2：

当对一条消息进行编辑时有这么多种操作，手胖不小心点到撤回，微信会在撤回消息反馈的同时，提示可以重新编辑消息。点击重新编辑，撤回的消息就会重新出现在输入框，用户编辑或者再次发送。

04一致性原则

Consistency and standards

Users should not have to wonder whether different words, situations, or actions mean the same thing.

理解：文案、功能、操作、逻辑保持一致，不让用户感到困惑

举个例子：当新建、创建、建立、新增、添加等等词语，同时出现在一个系统中

05防错原则

Error prevention

Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

理解：对关键操作或者不可撤回的操作进行确认，防止用户出错。在文案上保持一致，使操作的提示语更加清晰

场景：在车主退出认证的过程中，进行确认并提示此操作的重要性。

06减轻用户记忆原则

Recognition rather than recall

Minimize the user's memory load by making objects, actions, and options 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.

理解：把用户需要的信息展示出来，减少用户的认知负担。

场景：京东会把筛选条件显示出来，方便用户显示出来，但因为空间的原因只能显示部分筛选条件。

07灵活高效原则

Aesthetic and minimalist design

Accelerators — 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.

理解：为大部分用户提供灵活高效的操作

场景：MIUI的桌面可以批量进行操作，比如批量卸载、移动，多选成组等，手指戳几下就可以高效的完成桌面整理。

08易扫原则

Aesthetic and minimalist design

Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

理解：在浏览过程中信息要突出重点，弱化和剔除无关信息

场景：苹果的官方网站，不管是图片还是文字都展示的清晰明了，没有多余的信息。

09容错原则

Help users recognize, diagnose, and recover from errors 

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

理解：明确错误的状态，帮助用户去恢复或者提供下一步的方向。一些发生错误后只展示一个404的网站们，你们的良心不会痛么？

场景：在B站上面有想看的视频但暂时没时间看的话，可以将视频添加到稍后再看。但当添加的视频超过一定数量后会趣味提示“塞满啦！先看看库存吧~” 点明现在无法添加的状态并且引导用户去进行下一步。

10帮助原则

Help and documentation

Even though it is better if the system can be used without 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.

理解：帮助用户完成任务，包括一次性提示、常驻提示、帮助文档、客服等。

场景：石墨文档在编辑页面，提供了文档指南、快捷键、客服服务，帮助用户来解决写作过程中遇到的问题。

Powered by Froala Editor