Four friends are on a weekend trip to Goa and keep paying for things for each other. Design how they add a shared expense and settle up at the end, without anyone doing maths.
Friends in their twenties on a short trip, paying on their phones, who care more about fairness than pennies.
Start the timer and think out loud, like you would with an interviewer.
45-minute interview
One clock for the whole interview. Each phase fills up as time passes.
45:00left
Each prompt gives the AI a role, the whole brief, every edge case and a palette. AI drafts, you decide.
Best for a clickable prototype, fast.
ROLE You are a senior product designer building a high-fidelity, clickable mobile app prototype for a UX design interview. Make design decisions a hiring manager would respect, and keep the scope to the brief. THE CHALLENGE Split the trip: Four friends are on a weekend trip to Goa and keep paying for things for each other. Design how they add a shared expense and settle up at the end, without anyone doing maths. THE USER Friends in their twenties on a short trip, paying on their phones, who care more about fairness than pennies. MUST-HAVES - Add an expense in under 15 seconds - See at a glance if you owe or are owed - Split equally or unevenly - Settle up with as few payments as possible EDGE CASES (every one must be handled) - Someone joins the trip halfway and shouldn't pay for earlier expenses - An amount that doesn't split evenly (₹1,000 ÷ 3) - An expense added twice, or by mistake, and needs undoing - Someone pays back in cash instead of in the app - A friend who isn't on the app yet SCREENS TO BUILD 1. Trip balances (390×844): whether I'm owed or I owe, who owes whom, and recent expenses 2. Add expense (390×844): amount first, what it was for, who paid, and how to split it 3. Settle up (390×844): the fewest payments that clear the trip, and how to pay or mark as paid Link them so the main flow is clickable end to end. Show each edge case as a real state (an error, a warning, an empty state or a confirmation), not as a note. VISUAL STYLE - Deep green #0E5A4A: primary buttons and the balance card - Mint #E3F4EC: soft panels and highlights - Paper #F7F7F4: the screen background - Ink #17171C: text - Owed green #137A4B: money you get back - Owe red #B42318: money you owe, and destructive actions - Type: one clean sans-serif. One clear hero (a title or a number) per screen, then a clear order of importance. - Spacing: an 8-point grid, generous margins, touch targets of at least 44 px. - Accessibility: text contrast of at least 4.5:1, labels on every input, never colour alone to carry meaning. CONTENT Use realistic content: Indian names (Riya, Kabir, Meera), amounts in rupees (₹), a weekend in Goa, and payments by UPI. No lorem ipsum. DON'T - Don't add features the brief doesn't ask for. - Don't use more than one primary button per screen.
2 strong answers, each with its own look and reasoning. Try it yourself first.
Done designing?
Compare your screens with 2 different solutions, decision by decision.