Key answer: UX (user experience) is the whole of the experience, i.e. whether the product solves the problem and the path to the goal is logical. UI (user interface) is the visual layer, i.e. layout, typography, colour and components. UX without UI is a diagram with no character; UI without UX is a pretty façade where nothing gets done. A good product needs both.
Table of contents
The short answer
UX governs how the product works and whether it gets the job done: structure, paths, naming, step order. UI governs how the product looks and responds: layout, typography, colour, components and their states. The boundary can blur, but the distinction organises the work – and explains why a "beautiful website" can fail to sell.
A restaurant, not icing
The popular metaphor says UX is the cake and UI the icing. It's catchy and misleading – it implies UI is decoration. A restaurant works better: UX is the menu, the serving order, the waiting time and whether the waiter understands questions. UI is the interior, the tableware and the menu's legibility. An evening can be ruined by an undercooked dish or by a sticky floor – the guest doesn't analyse which "layer" failed. They just don't come back.
What a UX designer actually does
- researches users and their problems (interviews, tests, analytics),
- designs the information architecture: what lives where and what it is called,
- draws user flows and functional wireframes,
- tests prototypes with people before code exists,
- makes sure every step moves the user toward their goal – and the company toward conversion.
UX work tends to be invisible: nobody praises a site because "everything was findable". Only its absence shows.
What a UI designer actually does
- translates wireframes into the brand's final visual language,
- builds the typographic hierarchy and the grid,
- designs components with all their states (hover, focus, error, loading),
- ensures contrast and accessibility (WCAG),
- designs the micro-interactions that create a sense of fluidity.
UI's work is visible instantly – and it builds the first impression of credibility. Research shows trust judgements about a site form in fractions of a second, based on aesthetics.
What happens when one layer is missing
UI without UX: "the beautiful maze": the site dazzles in portfolio screenshots, but users can't find the pricing, the form has 14 fields and the path to purchase runs through six screens. Result: traffic without conversions.
UX without UI: "useful boredom": everything works logically, but last-decade looks undermine credibility. In premium segments and trust-based industries, that's disqualifying.
How it works in practice
In a healthy process the layers follow and interweave: research → architecture → wireframes → testing (UX), then visual design and a design system (UI), then testing again. That's why splitting "the UX phase" and "the UI phase" between different companies usually hurts – each layer's decisions constantly affect the other.
At Sweet Lava one team designs both layers (plus AX – AI experiences), and the developers implementing them sit at the next desk. See how we work.