User experience is not the paint. It is the load-bearing wall. How the data is shaped, how long a screen takes to answer, what happens when something fails: all of it reaches the reader as a feeling, long before they notice a colour.
Which means most experience problems are decisions made somewhere else.
Start from the job, not the screen
Before drawing anything, finish this sentence: the reader came here to ____ .
One verb. Book the session. Find the tool. Get the invoice. If the sentence needs an "and", there are two screens.
Then remove every step that is not part of it
Walk your own flow and count the steps between arriving and finishing. Each one needs a reason. Most sign-up forms, cookie banners and welcome tours exist for the company, not the reader.
Most of what gets called delight is just the absence of friction. Nobody thanks you for it, and everybody notices when it is missing.
Speed is a feeling, not a metric
A screen that answers instantly feels well made even when it is plain. A beautiful screen that hesitates feels broken.
Three habits carry most of it:
- —Show the shape of the page immediately, even before the content arrives.
- —Never let a button sit silent after a press. Change it the moment it is tapped.
- —Assume the action worked and correct it if it did not, for anything small and reversible like a like or a save.
The states nobody designs
A screen has four states. Most projects design one of them.
Empty
The first thing a new reader sees, and usually a blank box. Say what goes here and give them the one action that fills it.
Loading
If it takes under a second, show the shape of what is coming. If it takes longer, say what is happening. A spinner with no words reads as stuck.
Error
Say what happened, in the reader's terms, and what to do next. Keep whatever they typed.
Full
The state you designed, plus the version with fifty rows in it and a name three times longer than your placeholder.
Words are the interface
Most of what a reader looks at is text. Labels, buttons and messages do more for clarity than any layout change.
- —Buttons name the action: "Send the question", not "Submit".
- —Labels are plain nouns: "Email", not "Please enter your email address".
- —Helper text explains why the field exists, not what to type.
Reading your own interface out loud finds more problems in ten minutes than a week of opinions.
Watch one person use it
Not a survey. One person, your actual screen, no help from you. Ask them to do the thing and stay quiet while they try.
You will learn more in fifteen minutes than in a month of internal debate, and you will only need to watch three people before the same two problems repeat.
Start here this week
Open your own product on a phone, on a slow connection, as a brand new user. That path is the one most readers take and the one teams almost never test.
The design systems include the four states described here, so the empty and error versions exist from the start rather than being added after launch.
