A food discovery app that turns "what should I eat?" from a daily stressor into something you actually look forward to — built around effortless discovery, smart grocery planning, and a social layer that makes cooking feel less solitary.
Role
Solo Designer
Platform
iOS Mobile
Tools
Figma, Miro, Google Drive
Type
Concept Project
Overview
TASTI started from a simple observation: deciding what to eat is one of the most repeated daily decisions we make. For most people this is draining. Existing apps are built for searching or ordering, not discovering. When you don't know what you want, they give you more of the same friction.
The goal was to design something fundamentally different! A food discovery platform built on four core values:
The final product covers the entire cooking journey - from the initial spark of inspiration, through filtering and saving recipes, building a grocery list tied to your local store, sharing what you've cooked with friends, and earning recognition through competitive food challenges.
"Don't create frames, create experiences."
The Problem
Existing food apps assume users already know what they want. The entire interface is designed for intent, search, filter, order. When someone opens an app without a clear vision, the interface gives them nothing to hold onto.
Key pain points identified
- Decision fatigue — too many undifferentiated options with no guiding hierarchy
- Lack of delight — food app UX is transactional, not experiential
- No community layer — eating is social, but food apps are solitary
- Passive discovery — you only find what you already know to search for
- Disconnected planning — no link between recipe discovery and the actual grocery shop
Research
The research phase involved user interviews, competitive analysis, and structured workshop sessions. Participants spanned a range of cooking habits — from people who order takeaway daily to committed home cooks who plan their week in advance.
The core insight
People don't want to choose, they want to be inspired, then choose from a small, curated set. The mental cost isn't the decision itself, it's having no starting point. Give someone one compelling option and they immediately know whether they want it or not.
This single insight shaped the entire interaction model: present one dish at a time, make the accept/reject gesture effortless, and let taste preferences emerge passively from those micro-decisions.
Design Process
Brand identity
The TASTI brand was designed to stand apart from generic food app aesthetics. The primary color is warm orange (#F47320), energetic without feeling fast-food adjacent. A deep charcoal (#444444) grounds the dark header bar and anchors the typography. A warm cream (#FFF5EE) provides the background layer, keeping the palette grounded and easy on the eye.
Typography is set in Poppins — geometric, warm, and bold at display sizes while maintaining clarity in dense list and filter UIs.
#F47320
#444444
#FFF5EE
Navigation model
The app is structured around four bottom-tab zones, each mapping to a distinct user need:
Wireframes & iteration
Early lo-fi wireframes explored three navigation models. The swipe-based discovery flow, presenting one dish at a time, consistently won in testing over grid and list alternatives, on both task completion speed and reported enjoyment. Once that was settled, the remaining screens were designed to serve it. Everything in the app flows toward a recipe in your hand and ingredients on a shopping list.
Feature — Discover
Feature — Recipe Bank
Feature — Gamification
Learnings
TASTI grew from a small scope that consisted of a single discovery mechanic, to a full cooking platform, discover, plan, shop, share, compete. Looking back, each feature earned its place: the grocery list closes the loop from inspiration to action; the social layer gives the discovery mechanic something to feed into; the gamification makes the social layer worth returning to.
The challenge was keeping each part feel lightweight and cohesive despite the breadth. That pushed me to think in systems rather than screens, a decision made in the filter model would ripple into the search results, the recipe detail, and the grocery list. You can't design those independently.
The brand identity work, running parallel to UX and not after, changed how I approach visual design. When the brand is decided early, every screen decision has a reference point. The fork-in-A logo, the orange-on-charcoal header, the warm cream background — none of those were afterthoughts. They were constraints that made the rest of the design easier, not harder.
Feature — Social