Article4 min readUpdated
UI vs UX design: the difference, explained without jargon
UX is how a product works, UI is how it looks and feels. A simple explanation with examples, and why a product needs both.
By Tithi Mondal, UI/UX Designer
Clients often ask whether they need a UI designer or a UX designer. The honest answer is that a product needs both kinds of thinking, and on most projects one person does both.
A simple way to see it
Think about ordering food at a restaurant.
- UX is the whole visit. How quickly you are seated, whether the menu is easy to understand, how long the food takes, how you pay.
- UI is the menu card itself. The paper, the type, the photographs, whether the prices are easy to find.
A beautiful menu in a restaurant with forty-minute waits is good UI and bad UX. A fast, friendly place with a photocopied menu is good UX and weak UI. You remember the places that got both right.
What UX design involves
- Talking to users and studying what they do today
- Listing the tasks the product must support
- Drawing user flows: the path from opening the app to finishing a task
- Deciding what goes on each screen and what is left out
- Wireframes, which are plain layouts without colour
- Testing a prototype with real people and fixing what confuses them
The output is a structure. It answers the question: can people get things done?
What UI design involves
- Choosing typography, colour and spacing
- Designing buttons, forms, cards and navigation
- Building a component library so everything is consistent
- Designing states: pressed, disabled, loading, empty, error
- Icons, illustrations and small animations
The output is the finished look. It answers: does this feel clear, trustworthy and pleasant?
Where they overlap
In practice the two are never fully separate. The size of a button is a UI decision that changes how easy it is to tap, which is UX. The number of steps in checkout is a UX decision that changes how the screens must be laid out, which is UI. That is why they are usually written together as UI/UX.
A real example
On a seller app I designed for a marketplace, sellers had to verify a phone number, an email address, a tax number and a licence before listing anything.
- The UX work was deciding the order, letting sellers save and continue later, and showing progress so nobody felt lost.
- The UI work was the progress bar, the green "verified" ticks and a success screen that made finishing feel like an achievement.
Remove either and the flow fails: sellers either give up halfway, or finish without feeling confident.
Which one do you need?
- New product: start with UX. Structure first, style second.
- Product that works but looks dated: mostly UI, with a quick UX review.
- Product people abandon: UX. A new coat of paint will not fix a confusing journey.
If you are not sure which applies to you, send me a link or a few screenshots and I will tell you what I see.
Frequently asked questions
Is UI or UX more important?
Neither works alone. UX makes a product usable and UI makes it clear and trustworthy. For a new product, UX decisions come first because they shape every screen.
Can one designer do both UI and UX?
Yes. On most startup and small business projects one UI/UX designer handles research, flows, wireframes and visual design.
- UX Basics
- UI Design