Why I made Hungrrry

I built Hungrrry because I had a ridiculous number of recipe tabs open all the time and still couldn't figure out what to make for dinner.

I have ADHD, and dinner planning tends to happen very "in the moment" for me. I usually don't realize how hungry I am until I'm already starving. Then I open the fridge, see ingredients I need to use before they go bad, and completely blank on what recipes I know that actually use them. I'd saved hundreds of recipes over the years — bookmarks, screenshots, TikToks, Instagram posts, browser tabs — but when it came time to actually cook something, my brain couldn't reconcile any of it together fast enough to act on it.

So I'd default to the same thing over and over, or give up and buy fast food instead.

The frustrating part was that I actually like cooking. I had recipes I genuinely loved. Some I made regularly for months before forgetting they existed for years. Others I kept meaning to try but could never find again when I needed them. Most recipe apps felt too rigid, too cluttered, too expensive, or too focused on meal prep systems that didn't match how my brain works.

Hungrrry started as a way to close that gap between:

• recipes I save
• ingredients I already have
• what actually sounds good right now
• and getting through the grocery store without getting overwhelmed or distracted

The core idea is simple: swipe through recipes until something actually resonates, save the ones you want, turn them into a grocery list, remove what you already have at home, and get through the store quickly enough that you actually make the food instead of abandoning the plan halfway through.

Another huge reason I built it was recipe sharing.

My dad and I are constantly sending each other recipes. He prints recipes and keeps them in binders. I send URLs and screenshots. We both lose things constantly. Pinterest felt overwhelming for him and messy for me, so shared cookbooks became a really important part of the app. Now we can keep collections together, leave notes on recipes, rate what we liked, and revisit meals we'd otherwise forget existed.

One thing that's important to me: Hungrrry is not meant to take traffic away from recipe creators.

Every recipe links back to the original source. The goal is to help people organize and rediscover recipes they genuinely want to cook while still sending traffic and attribution back to the people who created them.

For the vast majority of recipes, Hungrrry does not store cooking instructions at all — the original creator's site is where you go to actually read and make the recipe. The small number of recipes that currently include full instructions came from a development API that I used while building and validating the app early on, and those are being phased out as the platform grows.

Right now the app is still taking shape. I'm continuing to improve the experience, refine the organization tools, and build around the ways people actually save, browse, and return to recipes over time. But even in its current state, it already solves a very real problem in my own life, which is probably the best reason I can think of to keep working on it.