Chaat
"Food, tailored for you."
Role
UI/UX Design Lead · Front-end Developer
Year
2024
Duration
2 years
Team
5 (design, engineering, marketing)
Why Chaat exists.
There's no shortage of food discovery apps out there. However, most organize their experience around restaurants rather than the individual dishes. Users are left with multiple decision problems: first, where should you eat? Second, when you're there, what's the best option to pick?
Objectives
- Help users discover dishes they will actually love.
- Build a recommendation experience that feels personal.
- Validate the concept with a working prototype in front of real users.
I led the UI/UX design end-to-end and shipped the front-end build, working closely with the founding team on product direction.
Design lead
Owned wireframes, Figma prototypes, visual design, and design system from zero.
Front-end engineering
Shipped the original Flutter build and React rebuild; bridged design and engineering with working components.
User research
Recruited and ran moderated tests; synthesized findings into design changes.
Product strategy
Helped shape the intention: what we were building, aims, and features.
Food discovery is flawed. You discover places, not food experiences.
When people want to eat something new, what's the best place to turn to? Social media and specialized review apps offer partial solutions, but none target the core problem: people don't want to scroll through restaurants; they want to discover specific dishes they'll love.
From our case studies and research, we found that the current experience creates friction at every step. Discovery, restaurant selection, and finally ordering; users often found the process from desire to dish overwhelming.
Four phases, lots of iteration.
Research
Understanding how people actually pick food.
Describe the research methods and what they were chosen to answer. Avoid listing artifacts — describe the question, the method, and the insight.
Ideation
From taste profile to feed.
Sketches, divergent concepts, and the framework you used to compare them. Show the path, not just the destination.
Prototyping
Wireframes to working build.
Walk through the progression from low-fi to high-fi. Call out the moment you committed to a direction and why.
Testing
A/B testing wireframes with real users.
Method, sample, and what the data told you. The strongest case studies show a clear before/after — what you believed, what you learned, what you changed.
A taste-profile-first discovery feed.
Describe what the final product does, the design decisions that made it work, and what makes this solution different from the alternatives. End on a real-world result, not a feature list.