Designing Empty States You Will Actually Read
An empty state is a first impression for a feature. 'No data' is a missed opportunity — explain what the feature does, why it is empty, and what the next…
Read article →Form Validation That Respects the User
Validate on blur, not on every keystroke. A user typing their email should not see 'invalid email' before they finish the @.Show errors inline, anchored…
Read article →Designing for Real Devices, Not Devtools
Devtools device emulation does not reproduce slow CPUs, OS keyboards, or 3G networks. Test on a 2018 mid-range Android occasionally — the experience differs sharply…
Read article →Why Tooltips Are the Wrong Answer Most of the Time
Tooltips are invisible by default. Users do not hover icons looking for hidden help — they tap and hope.If the label is essential, put it…
Read article →Choosing a Default That Does the Right Thing
The first default beats the user's first decision. The longer it persists, the more users you affect — and the more you should sweat the…
Read article →The Quiet Power of Plain HTML Forms
Native form elements have decades of accessibility, autofill, and platform integration baked in. A custom div-and-JavaScript dropdown rarely improves on <select> when measure…
Read article →Designing With prefers-reduced-motion
About 5% of users have prefers-reduced-motion set — vestibular disorders, headaches, or just a preference for calmer interfaces. Respect it.The CSS pattern: @media (prefers-reduced…
Read article →Search That Feels Instant
Three rules: debounce keystrokes, cancel in-flight requests, render results progressively. Together they make a slow backend feel responsive.The minimum debounce that still feels i…
Read article →Buttons vs Links: The Five-Second Rule
If the control navigates to a URL, use an anchor. If the control performs an action, use a button. Get this right and middle-click, copy-link,…
Read article →