UX vs UI: What Each Really Means and What to Ask Your Designer

Many briefs ask for "a UX/UI designer" as if it were one job with a slash in the middle. Sometimes one person can do both, but the two disciplines answer different questions. If you do not know which question you are asking, you will hire the wrong person, judge the work by the wrong standard and pay for a redesign that does not fix the real problem.

UX: does it work for the person using it?

User experience (UX) covers the whole path a person takes to get something done: find a product, compare options, register, pay, get support. A UX designer asks: who is the user, what are they trying to achieve, where do they get stuck, and what is the shortest reliable route to the goal?

UX work is mostly invisible in the finished product. It shows up as research notes, user interviews, journey maps, information architecture (how content and menus are organised), user flows and wireframes: rough grey layouts that show structure without colour or style. A good UX designer spends a large part of their time talking to users and watching them use the product, not drawing.

Bad UX looks like this: a checkout that asks for the same data twice, a form that deletes everything when one field is wrong, a menu where nobody can find the delivery terms. You can have a beautiful screen with terrible UX.

UI: how does it look, read and respond?

User interface (UI) is the layer the person actually sees and touches: layout, typography, colour, icons, buttons, spacing, states (pressed, disabled, error, loading) and small animations. A UI designer turns the wireframe into a consistent visual system that fits the brand and is easy to read on every screen size.

Good UI is not decoration. It creates a visual hierarchy so the eye goes to the most important action first, makes buttons look like buttons, keeps contrast high enough to read in sunlight and keeps every screen consistent. The main output is a design system or UI kit: reusable components and rules that developers can build from.

Bad UI looks like this: grey text on a light grey background, five different button styles on one page, an icon nobody understands without a label.

How they work together

Think of a building. UX is the floor plan: where the doors are, how you get from the entrance to the kitchen, whether the stairs make sense. UI is the materials, colours, lighting and signs. A great floor plan with cheap finishes feels cheap; beautiful finishes in a confusing building still leave people lost.

In practice, the work moves in a loop rather than a straight line:

1. Research: interviews, analytics, support requests, a review of competitors.
2. Structure: user flows, information architecture, wireframes.
3. Visual design: the UI layer applied to the wireframes, plus design system components.
4. Prototype and test: a clickable prototype tested with a small group of real users.
5. Handoff: components, states and specifications for developers.
6. Measure and improve: completion rates, drop-offs, support requests.

Testing often sends you back to step two. That is normal, and it is much cheaper than finding the problem after launch.

One person or two?

For a small website, a landing page or an early-stage app, one strong product designer who can do both is usually enough. For a large online store, a banking app or a product with many types of users, you will want separate specialists, or at least a UX researcher supporting the designer.

The warning sign is a portfolio that shows only polished screens. Ask where the research is. Ask what changed after testing. A designer who cannot explain why a screen looks the way it does is probably doing UI only. That is fine if UI is what you need, as long as you say so in the brief.

Questions to ask a designer before you hire

1. "Walk me through one project from problem to result." Listen for research, decisions and measurement, not only visuals.
2. "How did you learn what users needed?" Interviews, analytics, usability tests, or assumptions?
3. "Show me the wireframe and the final screen of the same page." This shows whether they think in structure first.
4. "What did testing change?" Good designers can name a decision they reversed.
5. "How do you hand off to developers?" Look for a component library, documented states and clear specifications.
6. "How do you handle accessibility?" Contrast, font sizes, size of tap targets, support for screen readers.
7. "What will you need from us?" Access to users, data, brand guidelines and a decision-maker who replies on time.

What to put in the brief

Separate the two in your brief. For UX, describe the business problem, the users and the tasks they must complete. For UI, describe the brand, the platforms and your visual expectations. Name the metrics you want to move: completed registrations, checkout drop-off, support calls about a specific step.

Include the languages you need. In our region a product often has to work in two or three languages, and a Russian or Azerbaijani label can be much longer than the English one. Layouts designed only for English break when real text arrives, so ask the designer to test with every language from the start.

If you work with an agency or a freelancer, ask for research findings as a deliverable, not only screens. Those findings stay useful long after the project ends, and the next team you hire will thank you for them. If you are still looking for the right specialist, you can publish a brief on the platform and compare portfolios side by side.

The takeaway

Before you write "UX/UI designer" in your next brief, write one sentence for each: what the user must be able to do (UX) and how the product must look and feel (UI). If you can only fill in the second sentence, you are not ready to start the design. You are ready to start the research.