Skip to content
Design Academy My progress

Stage 0 · Lesson 1 of 8

What UI design is and what UX design is

The two terms everyone mixes up, explained with one everyday product.

  • Beginner
  • 25 min
  • 5:45 video
  • 3 check questions
  • Exercise: 30 min
0:00 5:45

WatchDesignCourse5:45

What is UI vs. UX Design? A Practical Example in Under 6 Minutes

A short, concrete walk through the same product treated as an interface problem and as an experience problem. Watch it before reading the lesson: it gives you the vocabulary the lesson then sharpens.

By the end of this lesson you can

  • Define user interface (UI) design and user experience (UX) design in plain language.
  • Explain why a product can have a beautiful UI and a poor UX, or the other way round.
  • Identify UI and UX decisions in a product you use every day.

The idea

User interface (UI) design is the design of the parts of a product that people see, hear and touch: screens, buttons, text, icons, colours, layout and the way those elements respond when someone uses them. If you can point at it on a screen, it is part of the UI.

User experience (UX) design is the design of the whole experience a person has while trying to get something done with a product. That includes the UI, but also the steps a task takes, the order of those steps, the words used, how long things take, what happens when something goes wrong, and even what happens away from the screen, such as an email receipt or a phone call to support.

A useful way to hold the difference: UI is what the product looks like and how its controls behave. UX is whether the person achieved what they came to do, and how it felt to get there.

The two are not opposites and they are not separate jobs on most teams. UI is one of the most visible tools a designer uses to shape the experience. A designer who changes the order of a checkout, removes an unnecessary form field and rewrites an error message is doing UX work. A designer who makes the "Pay" button clearly the most important thing on the screen is doing UI work in service of the same experience.

Why the terms get confused

Job adverts often say "UI/UX designer" as if it were one word, and many people use "UX" to mean "the design of an app". That is fine in conversation. What matters for your learning is to notice the different questions each one asks:

  • UI questions: Is this readable? Does this look tappable? Is the most important action obvious? Is it consistent with the rest of the product?
  • UX questions: Who is this for? What are they trying to do? What gets in their way? How many steps does it take? What happens if they make a mistake? Did they succeed?

Why it matters in real projects

Teams waste a lot of effort polishing screens that solve the wrong problem. Knowing the difference helps you ask the right question at the right time. Early in a project, the useful questions are almost all UX questions: who, what, why and in what order. Later, UI questions matter a great deal, because an unclear button or unreadable text can break an otherwise good flow.

It also helps you describe your skills honestly. A portfolio of attractive screens shows UI skill. A case study that explains how you found a problem, shaped a solution and checked that it worked shows UX skill. Most employers want to see both.

A realistic example

Imagine a city bus ticket app. A commuter called Mina needs to buy a single ticket while walking to the bus stop.

  • A UI problem: the "Buy ticket" button is light grey on white, so in bright sunshine Mina cannot tell it is a button. The fix is a UI fix: stronger contrast and a clearer button style.
  • A UX problem: the app asks Mina to create an account, confirm her email and add a card before she can buy anything. The bus arrives while she is still typing. The screens might be beautiful, but the experience fails. The fix is a UX fix: allow guest purchase with a saved payment method from the phone's wallet, and offer an account afterwards.
  • A problem that is both: after paying, the ticket appears as small text in a list of past orders. The driver needs to see it quickly. The experience needs a "show ticket" step at the right moment (UX), and the ticket needs to be large, high-contrast and recognisable at a glance (UI).
UX covers every step of the journey. UI is the part that happens on a screen, so it is one of several tools for shaping the experience.

Step by step

  1. Pick a product you used today

    Choose something ordinary: a banking app, a food delivery app, a government website. Ordinary products teach more than famous ones because you already know where they annoy you.

  2. Write the goal in one sentence

    For example, "Pay my electricity bill before the due date." The goal is the person's, not the product's. "Use the payments feature" is not a goal.

  3. List the steps you took

    Include steps off the screen: finding the bill, looking up an account number, waiting for a confirmation email. Number them.

  4. Mark each frustration as UI or UX

    Next to each step, note anything that slowed you down. Label it UI if it was about how something looked or behaved on screen, UX if it was about the steps, order, wording or missing help. Some will be both.

  5. Suggest one fix for each

    Keep it short. "Make the due date bigger" is a UI fix. "Show the amount due on the home screen so I do not need to open the bill" is a UX fix.

Common mistakes

  • Mistake Thinking UX means wireframes and UI means colours.

    Instead Both are about outcomes for people. Wireframes and colours are just artefacts. Ask what question each artefact answers.

  • Mistake Judging a product only by screenshots.

    Instead Screenshots show UI. To judge UX you need to know the goal and try the task, ideally watching someone else do it.

  • Mistake Treating UX as an extra phase before "real" design.

    Instead UX thinking continues through the whole project, including after launch, when you learn how people actually use what you built.

Check your understanding

Choose an answer, then check it. There is an explanation either way.

Question 1 of 3A sign-up form has clear labels and good contrast, but asks for 14 pieces of information before the user can see the product. What is the main problem?
Show answer

A UX problem with the steps and what is asked for. The visuals are fine. The experience asks for too much, too early, which is a UX decision about the flow and content.

Question 2 of 3Which of these is a UI decision?
Show answer

Making the primary button visually stronger than the secondary one. Button styling and emphasis are part of the interface. Guest checkout and receipts shape the wider experience.

Question 3 of 3Can a product have a great UI and a poor UX?
Show answer

Yes, a polished interface can still make a task slow, confusing or impossible. Beautiful screens can sit inside a flow that does not match what people need. The bus ticket example shows this.

Practice exercise

Exercise · about 30 min

UI or UX? Audit one everyday task

Use the walkthrough above on one product you used this week. Work on paper or in a document; no design tool is needed.

Steps

  1. Write the goal in one sentence from the user's point of view.
  2. List every step, including steps that happen off screen.
  3. Mark at least five frustrations or moments of hesitation, labelled UI, UX or both.
  4. Write one specific, realistic fix for each.
  5. Choose the single fix you think would help most and explain why in two sentences.

Deliverable

A one-page audit: goal, numbered steps, labelled frustrations, fixes, and your top recommendation.

Self-assessment

Tick each item when it is true of your exercise. Be honest; this is for you.

5 items

Summary

  • UI is what people see and interact with. UX is the whole experience of trying to get something done.
  • UI is one of the main tools for shaping UX, so the two overlap heavily.
  • Early project questions are mostly UX questions; UI quality becomes critical as the design takes shape.
  • You judge UI by looking. You judge UX by trying the task and watching others try it.

Further reading

Third-party sources, chosen for reliability. They open in a new tab.

Your notes

Marking complete updates your course and roadmap progress.

Back to Orientation and design foundations Roadmap