UX, UI, and why confusing them costs you
Most people think design is the part where you choose colours. That is decoration. Design is deciding what happens when someone taps the button — and whether they can find the button at all.
The difference that actually matters
UX is how it works. UI is how it looks. You need both, but they fail differently.
| Question it answers | When it's wrong | |
|---|---|---|
| UX | Can I do the thing I came to do? | The user gives up and leaves |
| UI | Does this feel trustworthy and clear? | The user hesitates, then leaves |
Open your banking app and try to send money to a new person. Count the taps. Notice where you paused. Every pause is a UX decision someone made — or failed to make.
Why Nigerian products are a good place to learn
Look at Paystack's checkout versus a bank portal that still asks you to pick a branch from a dropdown of 200. Same country, same users, same regulations. The difference is entirely design decisions.
That is good news for you: the bar in many local products is low, and the gap between "works" and "pleasant" is where you'll get hired.
What a designer actually produces
Not a pretty picture. A designer hands over:
- Flows — the screens in order, including what happens when something goes wrong
- Components — a button defined once and reused, not redrawn 40 times
- Specs — spacing, sizes and states a developer can build from without guessing
By the end of this course you'll have all three for a real product, in a portfolio a hiring manager can open.
Try it yourself
Open any app you used today. Screenshot one screen. Write down:
- What is this screen for, in one sentence?
- What is the single most important action on it?
- Is that action the most visually obvious thing? If not, what is?
That third question is the whole job.