Eatzy Ordering: Order local food from any phone
The website where people order from local restaurants on Eatzy. Each delivery market brands it as its own, and it’s built for phones, where most orders come from.
- Role
- UI/UX Designer
- Users
- Hungry people, mostly on phones
- When
- 2017–2020
- Platforms
- Web app (in the browser)
The problem
No app yet, and most customers on phones
Eatzy's technology is shared by local delivery services that each run their own market. The ordering site had to be easy to customize for each market, and since there was no app at the time, ordering on a phone browser had to be effortless.
What I did
Building on users I already knew
- A head start: I'd designed an earlier website for the same company, so we knew the customers.
- Competitor research, then user flow, wireframes and prototypes.
- UI and specs, and working with the developers through the build.
The site
From hungry to ordered in a few taps
Photos, short descriptions and prices; one tap adds a dish.
They stick to the top while you scroll a long menu.
A bar with the count and total appears with the first dish.
Each local service puts its own brand on the same site.
Result
Revenue on both ends
Customers order food from local restaurants in one place. Because the client also delivers for those restaurants, it earns on both ends: a share of each order and revenue from its drivers. After launch, analytics and heatmaps showed how people used the site, feeding improvements, new features and A/B tests to raise conversion.
More from the same platform: dispatch, restaurant management and the kitchen tablet.
Tell me what you’re building and who it’s for. Thirty minutes is enough to see if I’m the right designer for it.
What happens next
- Pick a timeA 30-minute call, whenever suits you.
- Tell me about the productYour goals, the people using it and what’s in the way.
- Know if it’s a fitYou’ll leave knowing whether I’m the right designer for it.