"UI/UX" gets treated as one word, but it's two disciplines that solve different problems — one is whether a product makes sense, the other is what it looks like while doing it. This page maps the real distinction, the craft principles behind good interface design, and how to hire for or break into the field, with links to 22 in-depth guides.
The same question asked eight different ways — because it's the single most-searched confusion in the field, and getting it wrong shapes who you hire and what you brief them on.
What each term actually covers, how they overlap, and where teams mix them up.
How they overlap, where they diverge, and which one a project actually needs.
Different deliverables, tools, and success metrics — with a worked example from a real signup flow.
A founder's framework for deciding what your product actually needs.
The real difference, with a restaurant analogy that actually clears it up.
What actually gets beginners hired, and why most junior portfolios fail.
What UX actually means, the heuristics behind good decisions, and what bad UX costs.
Distinct histories — one from industrial design, one from human-computer interaction.
Why UX is closer to product research than visual design, and what happens when design and UX priorities genuinely conflict.
The actual process, the frameworks behind it, and how teams measure whether it's working.
Why a brand refresh can make a product look better and convert worse.
What the handoff looks like day to day, and where it breaks down.
The visual and interaction rules that separate an interface that feels obvious from one that feels decorative.
How typography, spacing, and Gestalt principles combine to make an interface feel obvious.
A practical walkthrough of Nielsen's heuristics, applied to real interface problems.
Atomic design, component states, and design tokens — the system behind buttons and cards.
Principles that hold up across projects — visual hierarchy, consistency, feedback.
Sidebar navigation, table density, and layout decisions for a usable dashboard at scale.
What real UI/UX experience looks like on both sides of the hiring table — as a candidate building a portfolio, and as a founder deciding whether to hire in-house or bring in an agency.
What hiring managers actually mean, and how to build it without one.
Real responsibilities, skill levels, and career progression by company size.
When hiring one hybrid designer works, and what it actually costs to get right.
Realistic cost tiers, expected deliverables, and red flags that predict a bad engagement.
Team composition, cost tiers, and the project signals that decide it.
An honest look at features, limits, and pricing versus Squarespace and Cargo.
UX is whether the product works and makes sense; UI is what it looks like while doing it. A restaurant analogy holds up well: UX is the menu design, table layout, and how easy it is to order — UI is the plating. Both matter, but they're solving different problems.
It depends on what's actually broken. If users can't figure out how to complete a task, that's a UX problem — research and flow, not visuals. If the product works but looks unpolished or inconsistent, that's UI. Many early-stage teams hire one hybrid "product designer" who does both at a basic level, then split the roles once the product and team are big enough to justify specialists.
At small scale, yes — the skills overlap more than job titles suggest. At larger scale, the disciplines pull in different directions enough that specialization produces better outcomes: UX work rewards slow, research-heavy iteration, while UI work rewards fast, detail-oriented visual execution.
Real, scoped project work beats generic portfolio pieces — redesigning an existing product with a documented rationale demonstrates the actual thinking hiring managers look for, not just visual polish. What counts as real experience, and a realistic timeline to get job-ready, are covered in the careers section above.