What Is UI vs UX — And Why the Term Was Coined to Escape the Word «Interface»

Here's a funny bit of history. The word "UX" wasn't invented because someone needed a trendy synonym for "interface." It was invented to get away from that word.
Don Norman introduced the term at Apple in 1993, and later spelled out why: "I invented the term because I thought human interface and usability were too narrow." He wanted a word that covered everything — industrial design, graphics, physical interaction, even the manual in the box.
So by design, UX is exactly the part that doesn't fit on the screen. Let's find the line.
UI is what you see. UX is what happens
UI (user interface) is the surface. Buttons, fonts, spacing, colors, icons, the little press animation. Everything you look at and tap.
UX (user experience) is the whole path a person takes toward their goal. Nielsen Norman Group defines it like this: "user experience encompasses all aspects of the end-user's interaction with the company, its services, and its products."
Notice what's missing from that definition: the screen. What's there instead is the company and its services. Waiting on support is UX. The wrong email landing in your inbox. The moment you realize you have to create an account just to press one button.
The example that makes the difference obvious
NN/g uses a case that lands instantly. Picture a movie review site. The interface is flawless: search is instant, the cards look great, everything is thumb-friendly. Great UI.
Now you go looking for independent films — and they simply aren't in the database. Your experience is ruined. No amount of padding or typography saves it.
That's the whole point: the UI can be perfect while the UX fails. The reverse happens too, just less often — a clunky service that does exactly what you need in two clicks.
Worth adding: "usability" is a third word, and it sits closer to UI. NN/g calls usability "a quality attribute of the UI" — is it easy to learn, is it efficient. UX is the broader idea.
Why AI is great at UI and nearly blind to UX
This is the practical part, and the reason the distinction is worth keeping in your head at all.
Ask a model for "a profile screen" and you'll get decent UI. Spacing aligned, buttons in place, tidy. It has seen millions of profile screens and learned what they look like.
But it has never seen your UX. The model doesn't know:
- why your user opened this screen in the first place;
- what they did a minute earlier and where they go next;
- that 80% of your people arrive on a phone, on a commute;
- that your signup takes four steps and half of them quit on step three.
None of that is in the prompt, so as far as the model is concerned it doesn't exist. It hands you the most probable screen, not the most suitable one. Hence that familiar feeling: looks nice, awkward to use.
So split the work accordingly. UI can be delegated almost entirely. UX is your half — you're the only one who has met an actual user.
What to do with this in practice
Three moves that turn this from terminology into a working habit.
- Start with the task, not the screen. Not "I need a settings page" but "someone wants to turn off notifications and leave." The screen is a consequence.
- Count steps, not pixels. The cheapest UX win is removing one step. The most expensive is recoloring a button and hoping.
- Give the model structure and states, not taste. How to phrase that is walked through in how to describe a UI to AI. And to stop the interface drifting screen to screen, you want a design system.
A quick honesty check: if you can't state your user's task in one sentence, you don't have UX yet. You have a mockup.
UI or UX — which matters more?
Wrong question: they aren't alternatives. UI is part of UX, not its rival. But if you're truly cornered, UX wins — nobody sticks with a beautiful product that's painful, while plenty of people happily use a plain one that works.
Do I need a designer if I'm building solo?
Not necessarily. AI tools cover the UI half pretty well. The UX half stays with you — you can't buy it, because it's about your specific users.
Is UX only about websites and apps?
No. By Norman's definition it covers the whole experience: packaging, support, emails, returns. Digital products just make the gap between "pretty" and "usable" visible fastest.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





