ROLE
Developer
TIMELINE
September 2024 - January 2025
FRONTEND
React
Vite
HTML
CSS
BACKEND
Node.js
Express
MongoDB

Between tight schedules, ingredient shortages, allergies, and fitness goals, cooking a healthy, satisfying meal can feel like solving a puzzle. For students and health-conscious individuals alike, this often means bouncing between five apps just to make dinner.
RecipeFit was created to eliminate that burden. Our goal was simple: make it as easy as possible to find a recipe that works for you, with what you have. Built by a team of five using MERN + Flask, I served as the product manager and contributed to early feature scoping, user validation, and AI integration strategy.
To design and build a recipe app that filters by available ingredients, dietary restrictions, and nutrition targets, offering smart substitutions and curated results—all in one place.
To understand the friction behind everyday meal planning, we interviewed 16 students and early-career professionals who cook at least 2x a week. We asked about their current cooking process and biggest frustrations.
We also sent out a broader survey (n = 45) and found:
| Insight | What It Meant For Us |
|---|---|
| People start with ingredients, not recipes | Ingredient-first search UI was critical |
| Allergies are high-risk | Safety filters must be front-and-center and reliable |
| Users want to feel healthy, not micromanage | We had to surface nutrition data clearly, but not overwhelm |
| App | Strength | Weakness |
|---|---|---|
| Yummly | Great UI and search experience | Poor for filtering by macros or allergies |
| MyFitnessPal | Strong nutrition tracking | Tedious recipe input, not food discovery |
| Tasty | Engaging content | Entertainment-focused, not goal-oriented |
| Visual inspiration | No filtering, no context |
Gap: None of these tools helped users say: "Here’s what I have, here’s how I eat—what can I make?"
Balancing Specificity and Flexibility
Too many filters = no results. Too few = irrelevant ones. We iterated on the filter logic to let users prioritize (“must-have” vs “nice-to-have”).
Prompt Engineering for Gemini
Early prompts gave wild substitutions (e.g., “replace chicken with applesauce”). We restructured prompts to include recipe context, diet labels, and formatting rules.
Allergy Trust
We had to sanitize and validate Edamam’s responses. If a recipe contained “may contain peanuts,” we excluded it entirely from peanut-free results.
RecipeFit: Eat smart. Cook easy.
questions? feel free to send me a message!