Foldwren

UX and UI design: what is the difference?

A plain explanation of UX and UI design using a cafe analogy, why your project needs both, and the questions to ask a designer before you hire.

UX is how something works for the person using it. UI is what they see and touch while they use it. The two overlap constantly, and plenty of designers do both, but they are different jobs with different questions behind them.

If you are hiring someone to design a website or an app, it helps to know which one you are actually paying for.

The cafe analogy

Picture walking into a cafe you have never visited.

Within a few seconds you work out where to queue, where the menu is, whether you order at the counter or sit down, and where to wait for a takeaway. If all of that is obvious, you never think about it. If it is not, you stand in the doorway feeling slightly foolish, and maybe you leave.

That whole experience, from door to coffee in hand, is UX, short for user experience. Someone decided where the counter goes, how the queue flows, how many steps there are between wanting a flat white and holding one.

Now look at the details. The menu board's lettering, the colour of the cups, the little sign that says "order here", the feel of the door handle. That is UI, short for user interface. It is everything you see and physically interact with.

A cafe with beautiful signage and a confusing layout is frustrating. A cafe with a sensible layout and unreadable chalk scrawl on the menu is also frustrating. You need both.

What does a UX designer do?

UX work is mostly thinking, asking and arranging. It tends to happen before anything looks finished.

  • Finding out who the users are and what they are trying to get done.
  • Mapping the steps someone takes to complete a task, such as booking an appointment.
  • Deciding what goes on each screen and in what order.
  • Sketching rough layouts, often called wireframes, with boxes and labels and no colour.
  • Testing those rough versions with real people and fixing what trips them up.

The output often looks unimpressive. Grey boxes, arrows, sticky notes. Do not be fooled. This is where most of the expensive mistakes get caught, while they are still cheap to change.

What does a UI designer do?

UI work takes the agreed structure and makes it clear, consistent and pleasant to use.

  • Choosing type, colour and spacing so the important things stand out.
  • Designing buttons, forms, icons and menus so they look like what they are.
  • Making sure the design matches your brand without sacrificing readability.
  • Defining how things behave when tapped, loading, disabled or in error.
  • Checking contrast and text size so people with poorer eyesight can still use it.

Good UI is quieter than people expect. Its job is to help someone understand a screen at a glance, not to show off.

What goes wrong when you only get one?

UI without UX

This is the more common problem. You receive gorgeous mockups early, everyone gets excited, and the thing is built. Then customers cannot find the booking button, the enquiry form asks for nine fields nobody needs, and the app's main feature is three taps deep. It looks great in a portfolio and performs poorly in real life.

UX without UI

Less common, but it happens, especially with internal business tools. The logic is sound and every feature is in a reasonable place, but the screens are cramped, the labels are jargon, and everything is the same shade of grey. People can use it. They just do not want to, and they make more errors than they should.

Do you need two different people?

Usually not, for a small project. Many designers handle both and move between them naturally. What matters is that both kinds of thinking happen, in roughly the right order: work out what the thing needs to do and how people will move through it, then make it look and feel right.

On larger apps the roles often split, and you may also hear about researchers, content designers and interaction designers. Do not get bogged down in titles. Ask what the person will actually do and what you will receive.

Questions to ask a designer before you hire

These will tell you quickly whether you are getting UX, UI or both.

  1. How will you find out what our customers need? A good answer involves talking to or observing real people, even a few.
  2. What will we see before the visual design? Look for mentions of flows, wireframes or a rough prototype.
  3. Can you show a project where testing changed the design? Anyone who tests with users has a story about being wrong.
  4. How do you decide what goes on the first screen? You want reasoning based on user tasks, not personal taste.
  5. How will the design handle errors, empty screens and slow connections? These are the parts that separate a pretty picture from a working product.
  6. What do you hand over at the end? Ideally design files, a set of reusable components and notes a developer can follow.

If the answers are all about colour palettes and mood boards, you are buying UI. That may be exactly what you need for a brand refresh. For a new app or a site with booking, ordering or accounts, make sure the UX thinking is in the quote as well, and that it comes first.

Your order