← All work
Food Marketplace2024

EatLocal

A two-sided marketplace connecting home chefs with their neighbors, with chef profiles, listing flows, and checkout designed for first-time users on both sides.

RoleFull-Stack Engineer & Content DesignerMonowaves Agency
StackReact Native, Firebase, Node.js, REST APIs
Tags
Content DesignUX WritingMarketplace UXMobile
Figma design & consultation — no public URL
EatLocal
The Problem

Two-sided marketplaces are hard to design because you're serving two completely different users with one product. Home chefs need tools to list, price, and manage orders. Buyers need to trust that the food is safe, fresh, and worth buying.

UX Approach

I designed the chef and buyer experiences as separate flows that share a data layer. The chef onboarding focuses on building a credible profile — photo, story, and certifications — because trust is the primary purchase driver for food from strangers.

Design Decisions

Chef profile as trust signal

The chef profile page is designed to answer: Who is this person? What do they make? Is it safe? Profile completion is encouraged through a progress indicator, and chefs who complete their profile get a 'Verified kitchen' badge on their listings.

Listing flow for non-technical users

Many home chefs don't think of themselves as 'sellers.' The listing flow uses language like 'Tell people what you're making tonight' rather than 'Create a new product listing.' Steps are simple: photo, name, description, price, portions available.

Checkout for impulse decisions

Food purchases are often impulse decisions. The checkout flow is designed to be completable in under 30 seconds: quantity, pickup or delivery, pay. No account required for first purchase.

Outcome

A production marketplace app with dual onboarding flows, listing management, and a checkout system. The chef onboarding profile completion rate was over 75% in early testing.

75%+Chef profile completion rate

See more

Back to all work

View all →