UI UX Design
UX decides what the thing does and in what order. UI decides how it looks and behaves while doing it. Both are design, they get conflated constantly, and confusing them is how a project ends up with a beautiful interface to a badly conceived flow.
The difference in practice
UX is structure and sequence: what a user is trying to accomplish, what steps that takes, what they need at each one, and what happens when something goes wrong. It is mostly decided before anything is drawn.
UI is the surface: type, colour, spacing, states, motion. It expresses the structure and it cannot rescue a bad one. A checkout with a step in the wrong place is not fixed by a nicer button.
What changes when the user is an expert
Nearly everything about what counts as good. Consumer interface conventions assume a novice who needs simplifying for. A process engineer looking up a compatibility chart does not need simplifying for, they need the data faster.
- Density is a feature. A comparison table beats six friendly cards. Spreading information out to look clean makes it slower to use.
- Precision beats approximation. "High temperature resistance" is worthless next to a number and a unit.
- Jargon is correct. Using the trade's actual vocabulary signals competence. Translating it into plain language reads as talking down.
- Progressive disclosure has limits. Hiding specification behind a tab to keep a page tidy hides the thing they came for.
What the work produces
| Output | What it settles |
|---|---|
| Flows | The steps to complete a task, including the failure paths |
| Wireframes | What is on a screen and in what priority, before visual decisions |
| Component library | Buttons, forms, tables, cards and their states, defined once |
| Design tokens | Type, colour and spacing as named values, so the system can be changed centrally |
| States | Empty, loading, error and success, which are where most designs are silently incomplete |
The states row is the one most often missing. A design showing only the successful path leaves the developer inventing the error message, and error messages are where users are most frustrated and least forgiving.
How a design is judged
On whether people can complete the task, not on whether the team likes it. Those come apart regularly, and internal opinion is the least reliable input available because everyone in the room already knows how it works.
Where a real interface exists, observed behaviour settles it: session recordings and form analytics show where people stall. Before it exists, a handful of people attempting a task while you watch will surface more than a month of internal debate.
Is accessibility part of this?
It is part of the definition, not a compliance step afterwards. Focus states, contrast, labelled fields, sensible heading order and adequate tap targets are interface design decisions, and they are cheap while designing and awkward to retrofit.
They also improve the interface for everyone. Clear focus states help keyboard users and anyone tabbing through a form quickly. Good contrast helps a screen-reader user and a technician holding a phone in sunlight.
Where this fits
Inside web development. It sits between custom design, which establishes the system, and the build. For an interface with genuine application behaviour rather than pages, it leads into web application development.
Frequently asked questions
Do we need UX work for a marketing site?
Lighter, but not none. The structural questions still apply: what is a visitor trying to find, how many steps does it take, what happens when the form fails. Those are UX questions whether or not anyone calls them that.
Can you work from our brand guidelines?
Yes. Guidelines usually cover logo, colour and type but rarely define interface components or states, so the work is extending them consistently rather than replacing them.
How much user research is realistic?
Less than a textbook prescribes and more than most projects do. Watching five people attempt the actual task surfaces most serious problems. The barrier is usually scheduling rather than budget, and talking to your own customers is a legitimate substitute for recruiting strangers.
See where you stand
We will review your current search visibility and show you what buyers find when they look for what you do.
Contact Us