UI vs UX design: what's the difference?

Product design

Imran KhanNovember 12, 20269 min read

A grey wireframe card labelled UX beside a finished interface card labelled UI, with a UI vs UX tile and a cursor, in Usarion's dark brand style

UX design is about how a product works for the person using it. UI design is about how its screens look and respond. UX decides what the person needs to do and in what order. UI decides what the buttons, text and spacing look like while they do it. They're two jobs on one product, and most of the confusion comes from the fact that one person often does both.

This guide uses a real redesign from our own work to show the split decision by decision. We design products for a living, so the examples are ours and you can open them. Every outside fact comes from the page named next to it, read on 12 November 2026.

The short answer

  • UX (user experience) is the whole experience of getting something done with a product: whether it solves the problem, whether the steps make sense, how it feels.
  • UI (user interface) is the part the person touches and sees: screens, buttons, menus, type, colour, icons, motion.
  • UX usually comes first, then UI, but the order isn't strict, and good teams go back and forth.
  • You need both. A beautiful interface on a confusing flow fails, and a sound flow behind an ugly, inconsistent interface loses trust.

The shortest version I've seen is CareerFoundry's: UX makes interfaces useful, UI makes them beautiful. It's a good line and it's slightly unfair to both, because a clear interface is also useful and a good flow can also be beautiful. Keep it as a starting point.

What is UX design?

The Nielsen Norman Group, in a definition by Don Norman and Jakob Nielsen, says user experience "encompasses all aspects of the end-user's interaction with the company, its services, and its products." It adds that "the first requirement for an exemplary user experience is to meet the exact needs of the customer, without fuss or bother."

That's broader than screens. The UX Design Institute points out that user experience is not a physical, tangible thing: it's the ease and user-friendliness of the interaction as a whole. Built In gives a nice example. You buy a camera with an easy interface, it breaks after a year and the company won't fix it. You'll remember the product badly, whatever the interface was like. That's UX.

In practice, UX work on a digital product usually means:

  • finding out who the users are and what they're trying to do, through research;
  • mapping the paths they take, and the places they stop or give up;
  • deciding what the product should include and how it's organised (the sitemap and information architecture);
  • sketching the flow as wireframes, and testing it;
  • changing it when the tests say it doesn't work.

Baymard puts the tools of this side as research tools, user-testing software, sitemaps, usability analysers and wireframing software. Its wireframes are mostly black, white and grey on purpose: they're about structure, not look.

What is UI design?

Baymard defines the user interface as anything a user interacts with to use a digital product. It lists screens, pages, sounds, keyboards and icons, and the interaction might be a tap, a mouse click, a console button on a video game or a voice command. In most of the work we do, it means the screens.

UI design is the work of making those touchpoints clear, consistent and on brand:

  • layout and visual hierarchy: what looks most important, and what doesn't;
  • type, colour, icons and imagery;
  • the components: buttons, forms, tables, menus, and how each one looks when it's empty, loading, wrong or finished;
  • how the interface changes on a phone, a tablet and a wide monitor;
  • motion and the feel of moving from one screen to the next;
  • the style guide or design system that keeps screen fifty looking like screen one.

Justinmind says UI deals with "snapshots in time": a single screen or element you can isolate and look at. That's useful, but I'd add that the states (empty, loading, wrong) are what separate a mockup from an interface people can really use.

UI vs UX design: the main differences

UX designUI design
The question it asksDoes this solve the person's problem, and can they get through it?Is it clear, consistent and does it look right?
What it works onThe whole journey, including steps off the screenThe screens and the elements on them
What it producesResearch findings, user flows, sitemaps, wireframes, test resultsVisual designs, components, style guides and design systems

Four differences are worth knowing.

Scope. UX covers the whole experience and can apply to anything a person uses: an app, a kettle, a clinic. UI is only the interface. Both CareerFoundry and the UX Design Institute make this point: UX isn't only digital, while UI belongs to interfaces.

What each one starts from. UX starts from a problem the user has. UI starts from a structure that already exists, and gives it a look and feel. Baymard describes the first as defining the user's problem and the second as the visual way of solving it.

What you can point at. You can screenshot a UI. You can't screenshot a user experience: you can only see its results, in whether people finish what they came to do.

How they're judged. A UI gets judged in a review: does it look right, is it consistent? A UX gets judged by use: do people finish the task, how long it takes, where they stop. Fedica's results, below, are measured in use.

Does UI sit inside UX?

Yes, in the sense that the interface is part of the experience. Built In lists "UI and UX are the same things" as a common myth for exactly that reason: UI significantly affects UX, but it's only a part of it. People also form an impression before they touch the product, from an advert or from earlier dealings with the company.

In day-to-day work, though, they're separate jobs with separate skills, and most teams give them separate names. Justinmind notes that UX also challenges the interface and justifies the elements that were left out. That's the useful part of the relationship: UX asks what needs to be on the screen, UI decides how it looks, and each corrects the other.

Which comes first?

UX usually comes first. CareerFoundry describes UX research as the first step when deciding whether to build something, with the UI designer stepping in once the prototype is largely settled. It also says this may not always be a linear path, and depends on who handles UX and UI: one person, or two.

A clean sequence is rare. A UI designer starts a screen and finds that the flow needs another step. A test shows that people miss a button, and the fix is visual: more contrast, a clearer label, a different place.

What UI and UX designers do each day

UX designerUI designer
Spends the week onResearch, user journeys, wireframes, usability testsMockups, components, style guides
ToolsResearch and testing tools, wireframing tools, FigmaFigma, moodboards, style guides, prototyping apps
Hands overFlows and wireframesFinal screens and a system developers can build from

The tools overlap more than the lists suggest, and so do the deliverables: the sources disagree on who makes prototypes. The UX Design Institute lists Figma in the requirements for both its UX designer and its UI designer. The skills differ more than the tools: UX leans on research, analysis and problem-solving, UI on visual design, typography and colour.

A real redesign, decision by decision

Dino is a group payments app: friends or teams share one card and the app splits every bill. It already worked when it came to us. In the words of our case study, people could use it but couldn't always tell what it was showing them.

We mapped 16 screens of the existing app, audited the five that caused the most confusion, and redesigned from there, to 21 screens. Here's what the case study says we found and did, with my own label for each as UX or UI. The labels are my reading, not Dino's.

What we found or didUX or UI?Why
Home opened on a stack of amounts with nothing saying what to do first. The audit's first note was that the personal balance should lead, so Home now opens on it, with three actions under it.UXIt's about the order of information and what the user does first.
The groups switcher opened a sheet titled "Select Payment Card". The group and the card became one choice instead of two steps.UXOur case study calls them two confusing steps. It removes a step.
Each group pays from a joint card, so we drew the group as a card in Dino's green with its name, members and an Active tag.UIIt's how the idea looks, and it makes the first decision above visible.
The edit screen puts the original and current totals side by side, with an edit history showing who changed what.BothThe need (check a split) is UX. The layout that makes it checkable is UI.
One full-width button at the foot of every form.BothOne main action per screen is a UX rule. A consistent button is UI.

The fourth row is the one to notice: the line goes through the middle of a single decision. That's why the two roles need to be talking while the work is done, not only at the hand-off.

The rule for the whole redesign was: every number says whose money it is, and every screen has one obvious thing to do next. That's a UX rule. The green card, the type and the spacing are how the rule became something people could see.

How you'd tell which one is the problem

Problems usually arrive as a sentence, not a diagnosis. This is how I'd sort the common ones.

What people sayLikely the problemFirst thing to try
"People sign up and never use the main feature."UXMap the first-run path and find where they stop.
"It looks dated" or "it doesn't feel like our brand."UIUpdate the visual language and the components.
"Support keeps getting the same question."Usually UX, sometimes UICheck if the answer is on the screen at all, then whether it's readable.
"Every page looks slightly different."UIBuild a design system.
"People can't find the setting."UX firstCheck where it lives, then how visible it is.

Most real problems are a mix, so it's a first guess. The point is to ask "is the path wrong or does it just look wrong?" before commissioning anything.

A redesign with numbers

Fedica, a social media platform we redesigned over six months, is our clearest case with results. It had fifteen audience tools, a planner and an inbox, each on its own page with its own way of working, and most people found the one tool they came for and never the rest. We redesigned it as one workspace, 193 screens across desktop and phone.

After the redesign, our case study reports 36 percent more accounts using three or more tools and 42 percent less time to plan a week of posts. The case study doesn't split these numbers between UX and UI, and I won't either: the redesign was UX, UI and a design system together. What I can point to is how they fit. The flow connects the tools, and every tool shares one visual language, so a new tool is a new card, not a new product to learn.

Can one person do both?

Yes, and on small teams it's common. Justinmind gives the question a section of its own, and CareerFoundry says the order depends on whether one person or several handle it.

There are two sides. One person who does both keeps the flow and the look consistent. The other side, which Justinmind raises, is that one person wearing two hats can leave blind spots and miss details a second pair of eyes would catch. If you have one designer, ask for a review from someone else at the key points.

Our subscription plans are staffed by senior designers, and our pricing page says the hours cover design and build together.

What this means if you're hiring

If you're buying design, here's what I'd ask, in this order.

  1. Which of the two are you buying? "UI/UX" on a proposal can mean research and flows, a visual refresh, or both. Ask for a list of deliverables so you know. Wireframes and user flows are UX. Final screens, components and a style guide are UI. Prototypes sit on the line: the UX Design Institute has UX designers making them, Baymard lists prototyping apps as a UI tool, so ask who builds them.
  2. Does the price include testing? Ask what gets tested, with whom, and what happens to the findings.
  3. Who builds it? A design that never meets a developer drifts. The best handover is a real component set a developer can build from, not just a screenshot file.
  4. Is there a prototype? A clickable prototype shows a flow before it's built and is the cheapest place to find out it's wrong.
  5. What stays with you? Ask for the files, the components and the written rules, so the next designer doesn't start again.

On our UI and UX design services page we say the people who design the screens can write the code that ships them. And if you aren't sure how a prototype differs from an early product, our guide on MVP vs prototype covers it.

Which should you learn?

If you're asking for yourself, the UX Design Institute's advice is that both are valuable and one can't exist without the other. I'd start where your strengths are. If you like people, research and puzzles, start with UX. If you like type, colour and craft, start with UI. You'll pick up the other half along the way.

FAQ

UX is the whole experience of using a product and whether it solves the person's problem. UI is the visual and interactive layer they use: screens, buttons, type and colour.

The interface is part of the experience, yes. But UX also includes things the interface doesn't, such as whether the product does the job and what the company does when something goes wrong.

UX usually comes first, because you need to know the problem and the flow before you design screens. In practice they overlap and feed each other.

Yes. Many small teams do. It keeps the flow and the look in step, but one person can leave blind spots, so get a second review.

No. UX applies to anything a person uses, a kettle included. UI belongs to digital interfaces, and Baymard's examples include a phone screen, a game console button and a voice command.

Partly. Figma shows up in both job descriptions at the UX Design Institute. Baymard lists research tools, user-testing software and wireframing software on the UX side, and moodboards, style guides and prototyping apps on the UI side.

Yes. A good interface can't rescue a flow that doesn't work, and a good flow loses people if the interface is unclear or inconsistent.


If you've got a product that works but loses people, bring it to a call. We'll look at where they stop and tell you whether it's a UX problem, a UI problem or both.

About the author

Imran Khan, Founder & Creative Head

15 years of industry experienceFormer Head of Design at Day TranslationsFormer Creative Lead at SupersideWork at Superside for brands including Meta, Red Bull and Ray-Ban

Find him on-

Imran Khan, founder of Usarion

Book a call

Pick a time that suits you

Get in touch

Let’s build something amazing together

Project details

or write directly to hello@usarion.com

We use your details only to reply to you. Privacy policy

For product, interface and web-system work that needs clear direction and careful execution.

// CookiesWe use Google Analytics and Microsoft Clarity to see which pages help people. They only run if you say yes. Privacy policy