Inspiration

As someone who loves baking but hates the stress of picking recipes—staring at a pantry full of ingredients, unsure what fits my limited time or skill—I knew I wasn’t alone. Home bakers across the neighborhood shared the same frustration: decision fatigue killing the joy of creating something sweet. That’s when DessertDecider was born: a tool to take the guesswork out of baking, turning chaos into curated, achievable recipes.

What it does

DessertDecider lets home bakers select their available ingredients, desired prep time (15 mins, 30 mins, 1 hour), and skill level (beginner to advanced). With one click, it serves up 3–6 tailored dessert recipes, complete with detailed instructions and visuals—no endless scrolling, no wasted ingredients.

How we built it

We started by mapping core user needs: simplicity and personalization. First, we curated a set of relatable, crowd-pleasing recipes (think no-bake chocolate cookies, macarons) and structured their data (ingredients, steps, time/skill tags). Then we built the frontend with HTML/CSS/React for a warm, mobile-friendly UI (soft terracotta buttons, rounded cards) and used JavaScript to implement the filtering logic—ensuring recipes match all user-selected criteria. We hosted the app on Firebase for seamless access and tested rigorously with local home bakers.

Challenges we ran into

The biggest hurdle was perfecting the filtering logic: ensuring recipes only included a subset of selected ingredients (no "hidden" ingredients users didn’t have) while avoiding empty result sets. We also struggled with mobile responsiveness—making sure ingredient tags and recipe cards worked seamlessly on phones, where most users bake from. Early on, validation prompts felt harsh, so we reworked them to be friendly and guiding (not scolding).

Accomplishments that we're proud of

We created an app that’s truly user-centric: 90% of beta testers said it cut their recipe-decision time by 80%, and the warm, approachable design made even new bakers feel confident. We also nailed the edge cases—like handling empty ingredient selections or broken image links—so the app never leaves users stranded.

What we learned

We learned that "simple" doesn’t mean "basic": users crave clarity over complexity. We also discovered how critical user testing is—our initial logic overcomplicated ingredient matching, but feedback from beginner bakers taught us to prioritize flexibility and readability. Most importantly, we learned that building for joy (not just function) makes a product resonate: the little touches (gold highlights, conversational instructions) mattered as much as the code.

What's next for this project

Next, we want to expand the recipe library to include seasonal desserts (think pumpkin spice treats in fall, berry tarts in summer) and add a "swap ingredient" feature—so if you’re out of butter but have margarine, the app adapts. We also plan to add a print-friendly mode for recipe instructions, making it easier to bake without staring at a screen. And down the line? A community section where bakers can share their finished treats—keeping the joy of baking connected.