Why I Built CookSnap (A Founder Note for 2026)

I’m Alex. I started building CookSnap at 14. It is now the spring of 2026, the iOS app is in early access, the recipe library is at 9,000+ entries, and roughly five thousand people have joined the waitlist. I wanted to write down why any of this exists, because the answer changes the way you use the product.

The problem I kept hitting

I would open the fridge, see four ingredients, and have no idea what to do with them. ChatGPT would invent something plausible that asked for ingredients I didn’t have. Google would return ten food blogs that wanted me to scroll past a personal essay to get to the ingredient list. SuperCook would surface 400 results scraped from across the web and I’d give up by the third click-out.

None of these tools were bad. They were just shaped for the wrong question. The question I had was: tonight, with these four real things, what is one recipe that exists?

What CookSnap is trying to be

A recipe finder with three commitments:

1. Every recipe is real.Hand-curated, vision- verified, ingredient lists normalized, steps checked. If a recipe is in the library, it’s been cooked.
2. Every match is honest. Fit percentage on every result. An explicit list of missing ingredients, tiered by how critical they are. No silent substitutions.
3. Every interaction is fast. Under-200ms matches. Free web tool with no signup. The iOS app uses on-device computer vision so the camera path is also under a second.

What CookSnap is deliberately not

• Not a recipe generator. No LLM invents dishes here. The architecture is retrieval against a curated library, full stop.
• Not a meal planner.Mealime exists. If you plan weekly menus, that’s the right tool. CookSnap is for the cooks who improvise.
• Not a recipe manager. Paprika exists. If you have a collection of recipes you love, organize them there. CookSnap finds you new ones.
• Not infinite. The library is ~9,000 recipes. It will not be 9 million. Curation has a ceiling and we are honest about it.

The trade-offs we made on purpose

Every product is a stack of trade-offs. Ours, written out:

• We chose library curation over open-web scraping. Smaller match set, higher quality floor.
• We chose retrieval over generation. Lower hallucination rate, faster responses, no creative recipe generation as a feature.
• We chose iOS-first over cross-platform. On-device vision works well only on Apple silicon right now. Android is on the roadmap; it’s not here yet.
• We chose solo development over investment. No outside money. No growth team. The product moves at one-person speed, which is honest about what one person can ship.

What I’m asking for

Try the web recipe finder if you haven’t. Tell me what’s broken — alex@cooksnapapp.com gets to me, not a support queue. If you’re on the waitlist, thank you. I read every signup form.

I’m building this slowly and on purpose. If that resonates, you’re probably the right user.