The 1% that matters

Why some interfaces feel unmistakably better

Most interfaces work. They load, respond, display data. Yet some feel _unmistakably better_. A button that responds 16ms faster. Real small caps instead of scaled-down capitals. A spring curve instead of linear easing. An error message that says _what to do_, not _what went wrong_. None of these survive an A/B test alone. Together, they're why people say "polished" without knowing why. ## The compounding effect Kerned headline. Eased animation. Copy that leads with _why_. Optical centring. Each layer amplifies the one beneath it. A spring animation on a poorly typeset page is not craft. ## What "website autism" actually means The inability to _unsee_ a typographic error. The compulsion to adjust a border-radius by two pixels because the concentric math is wrong. The refusal to ship "Learn More" when "See how it works" converts better. Not perfectionism. Trained pattern recognition. Once calibrated, you stop seeing interfaces as objects and start seeing them as collections of decisions. ## The four domains 1. **Typography**: selection, sizing, spacing, refinement of text. Where most quality gaps live. 2. **Animation**: motion that connects states and provides feedback. Done well, invisible. Done poorly, the first thing users notice. 3. **Craft**: spacing, colour, layout, interaction details. The 4-pixel grid. The `overscroll-behavior`. The focus ring that follows the border-radius. 4. **Copywriting**: word choices that determine whether a user feels guided or confused. A typeset headline means nothing under generic copy. A perfect drawer animation is wasted if the form inside has no `inputmode` on the phone field. ## What this course will do This course assumes you can build interfaces. It will train you to _see_. By the end, violations feel wrong before you can name them. Not knowledge. Instinct.