Learning library / Product experience
User experience and user interfaces
The interface is what someone sees and operates. The experience is the whole path they take to get a result, including moments before and after the screen.
Explore this guideUI describes the controls. UX describes the journey.
User interface (UI) includes layout, typography, buttons, inputs, states, wording and feedback. User experience (UX) includes finding the product, understanding its promise, finishing the task, recovering from errors and returning later. A polished screen can still create a poor experience if it asks for the wrong information or hides the next step.
Consider a booking tool. The UI might have a clean calendar. The UX also includes whether available times are trustworthy, whether the user understands what will happen at the meeting, whether confirmation arrives, and how to reschedule.
Observe the real task before drawing the screen.
Begin with who performs the work, what triggers it, where it happens, and what people use today. Short interviews, observation and a walkthrough of an existing workflow can reveal handoffs and constraints that a feature list misses. Turn findings into a small number of scenarios and test them against a prototype.
Ask someone to try the task without coaching. Watch where they pause, what they expect to happen, and how they recover. Treat one person's behaviour as a clue rather than proof that all users behave the same way; repeat the check with different people and contexts.
Build for people who use the web differently.
Readable text, clear focus states, keyboard operation, understandable errors and meaningful labels help people navigate and complete work. Accessibility and usability overlap, but one does not replace the other. A product can feel easy to some users while excluding people who rely on assistive technology.
Use accessibility standards and tests alongside real user review. An automated checker can identify some issues, but W3C notes that no tool alone can determine whether a site is accessible. Check a meaningful path with a keyboard and assistive technology where relevant.
Read the source: W3C: Accessibility and usability, W3C: Accessibility evaluation.
Make repeated patterns dependable.
A small design system can define buttons, forms, spacing, text styles and messages so similar actions behave the same way. It reduces unnecessary choices during delivery and makes changes easier to review across multiple screens.
Consistency should support the task, not freeze every screen into the same template. A dense admin view, a public landing page and an urgent error state may need different emphases while retaining familiar controls and language.
Use this in a project
Questions worth answering together.
These make the idea concrete before the team commits to a design or release plan.
- 01
What task must people complete without explanation?
- 02
What information or feedback is missing at each step?
- 03
Can the path be completed by keyboard and on a small screen?
- 04
How will we know the design helped rather than merely looked better?
Further reading
Primary references.
Technical references for the concepts in this guide. The project advice and examples are our interpretation.
From concept to delivery
Bring us the question you are working through.
From Melbourne, Paradox Design develops bespoke web applications and operational software. We can help turn a product idea, existing workflow or technical concern into a clear next step.