Three UX Basics: Clarity, Feedback, Hierarchy
Three simple habits that make any build easier to use — plus your choice point for today's project.
🎯 Three Habits, Not a Design Degree
You don’t need to study design to build something that feels good to use. Three habits cover most of it:
Clarity — there’s one clear main action, not six competing buttons. Someone landing on your page for the first time should know instantly what to do.
Feedback — something visibly happens when you click. A color change, a message, an animation. Silence after a click makes people think it’s broken, even when it worked.
Hierarchy — size and color show what matters most. Your main button should look more important than a small footer link, because it is more important.
If every element on the page is the same size, weight, and color, nothing stands out — including the one action you actually want people to take. Pick your single most important action and make it visually louder (bigger, bolder, brighter) than everything else. That’s hierarchy doing its job.
👀 See It Applied
Your instructor will pull up yesterday’s boarding-pass demo and run it through this lens live — pointing out one thing that’s already clear, one place that’s missing feedback, and one fix that improves hierarchy. Then they’ll prompt Gemini for that one fix, live, so you can see the before and after.
🔀 Choice Point
Before you start building, decide:
- Iterate yesterday’s project — apply today’s PM + UX lens to what already exists, and save it as the next version number (for example,
maria_day1_v1.htmlbecomesmaria_day2_v2.html) - Start fresh with a new project, applying the lens from the very beginning — version resets to v1 under a new file name
Today’s build is themed: “Clear the Runway” — a fast, aviation-flavored mini-game (think Whack-a-Mole): aircraft pop into random slots on the screen and you click them before they vanish. If you’re iterating yesterday’s project instead, that’s completely fine — just make sure your PM answers (who it’s for, the one thing it does well) are clear before you touch Gemini.
You liked yesterday's boarding-pass page and want to keep working on it today instead of starting Clear the Runway. What's the correct choice, and what should the filename look like?
Reveal Answer & Explanation
That’s a valid choice — iterate — and the filename bumps to today’s version, keeping the same name and day-1 origin visible in the trail.
If your file was maria_day1_v1.html, today’s save becomes maria_day2_v2.html. The important part isn’t which project you choose — it’s applying today’s PM and UX lens to it, and never overwriting yesterday’s saved version.
⏭️ Up Next
Before you touch Gemini: what to do when your build inevitably breaks. Then you build — with the PM lens, the UX lens, and a debugging loop all guiding your prompts.