Real product screens, each with one design problem. Read the challenge here, make the call in UX Quest, then see why the best answer works and which UX law explains it.
Six areas where small design calls decide whether people stay, pay or leave.
A hidden cart, identical plans, a Pay button that looks like a tag.
See the challengesToo many fields, rejected phone numbers, five address boxes.
See the challengesButtons out of reach, targets too small, taps with no reply.
See the challengesContrast, colour, type scale, spacing and alignment.
See the challengesFirst screens, empty checklists, tours and drop-off.
See the challengesWhen AI should act, ask, explain or hand over to a human.
See the challenges21 challenges, free with an account. Read the problem here, then solve it in UX Quest and see why the strongest answer works.
A settings toggle waits for the server before it flips, so for ~700ms after a tap nothing moves. Users assume it missed and tap again — silently undoing their own change.
A notes app took off on 6.7-inch phones, but 'New note' lives top-right — the one corner a thumb can't reach one-handed. Reviews are piling up about how awkward it is one-handed.
A product card's caption is a tasteful light grey on white — crisp in Figma, gone the instant it's read outdoors or by low-vision eyes. It just failed an accessibility audit.
A teammate's profile card uses gaps of 6, 11, and 13px — no scale, just values nudged by eye. It looks subtly broken and no one on the team can say exactly why.
A landing page sets its headings at 14/15/16/17/18/19/20px — every level a pixel apart. With no real jump between them, the eye finds no anchor and skims straight past the H1.
A checkout's 'Continue' button ships with 4/8px padding — technically a button, visually a tiny chip. It reads as skippable at the exact step it should feel inevitable.
A SaaS team shipped a dashboard using all eight brand colors at equal strength. Everything competes for attention, so nothing wins — users can't find the primary action in the noise.
An editing toolbar packs 24px icons 4px apart, with 'Delete' right beside 'Edit'. People keep destroying work they only meant to change.
A search screen returns in ~600ms but hides it behind a centered, blocking spinner. The wait is short; the frozen screen makes it feel broken.
A chat app's settings screen lists six switches in one flat list. Support keeps hearing that people turn off the wrong ones, and testers can't tell which switches belong together.
A streaming app's Trending row fits three cards exactly on the screen. Analytics show almost nobody swipes it, so the other eight titles go unseen.
An app's loading spinner is a thick, complete ring. In the redesign, the team wants it lighter and still instantly recognisable, even at small sizes.
A welcome screen shows a row of badges, three small illustrations, carousel dots and four buttons. New users bounce, and testers say they don't know where to start.
A pricing page shows three plans with identical cards. Most visitors pick the cheapest, even though the middle plan fits most teams best.
A clothing shop's filter screen shows size, colour and fit as rows of chips. The chips that are switched on look almost exactly like the ones that are off, so shoppers can't tell what is applied and keep tapping to check.
A clothing shop's new app moved the cart to the bottom-left corner and gave it a custom icon so the app would look different. Since the redesign, support gets messages asking where the cart is, and fewer people reach checkout.
A settings screen shipped with 'Save changes' in pale grey on white — about 1.6:1. The one control that commits the user's work is the one they can't find.
A music player's Skip control is a 28pt icon squeezed into the transport bar. Driving or walking, users jab at it two or three times before it catches.
An article renders its headline at the same size and weight as the paragraph below it. Readers arrive mid-page with no idea where the story actually begins.
An assistant booked a non-refundable 06:12 train after an ambiguous request for a 'flexible morning trip'.
A calendar agent moves an important meeting based on incomplete context.
Practise on real screens: look at a product, decide what is wrong and why, then compare your answer with the reasoning. Short, daily challenges like these build that judgment faster than reading alone.
Yes. UX Quest has 21 Beginner challenges, free with an account, each built around one common mistake and the UX law that explains it.
No. Every challenge runs in the browser on a phone or laptop. You decide what to change and get instant feedback.
They train the reasoning interviewers ask about: why a design works and which principle backs it. UX Quest also keeps a Decision Card of your reasoning, so you can show how you think.