Service
Designing the screens people use, not the ones they read
A marketing page is judged in two seconds. A tool somebody opens every morning is judged over months, and the criteria are completely different.
A product is not a longer website
A website persuades somebody to act once. An application supports somebody performing the same task repeatedly, often under time pressure, often while thinking about something else. Optimizing it for first impressions actively makes it worse.
The measure changes accordingly: not whether the screen is striking, but whether the frequent task takes the fewest steps, whether errors are recoverable, and whether somebody returning after a fortnight can still find what they came for.
Put plainly: if what you need is a website that wins customers, that is our web design service. This page is for the screens behind a login — the dashboard, the portal, the booking flow, the tool your own team uses every day.
Two different jobs, routinely confused
They get bundled into one phrase, which is why briefs so often ask for the wrong one. Both matter; they answer different questions and they happen in a different order.
What are people trying to do, in what order, and what stops them? This is research, task flows, information architecture and wireframes — the decisions that determine whether the thing is usable at all, made before anything is styled.
It is also where the cheapest fixes live. Removing a step costs a conversation at this stage and a rebuild once it has been designed, developed and shipped.
How it looks, reads and responds: type scale, spacing, color, states, and the components everything is assembled from. This is where a product starts feeling considered rather than assembled.
It is also where consistency is won or lost. A design system — real components with defined states rather than a page of screenshots — is what stops the fourteenth screen looking like a different product.
Accessible because it is the same work
Contrast that holds, targets big enough for a thumb, focus states that are visible, forms that a keyboard can complete, and motion that can be turned off. None of that is a separate accessibility phase; it is what competent interface design already looks like.
Doing it during design costs nothing extra. Retrofitting it after an audit means revisiting every screen, which is how it ends up being described as expensive.
Measured on this page, in your browser
This page, checked against the basics
- —
- —
- —
- —
These are read from your browser as you look at this, not typed in by us. Open devtools and check them — that is rather the point.