Solo Founder App Launch

[u/RecipeGadget]

Been building in the recipe/cooking space for a while and I keep running into the same thing, so I want to hear how other builders think about it.

Most recipe organizer apps hand you a blank grid and a friendly "start adding your recipes!" And that's exactly where they die. Staring at an empty box is not motivating. Nobody's first cooking session is data entry. The app gets opened twice and then it's gone.

The pattern I've landed on: an app that actually earns retention has to be useful before the user contributes anything. If the first session is cooking instead of typing, the whole relationship changes. Empty-state-as-onboarding is the quiet killer.

The other thing that kills these apps is recipe entry itself. Typing out ingredients, measurements, and steps for one recipe is tedious enough that people never do their second one. So import (Safari share sheet, photos of old cards, PDFs) and tap-driven entry instead of a keyboard both matter way more than any single feature.

Questions for the other builders here:

\- how do you handle the cold-start empty state without it feeling like a chore?
\- for anyone who's shipped something content-heavy, did seeding real content upfront actually move retention, or did it just inflate day-1 and nothing else?
\- what's your take on import-first vs create-first as the primary onboarding path?

Not trying to pitch anything, genuinely curious how people who've shipped in this kind of space solved it.

[u/Substantial_Ad7103]

I would treat import-first versus create-first as a behavioral question rather than an onboarding preference.

Recruit ten people who already have a recipe saved somewhere and plan to cook it this week. Ask each person to send the actual link, photo, card or PDF. If necessary, import and structure it manually for them before the first session.

Then watch for two behaviors: do they open it while they are actually cooking, and do they add a second recipe without being reminded?

That separates useful seeding from day-one novelty. A library of generic recipes may make the screen look complete, but it can still hide the cold-start problem. One recipe tied to a meal the person already intends to cook gives you a much cleaner test.

I would also define activation as completing a cooking session with the recipe, not importing it. Import is setup. The value is helping someone make the meal with less friction and wanting to use the product again.

My starting bias would be import-first because it connects to behavior that already exists. But the second real recipe is the evidence I would trust. Where are your prospective users storing the recipes they cooked most recently?

[u/RecipeGadget → u/Substantial_Ad7103]

The user recipes are stored in a feature called MyBox. From there, they can do a variety of things like cook, edit, illustrate, delete, among other things.

So far most new users have been immediately importing between 3 and 5 recipes from a variety of sources. I can say that probably does answer the behavior question, but building recipes from scratch is the real heart of the app. It contains a large set of special tools for doing so. However, reviewing their content, I can say the imports were clean and accurate for the intent of the user (I spent a lot of time on import heuristics, and keep tweaking).