WalkUp Digital
Guide

UI vs UX design: what is the difference?

UI and UX are written together and usually designed together, yet they answer different questions. This guide explains what each covers, what each delivers, and how both show up in two products we designed and built, Kalimenu and AppInsure.

What is UX design?

UX stands for user experience: everything a person goes through while trying to get something done on a website or in an app, from the first screen until the task is finished or abandoned. UX design shapes that experience on purpose. It starts with questions about people rather than pixels: who arrives, what they came to do and what could stop them.

On a business website the answers are usually concrete. A visitor wants to know whether you offer what they need, whether they can trust you and how to get in touch. UX design decides which pages exist, which question each answers first, what the navigation calls things and how many fields the enquiry form really needs. None of this is visible as design. All of it is felt when it is wrong.

What is UI design?

UI stands for user interface: the screens, controls and text a person sees and touches. UI design decides how each screen is laid out, which typefaces, sizes and colours are used, what a button looks like and how it responds when pressed, disabled or waiting for a result. It also covers the states that are easy to forget: an empty list, a slow connection, a form that has failed.

Good UI is consistent before it is attractive. The same action looks the same everywhere, the main action on each screen is the easiest to find, and the visual language matches the brand the business already has. Where a company has a logo, colours and typography, the interface puts them to work on screen; our guide to what a brand identity package includes shows where identity ends and interface begins.

UI vs UX: what is the difference?

The simplest way to separate them is by the question each answers. UX asks whether the product does the right thing for the person, in the right order. UI asks whether each screen presents it clearly and behaves predictably. Take an online shop's checkout. UX decides that it has three steps, that delivery details come before payment and that a customer can buy without creating an account. UI decides how those steps look, which button is primary and how a mistyped card number is pointed out.

Each can fail without the other. A polished interface on top of a confused structure still loses people, only more elegantly. A sound structure behind a cluttered or illegible interface loses them too, because visitors judge a business partly by what they see. That is why the two are written as UI/UX and are often handled by the same people from start to finish.

Some ground belongs to both: the wording of buttons and error messages, accessibility, and the way a page behaves on a small phone screen.

What UX delivers and what UI delivers

UX deliverables come first. Research gathers the business objectives, the tasks people come to complete and, for an existing site, evidence of where they struggle: analytics, the questions customers ask by phone, abandoned forms. The page structure, or information architecture, sets out which pages exist and how they are grouped. User flows map the steps through each important task. Wireframes show each key screen in plain greys, so hierarchy and content are agreed before anyone discusses colour. A clickable prototype joins them so the flows can be tried, by the client and, where the project includes it, by real users.

UI deliverables build on those decisions: the final screen designs for mobile and desktop, a library of components such as buttons, form fields, cards and navigation with every state drawn, and named values for colour, spacing and type, often called design tokens. On a larger product these are gathered into a design system, one reference the next designer or developer can extend without redrawing what exists. Our UI/UX design service lists what we hand over and in what form.

How do UI and UX work together in a project?

In order, with overlap. Structure is settled first because it is cheapest to change on paper: moving a step in a wireframe is quick, in a finished design it means redrawing several screens, and in finished code it means rebuilding them. Visual design then starts from the agreed wireframes. The prototype is where the two meet, because it is the first version people can use rather than look at.

In practice the work loops back. A UI problem often turns out to be a UX one: a menu that will not fit on a phone usually has too many items, and the fix is to regroup the pages, not to shrink the type. UI can also undo a UX decision: a step that worked in a wireframe fails if its button looks disabled. Reviewing the prototype on a real phone catches many of these problems before development.

Development is the last link. Designs handed over with components, states and spacing defined are built as designed; flat pictures are left to interpretation. When design and build sit with the same studio, as in our web development work, the prototype carries straight into the build instead of being handed to another team to reinterpret.

Does a small business website need UX design?

Yes, scaled to the site. A five-page website still has tasks: find the service, check that the business is credible, make contact. UX work for it may be a page structure, one flow for the enquiry and wireframes of the home page and one service page. An online shop needs far more: search and filters, product pages, basket, checkout and customer accounts, each with its own flow. An app with several types of user, each seeing different data, needs the most.

That difference is also what moves the cost. Compare a five-page site with one form and a shop with payments: the second has more templates, flows and states to design, and more to test. Other factors are the number of user roles, the languages of the interface, whether a design system is needed and whether usability testing with participants is in scope. Our guides on what affects the cost of a website and building an online shop go through those decisions.

UI and UX in Kalimenu

Kalimenu is our QR menu with ordering at the table. Its central UX decision is stated on its home page: the guest scans the code and the menu opens straight away in the language of their phone, with no app and no account. Two steps that would stand between a seated guest and the menu are simply not there.

The ordering flow is designed for the staff as much as for the guest. An order reaches the waiter's phone with a notification and goes to the kitchen only once the waiter has approved it, so a mistaken order is caught before anything is prepared. Drinks go to the bar and food to the kitchen, each on its own screen.

The UI is where venues differ. Each applies its own logo, cover photo, colours and typeface, or a ready-made theme, and sees every change at once, the way guests will. The flow stays the same in every venue; the look is the venue's own. That is the UI/UX split inside a single product. The full account is in how we built Kalimenu.

UI and UX in AppInsure

AppInsure is our iOS app that insurance intermediaries offer to their clients under their own logo. The UX starts from its two audiences: the client who uses the app and the intermediary who decides to offer it. The website gives each a page of their own, and the client's page says, before anything is downloaded, what is needed to begin: the intermediary's invitation code and the client's tax number.

Another decision concerns a stressful moment. After a breakdown or an accident, the app knows which roadside assistance number belongs to that particular vehicle and calls it directly, so nobody has to look it up when it matters. The interface supports this with short, plain wording: a policy is either in force or expired, and getting started is set out in three numbered steps. The AppInsure case study covers the rest, including how the app handles personal data.

Accessibility and search: where UI and UX meet

Accessibility is decided in design. The W3C's Web Content Accessibility Guidelines (WCAG 2.2) set testable criteria, and several of them are design decisions. At level AA, normal-size text needs a contrast ratio of at least 4.5:1 against its background. Colour must not be the only visual means of conveying information, so an error marked only in red is not enough. When a form detects an input error automatically, the field must be identified and the error described in text. At level AA, targets for a pointer or a finger must be at least 24 by 24 CSS pixels, with defined exceptions. Separately, in the EU the European Accessibility Act (Directive (EU) 2019/882) applies to e-commerce services provided to consumers after 28 June 2025; microenterprises that provide services are exempt from its accessibility requirements.

Google's documentation on page experience covers related ground. It says Google's core ranking systems look to reward content that provides a good page experience, and its self-assessment questions ask whether content displays well on mobile devices, whether pages avoid intrusive interstitials and whether visitors can easily tell the main content apart from the rest. Those are UI and UX decisions. Google also says it always seeks to show the most relevant content, even when page experience is sub-par, so design supports search visibility but does not replace content. Our guide to technical SEO covers Core Web Vitals.

How to prepare for a UI/UX project

Bring answers about people rather than preferences about style. Who uses the website or app, and which three tasks matter most? What do customers ask most often? If a site exists, where do visitors leave and which pages bring enquiries? Which brand assets exist, and which systems must the product connect to?

With those answers, a conversation sets the scope: how many templates or screens, which flows, whether a design system is needed and whether testing with users is included. We then quote the project in writing before work begins. You can start through the contact page.

Questions

Frequently asked.

What does a UI/UX designer do?

They turn what a business knows about its customers into screens that can be built. The work runs from research and page structure, through user flows, wireframes and a prototype, to the visual design of every screen and its components, and ends with a hand-off developers can build from.

Is UX more important than UI?

Neither works alone: UX decides whether the product does what people need, and UI whether they can see and use it. If one must come first, settle the structure: a clear flow with plain visuals works, refined visuals on a confused structure do not.

Is UI/UX design the same as web design?

Not quite. Web design is a looser term that usually includes UI/UX and sometimes the build. UI/UX design names the planning and screen design specifically; web development turns the designs into a working site with a content management system, forms and hosting.

What is a design system?

A shared reference for the parts an interface is built from: colours, type sizes, spacing, and components such as buttons and form fields with all their states, plus notes on their use. It keeps new pages consistent and later changes faster. Small brochure sites rarely need a full one; growing products usually do.

Can the UI change without changing the UX?

Yes. A visual refresh can keep the structure and flows, and if page addresses and content stay the same it carries less risk for search. If visitors struggle with the structure itself, a new look will not solve it; the work has to start from the flows.

Does good UI/UX improve Google rankings?

Not on its own. Google says its ranking systems look to reward a good page experience and use Core Web Vitals, but it always seeks to show the most relevant content. Good design helps people use what they find; nobody can guarantee a position in the results.

Start a project.

Contact the studio