The one-line answer
UI is the visible surface of the product. UX is the discipline that decides what the surface should do, for whom, and why. UI is one of UX's outputs.
That's the operational summary. Everything below is the practical detail — what each discipline actually does on a Tuesday afternoon, where the boundary sits in different sizes of organisation, why the titles have inflated since 2020, and how to think about which path to choose. For the broader Fundamentals frame, see what is UX design.
What UX design is
UX is the discipline of making products usable, useful and commercially effective. The work covers research (understanding the user and the context), structure (information architecture, navigation, hierarchy), interaction (how the product behaves), content (the words and information design), accessibility (the WCAG floor and beyond), and the negotiation with stakeholders about what gets built. The visible UI is one output of this work; everything that sits behind the visible UI is also UX work.
Operationally, a UX designer's week splits across three categories — synthesis (turning research and stakeholder input into problem framings), production (flows, wireframes, prototypes, content, the artefacts engineers can build from), and decision work (defending recommendations, communicating risk, revising). Mid-level UX designers spend roughly a third of their time in each. Senior UX designers spend more time on synthesis and decision; less on production.
What UI design is
UI is the discipline of designing the visible surface — typography, layout, colour, iconography, interaction states, the visual language that communicates what the product is and how to use it. The work covers visual hierarchy, brand expression, micro-interaction craft, design systems and component libraries, accessibility-aware visual choices (contrast, focus states, target sizes), and the production-quality detail that makes a product feel polished rather than rough.
A UI designer's week is more production-heavy than a UX designer's. The day-to-day is making screens — high-fidelity layouts, polishing details, building out design system components, working with engineering on the implementation of the visual specification. Senior UI designers move toward design systems, brand evolution, complex interaction patterns and the kind of cross-product visual consistency that takes years to build well.
Where they overlap
Five categories of work belong to both disciplines in most teams:
- Information hierarchy. Deciding what's most important on a screen. UX brings the user-need framing; UI translates the hierarchy into type sizes, weights, spacing and visual prominence.
- Interaction states. Hover, focus, active, disabled, loading, error, success. Both disciplines own a piece — UX defines the behaviour, UI defines the visual rendering.
- Accessibility. Contrast and target sizes are mostly UI; semantic structure and keyboard interaction are mostly UX. Neither owns it alone, and weak accessibility usually means the disciplines weren't talking.
- Component design. What a button should communicate is UX; how it should look is UI. In design-systems-heavy teams the two roles often pair on this.
- Content placement. Where the copy goes is UX (related to hierarchy and flow); how it sits visually is UI (related to layout and typography).
In small teams these overlap categories are held by one person. In larger teams they're the boundary territory where the two disciplines need to work together actively. The teams that ship well have explicit conversations about who owns which piece; the teams that don't ship products with detail inconsistencies that get noticed in audits months later.
Where they meaningfully differ
The differences are sharpest in the work that sits at the extremes of each discipline.
Work that lives clearly in UX
- Conducting user research (interviews, surveys, usability tests)
- Information architecture and navigation design
- Defining flows and decision points
- Writing problem statements and decision memos
- Stakeholder workshops and alignment sessions
- Measuring and reporting UX outcomes against business metrics
Work that lives clearly in UI
- Visual brand expression in product
- Typography systems and type-scale design
- Colour systems and palette design
- Micro-interaction craft and motion design
- Design system component visual specification
- High-fidelity production design
The boundary is fuzzier in the middle — flows, components, accessibility, content — and that fuzzy middle is where most product teams have alignment work to do.
UX vs UI vs Product Design
Product Designer is the title that has confused everything since around 2018. The cleanest practical framing:
Product Designer in Silicon Valley and SF-influenced product teams means "a designer expected to do UX, UI, and contribute commercially to the product as a whole". The title implies seniority, ownership and outcome orientation; the salary expectation is higher than UX or UI alone.
Product Designer in UK and European contexts varies wildly. Some companies use it interchangeably with Senior UX Designer. Others use it to mean "UI designer who works on products rather than marketing". A third group use it as a rebrand of UX to sound more commercial. When you see the title on a UK job spec, read the responsibilities section carefully — the title alone does not tell you what the role is.
The full picture sits in the careers cluster: UX vs Product Designer covers the title politics and offer implications in operational detail.
Why job descriptions blur the lines
If you read 100 UK design job descriptions in 2026, you'll see "UX/UI Designer" appear roughly twice as often as either UX Designer or UI Designer alone. The blur is not accidental. Three reasons drive it.
Resource efficiency. A startup or small product team gets more shipped from one designer holding both responsibilities than from two specialists. The combined title reflects the reality of the work expected.
Recruiter hedging. Job postings often originate with HR or recruiters who don't distinguish the disciplines. "UX/UI" widens the candidate pool, even when the hiring manager has a specific specialism in mind.
Inflated expectations. Some job descriptions list responsibilities from UX, UI, content, research, brand and front-end engineering in the same role. These are not realistic expectations of one designer's time; they're wishlists from teams that haven't decided what they actually need. Candidates who recognise the pattern interview with that awareness.
Title inflation since 2020
Four titles have inflated meaningfully in the UK and US markets since 2020:
- Senior Designer — increasingly used for designers with 3–4 years of experience. Pre-2020 it meant 6+ years.
- Lead Designer — often used for individual contributors with limited reports rather than people-managers.
- Principal Designer — newly common; varies wildly between "very senior IC" and "design strategy oversight" depending on org.
- Staff Designer — borrowed from engineering; in some orgs the most senior IC title.
The pattern: titles have inflated to compensate for slower salary growth in cash terms, particularly in startups offering equity rather than cash uplift. For candidates, this means reading the responsibilities and reports, not just the title. The careers cluster goes deeper: senior vs junior UX designer covers what the seniority bands actually mean operationally.
What hiring managers actually expect
Behind the inflated titles and confused job specs, hiring managers in 2026 screen for a relatively short list:
- Evidence of decision-making. The portfolio case studies show why you made the choices you did, not just what you shipped.
- Working command of both disciplines. Even when the role is specialist, the assumption is you can hold a conversation about the other side.
- Accessibility literacy. WCAG 2.2 floor, contrast and focus state awareness, semantic markup understanding for UX; visual accessibility awareness for UI.
- Tool fluency. Figma is the default for both. Strong knowledge of design tokens, components and auto-layout for both.
- AI judgement. By 2026 every senior interview will ask about AI. Designers who can articulate where it accelerates them and where it doesn't are hired; designers who treat it as a binary topic are not.
- Communication. Writing samples, presentation samples, evidence that the candidate can argue for a design decision in front of an executive.
For the operational view of how to demonstrate these in a portfolio, the UX portfolio guide covers what hiring managers actually finish reading.
Career implications
For someone choosing between the two paths, three honest observations matter most.
UX is more durable to AI compression. The judgement, research and stakeholder communication layers of UX have not been compressed by AI in 2026. The pure visual-production layer has. UX-leaning designers who can defend decisions are gaining leverage; UI-leaning designers who can only push pixels are losing share to software.
UI specialism still pays, but at the top. Senior UI designers with deep design-system expertise, complex interaction-pattern fluency, or brand-anchored craft are in demand and well compensated. The career path narrows toward seniority — there are fewer mid-level UI roles available than in 2022.
The combined path is the most common. Most working designers in the UK in 2026 do both. The honest career advice: build both competencies, then deepen into whichever side of the work you genuinely enjoy most. The UX salary reference covers the live UK ranges by seniority.
The strongest hires I've made in the last three years have all been designers who can hold both disciplines competently and have specialised deeply in one. A pure-UX designer with weak visual craft loses credibility in design reviews; a pure-UI designer with weak research literacy loses credibility in stakeholder meetings. The combination beats the specialisation when you're hiring for one designer to do real work.
The AI effect on both
AI has reshaped both disciplines, but in different ways.
For UX, AI accelerates the mechanical layer of research (transcript coding, theme clustering, first-pass synthesis), the production layer of design (flows from prompts, wireframes from descriptions), and the writing layer (microcopy variants, decision memos, stakeholder updates). It does not replace the judgement layer — recognising what an interviewee isn't saying, defending recommendations to executives, deciding which finding matters most. The full operational view: AI for UX designers and the framework anchor what AI should not replace in UX.
For UI, AI accelerates visual production directly. Asset generation, layout variants, component variations, brand-applied design work. The compression at the entry level is real. What AI does not yet do well: design-system governance, complex multi-state interaction patterns, brand evolution that compounds over years, accessibility nuance, the polish that distinguishes a product that feels professional from one that feels generic.
The pattern in both disciplines is the same: AI compresses production, expands judgement and direction. Designers who position themselves as direction-givers do well; designers who position themselves as producers are competing with software.
Which to choose
If you're early in the discipline and genuinely choosing, four honest questions:
- Do you enjoy talking to users and stakeholders, or do you enjoy making things look right? Both are valid, both can pay well, both can be a career. The first instinct is closer to UX; the second is closer to UI.
- Do you find satisfaction in framing the problem or in solving it visually? Framers gravitate to UX; solvers gravitate to UI.
- Do you want commercial impact to be measurable, or craft to be visible? UX maps to the first; UI maps to the second. Both are real; the question is which form of recognition you want to optimise for.
- How comfortable are you with ambiguity? UX work has more of it. If you find ambiguity energising, UX. If you prefer cleaner boundaries, UI.
And the practical answer most senior practitioners give: start with whichever side resonates, get to working competency in the other within two years, and let your specialism crystallise from your actual work, not your early decision. The how to become a UX designer in 2026 pillar covers the operational path into the discipline.
Frequently asked questions
What is the difference between UX and UI design?
UI is the visible surface of the product — typography, layout, colour, icons, interaction details. UX is the broader discipline that decides what the surface should do, for whom, and why. In small teams the same person does both; in larger orgs they're separate specialisms. The cleanest framing: UI is one of UX's outputs.
Is UX or UI design harder to learn?
UI is easier to learn to competence; UX is easier to learn to a beginner level. UI has a finite tool set (type, colour, layout, components) and clear best practice. UX has fewer discrete skills but more judgement work — knowing which research method to reach for, defending decisions under pressure, framing problems so the team can solve them. Both get harder as you get senior.
Do you need to know UI to do UX?
Yes, at a working level. A UX designer who can't recognise weak visual hierarchy, who can't tell when typography is failing, who can't make a button look credible, is doing only half the job. The reverse is more forgiving: UI specialists can specialise without strong research chops, particularly in larger orgs. But the strongest practitioners have a working command of both.
Which pays more — UX or UI design?
UX pays slightly more on average in the UK in 2026, but the gap is narrowing and roles increasingly carry both responsibilities. Senior UX with research or leadership specialism tops out higher than senior UI; senior UI with strong design-system or interaction expertise converges. The overlap is now significant.
Is UI design dying because of AI?
No, but the entry-level UI role has compressed sharply. AI produces passable visual output in seconds; junior UI hiring has softened since 2023. Senior UI roles involving design systems, accessibility, complex interaction patterns and brand-anchored craft have held or grown. Same pattern as UX: production compressed, judgement layer not.
Should I learn UX or UI first?
UX, if your interests run toward research, strategy or commercial impact. UI, if your interests run toward craft, visual systems or brand. Both, eventually, regardless of where you start. Most career-long practitioners hold both at a working level; deep specialism develops in years three to five.