Book a call
All writing

UX design vs UI design in 2026: what is the difference?

UX design works out how people finish a task in your product. UI design makes the screens and parts they do it with. On software, one team usually does both.

UX design works out how a task in your product should go: the steps, their order, what the person needs at each one and what happens when something fails. UI design makes the screens the task runs on, meaning the type, colour, layout and components, with every state each one can be in. The difference that matters when you hire is which one is failing. If people cannot finish the task, you need UX work first. If they can and the product looks dated, UI work may be enough.

Studios write “UX/UI” because on software the same people usually do both, and in our view that is how it should be bought. The checks below tell you which half your product needs most, so you can brief for it.

1. What does UX design cover, and what does UI design cover?

Nielsen Norman Group defines user experience broadly, as every part of a person’s dealings with a company, its services and its products, and keeps it separate from the user interface. When a software company hires for UX design, it usually means a narrower piece of that: whether people can finish the tasks the product exists for. Nielsen Norman Group calls that usability, how easily people complete a task with an interface.

What UX work hands over

  • User flows: each task drawn from where the person starts to where it succeeds or fails, with every point where the path splits.
  • Wireframes: plain drawings of each screen that settle what goes on it and in what order, before colour or type.
  • Prototypes tried by people who do the task, with notes on where they got stuck.
  • Decisions on structure: what the navigation holds, what the product calls things and which steps can go.

What UI work hands over

  • A visual language: type, colour, spacing and icons, with rules for using them.
  • Components such as buttons, inputs, tables and panels, each drawn in every state, including loading, empty, disabled and error.
  • Finished screens on your own content, at the sizes people use them.
  • A design system that holds all of it, in the design tool and, where it is in scope, in code.

The two lists meet in the states. Deciding that a failed import keeps the records that went through is a UX decision. Drawing the message that says so, and the button under it, is UI. Both have to be made before an engineer can build that screen.

UX design and UI design side by side, as they apply to a software product.
ComparedUX designUI design
The question it answersCan people finish the task?Is each screen clear and consistent with the rest?
What you getFlows, wireframes, tested prototypesA visual language, components, states, a design system
How it is checkedWatching people try the taskReviewing screens on real content against the system
Signs you need itPeople stall, ask support or give up partwayTasks get done, but screens look dated or mismatched
Who does it on softwareUsually a product designerUsually the same product designer
The right call whenThe flow is broken or not yet designedThe flow works and the surface has fallen behind

2. Which one is your problem?

Look at what people do in the product before you look at how it looks. A dated screen draws complaints because everyone can see it, while a task that fails quietly often costs more and is reported less. Run these checks on one task that matters to the business, such as setting up an account or sending the first invoice.

  1. Watch a few customers do the task on a call, without help, and note where each one pauses or asks a question. Nielsen Norman Group says five users are often enough to find many of the larger problems.
  2. Read the last month of support tickets about that task. Questions about how to do something point to UX.
  3. Find where people leave the task in your product data. A drop at one step is a problem with that step, however the screen looks.
  4. Open five screens side by side. Two different buttons for the same action, or tables that sort in different ways, mean the product has no shared parts, and that is UI work.
  5. Ask prospects who chose a competitor what put them off. “It looked old” in a demo is about the UI.
  6. Ask your engineers how they build a new screen. If they copy an old one and change it, the product needs a design system.

A worked example

Say you sell rostering software and your larger customers tell you it looks dated. In the sessions, managers publish the weekly roster without trouble, but staff who want to swap a shift open three menus before they find the option, and swaps are the most common subject in your support inbox. The managers’ complaint is about the UI. The staff have a UX problem, and it is the one costing you support time. A brief for a new look would leave it where it is.

3. Why does one designer usually do both?

On a software product the two are hard to pull apart, because most of the decisions sit inside a screen. Whether a table filters as you type or after you press a button, what a form keeps when it fails, where a warning appears before an approval: each is a decision about the task and about the screen at once. Hand the flows to someone else for the visuals and those decisions get made twice, or by nobody.

In our view one person or one team should own both for any given part of the product, and you should check that they are good at both. We describe our product design as UX and UI design for software, and the same people trace the task through the live product, draw the screens and states, and review the build with your engineers. Where the work includes a design system, we build it in code as well as in Figma, so the components your engineers use match the ones in the file.

Accessibility shows whether one team owns both. The W3C’s Web Accessibility Initiative describes it as people with disabilities being able to perceive, understand, navigate and interact with what you make. Contrast and text size are UI decisions. Reading order, labels a screen reader can announce and a way back from an error are UX decisions. A team that leaves accessibility to a colour check at the end has split the work.

4. What should you ask a studio so you are not sold a reskin?

A visual redesign is easy to sell, because the before and after look different in a pitch, and new screens on the old flows can still fail the same task. Ask these about your own product, and get the answers in the proposal.

Agree the measure before work starts, such as setups completed, and record where it stands today. A polished prototype alone is no evidence that the product got better.

5. What does it cost, and how long does it take?

We price UX and UI together as product design, from $10,000 a month. That is our own published price and says nothing about what other studios charge. A focused piece of product design on one area of a product usually takes four to six weeks. Both move with the tasks in scope, access to your users, the technical constraints and what you need handed over, and we agree the scope and price before work starts. Our product design cost guide has the rest.

6. When is the smaller job the right one?

Buy the UI work on its own when the checks say the tasks work. Redesigning flows your customers already know costs time and makes them relearn the product.

Some briefs need less than either. If one screen confuses people, redesign that screen. If the trouble is what a button or an error message says, change the words. When we review an existing product, the result can be a redesign or a smaller change to its structure, wording or behaviour.

UX work comes first when the checks show people failing a task, or when a new feature changes how the product works. Restyled screens would need reworking once the flow changes.

7. Questions

  1. UX design works out how a task in a product should go: the steps, their order, what the person needs at each one and how they recover from errors. UI design makes the screens the task runs on, meaning type, colour, layout and components with all their states. If people cannot finish a task, start with UX. If they can and the product looks dated, UI work may be enough.

  2. For most software products, hire one product designer or one team that can do both, because decisions about a task and the screen it runs on are made together. If people get stuck in your product, look for flows, testing and prototypes in their past work. If the tasks work, look for a visual language and a design system.

  3. Mostly. Product design is the usual name for UX and UI work on software done by the same people, and it often includes working with product priorities and engineering constraints. Titles vary between teams, so ask what the designer will hand over: flows and tested prototypes, finished screens and components, a design system and review of the build.

  4. Rarely on its own. If people leave at one step, watch a few of them try it and read the support tickets about it. A step that asks for something people do not have to hand, or fails without saying why, is a flow problem that new colours leave in place. Fix the flow first and measure the step before and after.

  5. At Refract, product design covering both UX and UI starts from $10,000 a month, and a focused piece of work on one area of a product usually takes four to six weeks. That is our own published price; other studios set their own. What moves it is how many tasks are in scope and what you need handed over.

Sources and further reading

Written on by RefractStudio notes

Keep reading

Working on something like this?

Tell us where it’s stuck. We’ll tell you what we’d do first, and whether we’re the right team.

Most teams start with a call, then a sprint or an audit.

Book a call
  • Angus
  • James
  • Naiya
  • Lilian
  • Luca
  • Minh
  • Jorge
  • Toffee

The people you’d work with, from the first call to launch