principle-experience-first
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseExperience First
体验优先
When implementation convenience conflicts with user delight, choose delight.
- Every feature, control, and option must be justified
- Ship less, ship better (polished experience with three features beats rough one with ten)
- Prototype before committing (design decisions are cheaper in throwaway HTML than production code)
- Get the details right (transitions, alignment, spacing, feedback, error states)
- Tighten the core loop (every feature should serve the central workflow or get out of the way)
The user is whoever consumes the work. For a UI that is the end user. For a library or an internal API it is the colleague who imports it. The engineer who maintains the code next is a user too. Weigh their experience the same way, and explain impact from their perspective.
Foundations should serve the experience. Foundational thinking governs the sequence of work. This principle governs the target.
当实现便利与用户愉悦发生冲突时，选择用户愉悦。
- 每个功能、控件和选项都必须有充分的存在理由
- 少而精（精心打磨三个功能的体验，胜过包含十个粗糙功能的版本）
- 承诺开发前先做原型（在一次性 HTML 中调整设计决策，比在生产代码中更经济）
- 把细节做到位（转场、对齐、间距、反馈、错误状态）
- 收紧核心流程（每个功能都应服务于核心工作流，否则就应被移除）
用户就是最终使用这项成果的人。对于 UI 而言，是终端用户；对于库或内部 API 而言，是导入并使用它的同事。接下来维护代码的工程师同样是用户。应以同样的方式衡量他们的体验，并从他们的视角说明影响。
基础设施应服务于体验。基础设施思维决定工作的顺序，而这一原则决定工作的目标。