Imagine two appointment-booking apps. The first is visually polished, yet makes a customer call support whenever they need to change an appointment. The second lets them change it in seconds, but its labels are confusing and its controls difficult to distinguish. Neither is a great digital product.
The example captures the difference between user experience (UX) and user interface (UI) design, and why treating them as separate stages can produce disappointing results.
UX design concerns the experience of achieving a goal, including the underlying journey, its context and the way a service responds. UI design focuses on the interface through which people interact with that experience: its content hierarchy, visual language, controls, states and feedback. Their responsibilities overlap; the quality of one depends on the other.
UX: understand the task before designing the screen.
A team improving an appointment experience should first find out why people change appointments and what information they need. Does a person know where to find an existing booking? Can they see whether a change carries a cost? Are all users allowed to reschedule? What happens when availability changes while they are selecting a new time?
UX decisions shape the way the service works: how people navigate to their booking, what options are available, what information is requested and whether they can recover when something goes wrong. Research, journey mapping and usability testing can help reveal which decisions are well-founded and which assumptions need further evidence.
UI: make those decisions understandable.
Once the appointment choices have been defined, the interface makes them usable. Available and unavailable slots need to be distinguishable without relying on colour alone. A selected time should be clearly indicated. The primary action should communicate its consequence, and the interface must respond visibly when a request is processing or fails.
These are not simply aesthetic choices. A visual hierarchy tells people which information to consider first. A well-designed control communicates how it behaves. Typography and spacing help people understand the relationship between options. UI is the visual and interactive expression of the product’s underlying decisions.
One example, viewed from both disciplines.
Consider four moments in a rescheduling journey:
- Finding the booking: UX determines whether the service makes existing bookings discoverable; UI makes the entry point visible and recognisable.
- Selecting a new time: UX decides whether to present a calendar, a list or another flow based on needs and availability; UI makes the available dates, selected state, focus and feedback clear.
- Confirming the change: UX establishes what must be confirmed, including any cost or consequence; UI presents that information with a clear hierarchy and an accurate action label.
- Recovering from failure: UX provides a path if the chosen slot disappears; UI explains what happened and makes the next action easy to find, without losing relevant information.
Testing the finished experience can reveal either kind of problem. If people never find their booking, the information architecture may be at fault. If they find it but cannot recognise the change button, the interface may be failing. Sometimes both need to improve.
Do you need UX design or UI design?
The answer depends on the maturity of the product and the source of its problem. A new product with an uncertain proposition needs discovery and experimentation. An established service with frequent errors may need journey analysis and interaction improvements. A product with validated workflows but inconsistent screens may benefit from a stronger visual language and component system.
Once the problem is understood, choose an approach based on risk. Test the critical journey with representative users, inspect error and loading states, and check accessibility with keyboard and assistive technology. Then revisit the parts of the experience that the evidence identifies as weak. Avoid asking people merely which appearance they prefer; ask them to complete a realistic task.
Read more about how these disciplines fit into a broader product design agency engagement.
Design the experience as a whole.
At Dutch Lion, we believe the distinction is useful when it clarifies responsibilities, but unhelpful when it becomes a boundary. A product designer needs to understand how decisions about information, layout, interaction and technology influence one another.
The most successful interface is not just the one people admire. It is the one that helps them achieve what they came to do, confidently and with as little unnecessary effort as possible.
Explore Dutch Lion’s UX/UI and product design capabilities.


