In short
UI design is the interface a person sees and touches — layout, type, colour, components. UX design is the experience underneath — whether the product is useful, learnable, and actually gets someone to their goal. UI is a part of UX. A product needs both: good UX with bad UI feels untrustworthy; good UI with bad UX is a pretty dead end.
The short version
The most common analogy is a house. UX is the floor plan — where the rooms are, how you move between them, whether the layout makes sense for how people actually live. UI is the finish — the paint, the fixtures, the door handles you reach for. A gorgeous finish on a bad floor plan is still a house you don’t want to live in.
So: UX is whether it works. UI is how it looks and feels while it works.
What UI design covers
UI — user interface — design is the tangible, visual layer. It’s concerned with:
- Layout, spacing, and visual hierarchy — what draws the eye and in what order.
- Typography and colour — legibility, tone, and contrast.
- Components and their states — buttons, inputs, menus, and how they respond to hover, focus, and press.
- Consistency — the same patterns behaving the same way everywhere.
Done well, UI makes a product feel clear, credible, and effortless to look at. It cannot, on its own, make the product worth using.
What UX design covers
UX — user experience — design is the wider question of whether the product does its job. It covers:
- The problem — what the person is actually trying to accomplish.
- The flow — the sequence of steps between intent and outcome, and how to shorten it.
- Information architecture — how content and features are organised so people can find them.
- The edge cases — empty, loading, and error states, and what happens when things go wrong.
UX is mostly invisible when it’s good. You notice it only when it’s bad — when you can’t find the button, or the flow makes you repeat yourself, or you’re not sure whether your action worked.
Where they meet
The clean split is a teaching device, not a real boundary. In practice UI and UX decisions constantly affect each other. Making a primary action more visually prominent (a UI choice) changes which path people take (a UX outcome). Cutting a step from a flow (UX) changes what a screen needs to contain (UI). You cannot fully separate them because the person using the product doesn’t experience them separately.
Why you need both
The failure modes are symmetrical. A product with strong UX and weak UI feels clumsy and hard to trust — the logic is sound but nothing signals quality. A product with strong UI and weak UX is worse in a subtler way: it looks so polished that people assume the confusion is their fault.
This is why it rarely pays to treat UI and UX as separate purchases handed to separate people. The best interfaces come from designing the experience and the surface as one decision — and, ideally, from the same team that builds it, so the finished product still feels the way it did in the design.
Common questions
What is the difference between UI and UX?
UI design is the visual and interactive surface — layout, typography, colour, and the components a person touches. UX design is the whole journey — whether the product is useful, learnable, and gets the person to their goal. UI is part of UX, not a synonym for it.
Can you have good UI but bad UX?
Yes, and it is common. A product can be beautifully styled yet confusing, slow, or aimed at the wrong task. Polished visuals cannot fix a broken flow — they just make the wrong path look nicer.
Which matters more, UI or UX?
Neither works alone. Good UX with poor UI feels clumsy and untrustworthy; good UI with poor UX is a pretty dead end. In practice they are decided together, which is why most teams design them as one discipline.
Are UI and UX separate jobs?
They can be, especially in large organisations, but the split is often artificial. Interface and experience decisions constantly affect each other, so smaller and better teams usually treat them as a single practice.