UX or UI: what's the difference?

3 min read
Illustration split between a screen-flow plan (UX) and a polished interface (UI)

Summary: UX (user experience) is about how people use a product: whether they understand it, find what they're looking for and complete the task. UI (user interface) is the visual and interactive layer: colors, typography, components, button states. UX defines the path; UI makes that path clear and pleasant. A good project needs both.

The acronyms always appear together, UX/UI, giving the impression they're the same thing. They aren't. The ISO 9241-210 standard defines user experience as a person's perceptions and responses resulting from the use of a product, system or service, a broader concept than the screen.

The kitchen analogy

UX is the floor plan: where the sink, stove and fridge go so you can cook without walking in circles. UI is the finish: cabinets, faucets, handles, lighting. A beautiful kitchen with the fridge far from the stove is tiring. A well-planned ugly kitchen is one nobody wants to use.

What UX design does

  • Research: interviews, usage data analysis, conversations with support and sales.
  • Information architecture: organizing content, menus, section names.
  • Flows: the path to request a quote, buy or book, with the fewest steps.
  • Wireframes and prototypes: screen sketches, first without styling, to validate structure.
  • Usability testing: real people trying to complete tasks on the prototype.

What UI design does

  • Visual system: palette, typography, spacing, grid, icons, consistent with the brand identity.
  • Components: buttons, forms, cards, menus, with all states (default, focus, error, disabled).
  • Visual hierarchy: what draws attention first on each screen.
  • Visual accessibility: minimum contrast of 4.5:1 for normal text, visible focus, adequate touch targets (WCAG 2.2).
  • Design system: a documented component library that keeps screens and developers consistent.

Quick comparison

UX vs. UI
AspectUXUI
Central questionCan people do what they need?Does the interface communicate that clearly?
DeliverablesResearch, flows, wireframes, prototypes, test reportsFinal layouts, style guide, components, design system
MetricsTask completion rate, time, errors, conversionConsistency, legibility, accessibility compliance

What a project looks like

  1. Understanding the business and audience.
  2. Analysis of the current site (Analytics data, observed problems).
  3. Architecture and main flows.
  4. Wireframes and clickable prototype.
  5. User testing and adjustments.
  6. UI: final layouts and components.
  7. Development support and post-launch measurement.

Signs your site needs UX/UI

  • Lots of visits, few contacts.
  • Customers ask on WhatsApp about things already on the site.
  • People abandon the cart or form midway.
  • Each page looks like it belongs to a different company.
  • People using screen readers or keyboards can't use it.

We gathered practical tweaks in 7 UX tweaks that increase quote requests. For a full project, see our UX/UI design services, applied to websites, stores and apps.

Sources and references

Frequently asked questions

Are UX and UI done by the same person?

On small teams, often yes. On larger projects there are specialists in research, interaction and interface.

Which comes first, UX or UI?

UX. Structure and flows are defined first; then the visual finish is applied. Starting with visuals usually causes rework.

Is a design system only for large companies?

No. Even a simple guide to colors, fonts and buttons prevents inconsistencies and speeds up future changes.

Is accessibility UX or UI?

Both. UX ensures flows work for everyone; UI ensures contrast, visible focus and legible components.

Your website looks great but doesn't convert?

We analyze the experience and redesign the screens to lead visitors to contact you.

Read also

Written by Mário Moreno, founder of Agência hetsi, which has been building websites and handling digital marketing for businesses in Brazil and abroad since 2000. Mário Moreno on LinkedIn