7:15pm on a Friday.

You've been scrolling the same delivery app for twenty minutes. Pizza. Burgers. The noodle place that was soggy last time.

Through the wall, your neighbour's kitchen smells of garlic and something slow-cooked. Your stomach answers.

You don't know her name. You order the noodles again.

That's what WeCook is for.

Friday 21 November
7:15
Delivery app
now
Still deciding? Your usual noodles are 2 taps away.
Pizza place
12m ago
20% off tonight only. Order now!
Your phone, right now
Scroll
Food Marketplace
Mobile App

WeCook

A UK marketplace where local home cooks and bakers sell homemade food, and share the story behind it. Two apps, one for the people craving real food and one for the cooks making it.

Role
Senior Product Designer
Client
WeCook Limited, London
Platform
iOS & Android
Status
Live in the UK Β· 5K+ downloads
WeCook app screens shown on phones
01 β€” The before

Good home cooking already exists on your street. It's just hidden.

Today it travels by word of mouth, neighbourhood chat groups and Instagram DMs. A cook posts a photo. You message to ask if it's still available, how much it is, where to collect. Then you wait.

So you're left choosing between a stranger you can't vet and a chain you're tired of.

01
Chat groups & DMs
β€œStill available?” β€œHow much?” β€œWhere do I collect?” Then waiting.
02
Delivery apps
Built for restaurants: a logo, a star rating, a menu. Nothing tells you who is cooking.
03
Orders in every thread
For cooks: no queue, no record of who paid, orders scattered across chats.
04
No way to show trust
Cooks can't show their kitchen follows food-safety rules.
02 β€” The reveal

The first thing you see isn't a logo. It's a person.

A baker two streets away, flouring the counter in a short kitchen video. A cook's note about the recipe her grandmother taught her. Today's dishes, a price, and a way to order.

WeCook is where you scroll, follow, shop from and support the home cooks near you. That tray coming out of the oven on your street? Now you know who made it.

Customer app screens: onboarding, allergies, cook profile, dish details, orders, notifications and account
03 β€” Design decisions

Every decision started from one question: what does the person on the other side of the screen need right now?

01

Lead with the cook, not the menu

The moment

Remember the fridge, and the tray of food on your street made by someone you'll never know? The missing piece wasn't food. It was the person.

What I designed

Cook profiles that open like a creator's page: kitchen videos, recipes and personal story first, with the menu below.

Why

When you can see who's cooking, the question shifts from β€œwhat do I want?” to β€œwho do I want to eat from?” That gives a customer a reason to come back to the same cook.

Try itBe the cook. Your dish becomes the headline.
Your kitchen
0.3 mi away Β· Food-safety verified
Your signature dish
Homemade today Β· Order by 5pm
02

Start from the street, not the cuisine

The moment

Proximity is the whole point of homemade food, and most cooks only make a few dishes a day.

What I designed

Discovery that starts with who is cooking nearby, with cuisine and dietary filters layered on top.

Why

A long city-wide list buries the cook three doors down. Showing what's close and available today matches how people already find home cooks: by neighbourhood.

03

Make food safety visible

The moment

Trusting a meal from someone else's kitchen is the biggest leap a customer takes here.

What I designed

Food-safety status shown on the cook's profile, not hidden in the terms, and a cook onboarding flow that walks sellers through the requirements step by step.

Why

Customers get a reason to say yes. Cooks feel supported in meeting the rules rather than policed by them.

04

Give cooks a queue, not a dashboard

The moment

Before WeCook, a cook's orders lived across dozens of chat threads.

What I designed

A simple, card-based order queue, stripped down until it fit how home cooks actually work, not how restaurants work.

Why

Home cooks are not restaurant operators. The tool should feel as familiar as the chat they already use, with the chaos taken out.

Home cook app screens: dashboard, kitchen setup, delivery zone, verification, menu, resources and FAQ
04 β€” Outcome & reflection

Where it is now

UK
Live on iOS and Android
5K+
Downloads on Google Play
78
Screens in the customer app
156
Screens in the home cook app

What I learned

1
Two-sided means two first impressions.

Every choice that helps customers lands on cooks too, and the cooks' side has to be simple enough to adopt in an evening.

2
Trust is a feature, not a badge.

Faces, kitchens and visible safety status did more design work than any single screen.

3
Simple doesn't mean less thought.

The cook's order management looks simple because it took the most iteration.

What I'd do next

Distance control

A clear distance sort, and an honest empty state when few cooks are nearby yet.

Editable preferences

Dietary needs and allergies set during onboarding, easy to change later from the profile.

Look before you sign up

Let people browse cooks before creating an account, to lower the first hurdle.

7:15pm, Friday.

Garlic and something slow-cooked, drifting through the wall again.

This time you know her name.

And this time, one of those plates is coming to you.