principle-experience-first
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseExperience First
体验优先
The product is the experience. Every technical decision either helps or hurts it. When implementation convenience conflicts with user delight, choose delight.
- Say no to 1,000 things (every feature, control, and option must earn its place)
- 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)
- Sweat the details (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 seat.
Foundations should serve the experience, not the other way around. Foundational thinking governs the sequence of work; this principle governs the target.
产品即体验。每一项技术决策要么助力体验，要么损害体验。当实现便利性与用户愉悦体验发生冲突时，优先选择用户愉悦体验。
- 拒绝不必要的内容（每一项功能、控件和选项都必须证明自身存在的价值）
- 宁少勿滥，精益求精（拥有三项打磨精良功能的体验，胜过拥有十项粗糙功能的体验）
- 先做原型再投入开发（在一次性HTML中验证设计决策的成本远低于生产代码）
- 注重细节（过渡效果、对齐方式、间距、反馈机制、错误状态）
- 优化核心流程（每一项功能都应服务于核心工作流，否则就应移除）
用户是所有使用该成果的人。对于UI而言，用户是终端用户；对于库或内部API而言，用户是导入它的同事；后续维护代码的工程师也是用户。同样重视他们的体验，并从他们的角度解释影响。
基础架构应为体验服务，而非本末倒置。基础思维决定工作的顺序；而本原则决定工作的目标。