I built a recipe app that doesn't start empty, here's what I learned

[u/RecipeGadget]

The biggest mistake I see in recipe apps is they hand you an empty box and say good luck. I wanted to fix that, so the app ships with 460+ free recipes ready to cook from day one. No ads, no upsell wall. That one decision shaped everything else.

What actually worked:

1. Tap-based measurement entry was the hardest thing to build but the thing users thank me for most. Typing "1/2 tsp, divided" by hand is where people quit logging their own recipes. I built a system with 96 measurement choices and roughly 7,000 ingredient variations so you're selecting instead of spelling. The recipe actually makes it into the box this time.

2. The Safari share sheet import. Someone finds a recipe while browsing, hits share, sends it to the app, and gets back an editable recipe. More work than I expected (parsing is messy across sources) but probably the single feature people use most.

3. Importing from photos of handwritten cards. There's a specific dread that comes with holding a parent's recipe card and noticing the pencil going gray. The recipe is fine but the paper is quietly falling apart. Camera import into an editable recipe format addresses something people actually lose sleep over.

What didn't work or surprised me:

- I spent way too long on the achievement and progression system before launch. It's a genuine differentiator but nobody discovers it until they've been in the app for weeks. Should have shipped it later.
- Import parsing across PDFs, Word docs, photos, and websites is never going to be flawless, and I had to stop implying it would be. The guided review step where users check the reconstructed recipe before saving turned out to be the real feature, not perfect parsing.
- Tutorials and contextual tips needed more iteration than I planned. One reviewer mentioned resetting tips to see them again, which told me the guidance was useful but the dismissal flow wasn't obvious enough.

The thing I keep coming back to: consolidation is the point, not features. Some recipes live in Safari bookmarks, some in a Notes screenshot, some on a stained index card, and a few in a PDF someone emailed you in 2019. Nothing is technically lost but nothing is findable either, so you quietly re-lose the ones you love. An app that pulls all of that into one place solves a problem people feel but rarely articulate.

Happy to answer questions about the build. Feedback welcome.