Case study / 01
Munch is a food delivery app concept built around one idea: ordering is more fun with friends. Designed for Gen Z and millennial users who get bored eating the same thing on repeat.
Friend activity: live preview
Problem statement
That single line from an early interview became the north star for the whole project: build discovery around trusted recommendations from people you know, not just star ratings from strangers.
Process framework: Double Diamond
I structured the project around the Design Council's Double Diamond, alternating between opening up (diverging) and narrowing down (converging) twice, so every design decision below traces back to a research finding rather than personal taste.
Discover
Define
Develop
Deliver
Business research
Before designing anything, I mapped the features already considered table stakes, so Munch could meet expectations while still standing apart on the social layer.
| Feature | UberEats | Deliveroo | JustEat |
|---|---|---|---|
| Navigation style | Bottom bar | Dropdown menu | Bottom bar |
| Send a gift to a friend | Yes | No | No |
| In-app table booking | No | Yes | No |
| Collection option | No | No | Yes — highest rated |
| Visible offers & promos | Yes | Yes | Yes |
Finding
All three apps share the majority of their core features — a clear case of Jakob's Law: users expect your app to work like the apps they already know.
Finding
JustEat's higher store rating traced back almost entirely to one feature — collection — proving small conveniences can outweigh a bigger feature set.
Finding
None of the three surface a friend's order history. That gap became the opening for Munch's core differentiator.
Why competitor analysis first
Starting here, before talking to a single user, meant I could separate "expected" features (nav bar, offers, reordering) from genuinely open territory. Jakob's Law states that users spend most of their time on other products, so they prefer yours to work the same way. That let me spend design effort on the social gap rather than reinventing checkout or search.
User research
A team brainstorm produced a long list of candidate features. Surveys and interviews with regular fast-food-app users told me which of those actually mattered.
Why a red route analysis
A red route maps the highest-frequency, highest-value tasks in a product: the paths users take most often to get real value, borrowed from Transport for London's "red routes" that must never be blocked. Ranking features this way stopped the brainstorm's full wishlist from diluting design effort, and confirmed the brainstorm's instincts with actual user data rather than assumption.
Personas
Rather than invent archetypes, I clustered the interview transcripts by motivation for ordering: impulse and occasion, time pressure, and content for others — and built one persona per cluster so every design decision downstream could be checked against a real behaviour pattern, not a guess.
Orders on impulse between plans with friends. Wants inspiration, not just a search bar.
No time to cook most weeknights. Values speed, saved favourites and a frictionless reorder.
Documents every meal. Wants a platform that showcases where they ate, not just what they paid.
Ideation
Eight sketches in eight minutes forced quantity over perfection early on. From there, the same three screens (Home, Friends activity and Split bill) were wireframed in greyscale at the final layout and size before colour and photography went in.
Why Crazy 8's
The eight-minute constraint is deliberate: it's too short to get precious about any one idea, so it breaks fixation on the first solution and forces genuinely different layouts onto the page. I then took the strongest elements from different sketches rather than picking one sketch outright.
Why three fidelity stages, not one
Wireframing at the final layout and size kept feedback focused on content and flow, not colour or brand. Participants weren't distracted into commenting on visual polish before the structure was right. Visual and brand decisions were locked in last, once the underlying structure was already validated.
Wireframes: same layout and size as the final build, no colour yet
Home
Search sits in the bottom nav, matching the pattern UberEats and Deliveroo already trained users on (Jakob's Law).
Friends activity
Real names replace anonymous rows. Testing moved from "is this readable" to "would I trust this friend's pick".
Split bill
The +/− stepper appears here: exactly what 50% of survey respondents asked for.
Final UI
Home surfaces friends' favourites first, the activity feed makes their recent orders scannable at a glance, and split bill turns a group order into a one-tap settlement — closed by a push notification that lands on a friend's phone the moment they're asked to pay.
Home






Friends activity









Split bill






Notification
Hit Confirm & Split on the split bill screen. Fred's phone picks up a push notification for his share, closing the loop on the group-order flow.
Validation
Four task-based scenarios run through Figma Mirror with participants unfamiliar with the design.
Method
Each session was think-aloud and moderated: participants narrated their reasoning as they navigated, which surfaced why a screen worked rather than just whether the task was completed. Sessions were run one-to-one to avoid groupthink skewing the results.
Completed quickly by every participant, with positive reactions to the carousel format.
All participants found their way to the friend-activity feed without prompting.
Successfully completed by every participant with no hesitation.
Feedback was consistently positive — participants described the app as easy to pick up.
UI phase
Munch's in-app typeface is Lato, chosen for its comfortable reading weight at small sizes and its familiarity across similar apps. Below is the palette and core components that came out of the high-fidelity pass.
Coral / CTA
Teal / Social
Gold / Ratings
Surface
Base
Lato: Headline, semibold
Lato: Body, regular
Accessibility & heuristics
Visibility of system status
Order state (placed, preparing, on the way) is always visible on screen rather than buried in a notification, so users never have to guess where their order stands.
Recognition over recall
Favourites and recent orders surface on the home screen rather than requiring users to remember and re-search for a restaurant name.
Error prevention
The split-bill screen shows the recalculated total live as amounts are adjusted, so a mistake is visible before it's confirmed, not after.
Colour contrast
Body text on the dark surface sits at a 13:1 contrast ratio and the coral CTA at 4.6:1 against its background. Both pass WCAG 2.1 AA for their respective text sizes.
Conclusion
Self-assessment
Strongest muscle: turning a scattered brainstorm into a ranked, evidence-backed feature list. Next time: sharper usability testing that captures friction in the moment, not just end-of-session sentiment — and, with more time, a live A/B test on the friend-activity feed's actual impact on reorder rate.