principle-experience-first

1# Experience First
2 
3When implementation convenience conflicts with user delight, choose delight.
4 
5- Every feature, control, and option must be justified
6- Ship less, ship better (polished experience with three features beats rough one with ten)
7- Prototype before committing (design decisions are cheaper in throwaway HTML than production code)
8- Get the details right (transitions, alignment, spacing, feedback, error states)
9- Tighten the core loop (every feature should serve the central workflow or get out of the way)
10 
11The 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.
12 
13Foundations should serve the experience. Foundational thinking governs the *sequence* of work. This principle governs the *target*.