Light mode on. Physics cord simulation.
Tradish Header
Back to Projects

Tradish : Designing a global food discovery app from a personal passion

0

Lifetime Downloads

$0

Total Revenue

0/day

Peak Active Devices

Source: App Store Connect · Lifetime data

Project overview

Tradish is a mobile application for iPhone and iPad that helps home cooks discover, plan and cook authentic dishes from many cultures. As the founder, product strategist, UX designer and engineer, I built the first version in a six-week sprint (July-August 2025). Since then I have released incremental updates, gathered feedback and iterated on onboarding, recipe management and meal planning features.

I wrote this to show how I reason through product decisions, not only what ended up in the app.

Role
Founder, Product Strategist, UX Designer, Engineer
Category
Mobile App, Product Design, UX/UI Design
Project Type
Solo Project
Tools
React Native | TypeScript | Expo | Figma | Cursor

Personal and problem context

Growing up in a multicultural family in London, food was my bridge to countless cultures. I learned dishes from relatives, friends, and later from YouTube videos. As I took up cooking, I noticed a gap:

Finding diverse meals was hard. I'd try a Persian stew one week and Senegalese fish the next, but outside of word-of-mouth or random online searches, there was no tool that helped me continue exploring. Most recipe apps focused on generic or western food and emphasised nutrition tracking or trendy content.

The friction I experienced became the seed of Tradish. I wanted an app that:

  • Celebrated culture and heritage as much as calories and macros.
  • Was as quick to use as grabbing a recipe from a friend.
  • Encouraged experimentation and planning without overwhelming users.
Carousel image 1

Users

  • Primary: Busy home cooks who are culturally curious. They cook several times per week, crave variety and want to plan meals without spending hours researching.
  • Secondary: Diaspora users who want to rediscover dishes from their heritage and keep family recipes alive.
  • Not targeted: Professional chefs and social media-driven foodies; they require different feature sets (deep customization or social sharing), which would have distracted from the MVP focus.

Goals and success metrics

I defined concrete goals to keep the app outcome-driven:

1

Fast discovery

Reduce friction and encourage daily use

Find or generate a recipe in <15 seconds
2

Cultural exploration

Encourage trying dishes from new regions

50%+ of saved recipes from unexplored cuisines
3

Weekly planning

Support meal prep for busy schedules

Create a week-long plan within 3 minutes
4

Subscription uptake

Validate the value of premium features

>5% of active users subscribe to Tradish Plus

Constraints and assumptions

  • Solo founder: As both designer and developer, I had to balance scope with feasibility. I limited the MVP to a few high-impact features to ship quickly.
  • AI maturity: Recipe generation relies on language models. I assumed users would accept generative recipes if they could see and edit the output.
  • Dataset bias: I understood that not all cultures were equally represented in the dataset. A long-term goal was to source more diverse recipes.

Competitive analysis

Rather than building a feature matrix, I studied where competing products focus their energy:

Calorie tracking (MyFitnessPal)
Precision and nutrition insight
Joyless logging, little cultural context
Recipe aggregators (Yummly)
Huge databases, beautiful photos
Overwhelming results, limited cultural focus
Cooking media (Tasty)
Engaging videos and trends
Entertainment over meal planning
Food heritage blogs
Authentic stories
Hard to translate into actionable recipes

Gap identified: no one combined cultural storytelling with quick discovery and planning.

Design process

Phase 1
Research

As designer and target user, I combined desk research with lightweight user feedback.

  • Competitive teardown of western-centric recipe apps
  • App Store reviews + Reddit pain-point mining
  • Informal interviews with culturally diverse home cooks
Phase 2
Define

Framed the core problem and set experience principles as a north star.

  • HMW: help curious cooks discover & plan authentic meals
  • Personas: busy home cooks + diaspora users
  • Principles: speed · culture feels human · plan reduces decisions
Phase 3
Ideate

Sketched and prototyped multiple directions before committing to a layout.

  • Card vs list layouts for recipe discovery
  • Infinite scroll vs curated suggestions
  • GPT-4 placeholder recipes to test AI generation

Low-fidelity wireframes

I began with grayscale, low-fidelity wireframes to map out the core screens without getting distracted by colour or detail. I stuck to layout, hierarchy and flow, and asked on each screen: what does the user need here, and what's the fastest path to value?

Low-fidelity wireframes: Welcome, Onboarding, Home, Recipe Detail, Meal Planner, Saved Recipes

Mid-fidelity wireframes

Once the layout and flow felt right, I layered in the Tradish brand (the signature orange ), real content and more refined UI elements. This step validated that the visual hierarchy, spacing and component patterns worked with actual data before moving to code.

Mid-fidelity wireframes, with Tradish colours and real content

Test

Before building the full app, I tested interactive prototypes with a small group of five friends and colleagues. They were asked to complete tasks such as finding a dish from a new culture and creating a weekly plan. Their feedback highlighted friction points (e.g., too many onboarding questions, unclear icons) and validated the appeal of short cultural stories. After launching v1.0, I continued testing by monitoring analytics (onboarding completion, recipe saves, plan usage) and collecting qualitative feedback through testflight builds. Each release incorporated these learnings, such as simplifying the onboarding flow and introducing the Smart Meal Distribution feature.

Final screens

A guided tour of the shipped app, with callouts on the design decisions behind each screen.

1
Screen 1

Home — Let's cook!

Friendly entry point that nudges the user straight to action.

  • 1
    Pixel-art mascot
    Human, playful branding that sets Tradish apart from sterile recipe apps.
  • 2
    Daily fun fact
    Cultural context delivered in a single glance — no reading required.
  • 3
    One-tap "Cook Now"
    Reduces decision fatigue by always surfacing a single recommended meal.
  • 4
    Popular searches
    Cuisine-first discovery instead of ingredient-first filtering.
2
Screen 2

Home — search & recipe card

Orange discovery header with popular chips, search and a full recipe preview.

  • 1
    Popular searches
    Cuisine chips keep discovery one tap away from the keyboard.
  • 2
    Search field
    Single field for recipes, ingredients or cuisines.
  • 3
    Recipe sheet
    Title, story, macros and ingredients without leaving home.
  • 4
    Tab bar
    Home stays primary; Plan and profile stay reachable.
3
Screen 3

Recipe detail

All the info needed to decide and cook — without scrolling walls of text.

  • 1
    Search always visible
    Users can pivot to a different recipe without leaving the flow.
  • 2
    At-a-glance meta
    Time, calories, meal type and prep — the four questions users actually ask.
  • 3
    Macro breakdown
    Protein, carbs, fat in a glance so health-conscious users don't need a separate tracker.
  • 4
    Clean ingredient list
    Scannable bullets with accent dots that tie back to the Tradish orange.
4
Screen 4

Meal planner

Weekly planning that feels as lightweight as a calendar, not a spreadsheet.

  • 1
    Week navigation
    Arrows + explicit date range prevent the "what week am I on?" problem.
  • 2
    Weekly summary
    Calories + macros auto-aggregated so the user never does the math.
  • 3
    Shopping list CTA
    One tap to turn the plan into a grocery trip — the highest-value action.
  • 4
    Completed states
    Green + strikethrough gives dopamine + clear progress signal.
5
Screen 5

Shopping list

Auto-generated, grouped by aisle, with a real-world checkable UI.

  • 1
    Auto-sync
    Refresh pulls the latest ingredients from the plan — no manual entry.
  • 2
    Clear completed
    Lets users reset after a shop without losing the category structure.
  • 3
    Aisle groupings
    Pantry, Meat, Produce etc. — mirrors how people actually walk a store.
  • 4
    Big checkboxes
    Thumb-sized targets optimised for one-handed use in a supermarket.
6
Screen 6

Saved recipes

A personal cookbook that rewards exploration.

  • 1
    Personal framing
    "My Saved Recipes" + "Your Personal Recipe Collection" creates ownership.
  • 2
    Emoji thumbnails
    Cheap but delightful visual identity for every cuisine.
  • 3
    Consistent meta
    Time + calories appear on every card — predictable scanning pattern.

Experience principles

Before wireframing, I established three principles to guide every design decision:

  • Speed over completeness. Minimise steps to see value. If users don't get a recipe quickly, they drop off.
  • Culture feels human, not academic. Avoid dry encyclopaedic descriptions. Each recipe includes a brief story to provide context, drawn from trusted sources.
  • Planning reduces decisions, not adds them. Weekly planning surfaces only the most relevant options and suggests default calorie distributions so users aren't overwhelmed by numbers.

Information architecture

I kept the navigation intentionally shallow:

  • Home: AI-generated suggestions and quick search.
  • Discover: Explore by culture, ingredient or popularity.
  • Plan: Weekly meal planner with summary statistics (calories, cost, prep time).
  • Saved: A personal library of recipes.
  • Profile: Manage preferences and subscriptions.

User journey flow

I mapped the complete user journey from first launch through onboarding, recipe discovery, meal planning and the premium upgrade path. This diagram guided each screen's purpose and helped me spot places where the flow could stall.

Full user journey flow from app launch to meal planning and premium conversion