UI and UX get used as synonyms, usually by people selling one and calling it the other. They describe two different layers of the same product, and a project can be strong in one and weak in the other.
UX: does it work for the person using it
User experience is about structure and flow. It asks: what is this person trying to do, what steps does it take, where do they get stuck, and what happens when something goes wrong? UX work produces things like user flows, information architecture, wireframes and prototypes. None of it is about colour.
UI: how the working thing looks and feels
User interface is the visual and interactive layer: typography, colour, spacing, iconography, states, motion. Good UI makes a well-structured product feel effortless and trustworthy. Good UI on a broken flow just makes a frustrating experience look nice.
Why the distinction matters when you brief a project
If you ask for "a UI refresh" when the real problem is that customers cannot find what they need, you will get a prettier version of the same problem. If you ask for "UX" but expect a finished visual design, you may be surprised by grey wireframes. Naming the actual problem gets you the right work:
- "People abandon the signup halfway" — this is UX first.
- "The site works but looks dated and off-brand" — this is UI first.
- "We are building something new" — you need both, in that order.
How they work together
In practice the two overlap constantly. A UX decision about how many steps a form has directly affects the UI. A UI decision about button hierarchy affects whether users understand the flow. The best results come from treating them as one process with two lenses, not two separate handoffs.
In short
UX is whether it works; UI is whether it feels good to use. We handle both as part of our design work — if you are not sure which your project needs, describe the problem and we will tell you where to start.