Hello,

I’m building a meal planning app (FoodieFlow) and I’m at a crossroads with onboarding and would love some opinions from people who’ve actually shipped consumer apps.

Right now my onboarding flow is:

1. Name, email, username, DOB
2. Email verification
3. Dietary preferences (optional) + membership tier
4. Done

Pretty standard and it works, but I’m not convinced it’s the best approach for first-time user conversion.

I’m debating between 3 onboarding approaches:

Option 1: Keep it as-is

Users land straight on sign up / login and go through the current flow.

Pros:

• Simple
• No extra build complexity
• Clean auth-first model

Cons:

• No product exposure before commitment

Option 2: Post-signup walkthrough

User signs up first, then gets a guided tour or onboarding walkthrough of features.

Pros:

• Keeps auth clean
• Can personalise based on user data

Cons:

• Feels a bit like “explaining” instead of “using”
• Might be skipped or ignored

Option 3: Sandbox preview (guest mode)

User enters the app immediately with a pre-filled demo state (sample meals, pantry, etc).

They can interact with it (swap meals, regenerate plans, etc), then at the end it asks them to sign up to save progress.

Pros:

• They experience value immediately
• More “I’ve already started using this” feeling
• Likely higher conversion

Cons:

• More complex backend (guest state, data merging later)
• Slightly more engineering work

Curious what people here think works best in practice.

If you’ve shipped something consumer-facing:

• What actually converts better?
• Did walkthroughs help or just get ignored?
• Is sandbox/guest mode worth the engineering overhead?

Keen to hear real-world experiences, not just theory.

Hey everyone,

I’m building a meal planning app (FoodieFlow) and I’m at a crossroads with onboarding and would love some opinions from people who’ve actually shipped consumer apps.

Right now my onboarding flow is:

1. Name, email, username, DOB
2. Email verification
3. Dietary preferences (optional) + membership tier
4. Done

Pretty standard and it works, but I’m not convinced it’s the best approach for first-time user conversion.

I’m debating between 3 onboarding approaches:

Option 1: Keep it as-is

Users land straight on sign up / login and go through the current flow.

Pros:

• Simple
• No extra build complexity
• Clean auth-first model

Cons:

• No product exposure before commitment

Option 2: Post-signup walkthrough

User signs up first, then gets a guided tour or onboarding walkthrough of features.

Pros:

• Keeps auth clean
• Can personalise based on user data

Cons:

• Feels a bit like “explaining” instead of “using”
• Might be skipped or ignored

Option 3: Sandbox preview (guest mode)

User enters the app immediately with a pre-filled demo state (sample meals, pantry, etc).

They can interact with it (swap meals, regenerate plans, etc), then at the end it asks them to sign up to save progress.

Pros:

• They experience value immediately
• More “I’ve already started using this” feeling
• Likely higher conversion

Cons:

• More complex backend (guest state, data merging later)
• Slightly more engineering work

Curious what people here think works best in practice.

If you’ve shipped something consumer-facing:

• What actually converts better?
• Did walkthroughs help or just get ignored?
• Is sandbox/guest mode worth the engineering overhead?

Keen to hear real-world experiences, not just theory.

Built this to fix something that was genuinely annoying us every single day.

Me and my partner kept falling into the same loop:
no plan → bad food shop → random meals → midweek takeaways → repeat

So I built a simple app to handle it properly.

What it does:

• plan meals for the week in one place
• save and reuse meals you actually like
• import recipes from websites or photos
• auto-generate shopping lists
• track what you already have in your kitchen
• suggest meal ideas based on ingredients, time, and mood

Now we just sit down once a week, plan everything in ~10 minutes, and stop thinking about food for the rest of the week.

It sounds small, but it’s weirdly changed how often we default to takeaways.

Still in beta and improving it as people use it.

Would love any feedback or thoughts.

https://foodieflow.app/beta/

I built this because my partner and I were wasting way too much time every day just deciding what to eat.

Looking for some beta feedback.

App: https://foodieflow.app/beta/

What it does:

• Weekly meal planning
• Save and organise recipes
• Import recipes from web, images, or files
• “Foodie Assistant” suggests meals based on ingredients, diet, mood, and cooking time
• Auto-generated shopping lists
• Pantry tracking to avoid buying duplicates
• Simple meal prep and batch cooking flow

Why it exists:
Turns out the hardest part of food isn’t cooking, it’s the constant decision making around it. This is trying to remove that loop entirely.

What I need feedback on:

• Does this solve a real problem for you?
• Where do you get stuck or confused?
• Would you realistically come back weekly?
• What feels unnecessary or overcomplicated?
• What would make you stop using it immediately?

Pricing (beta):
£2.99/month for Pro membership BUT core features stay free

Also curious:

• Would you ever pay for something like this?
• If not, what’s missing?

Happy for honest takes, even if it’s not for you.

A bit of context — I'm in my 4th year of Mechanical Engineering, working in the field alongside it, so my brain is permanently running on fumes. My partner is the same. We are both completely useless when it comes to deciding what to eat, and when two exhausted, indecisive people live together the answer is almost always "just get a takeaway" — which gets old fast, both on the wallet and the waistline.

So for our anniversary, I built an app. Not exactly roses and chocolates, but hear me out.

What it does:

• Plan meals together for the week
• Save and organise recipes
• Import recipes from websites, photos, or files
• Foodie Assistant suggests meals based on ingredients, dietary needs, mood, and cooking time
• Auto-generate shopping lists from meal plans
• Track what you already have at home so you stop buying duplicates
• Make meal prep and batch cooking easier

The unexpected part is that we now spend maybe 5-10 minutes every Sunday planning the week and the whole "what are we eating tonight?" problem basically disappeared.

I'm still in beta and would love input from people who've actually shipped products before.

Beta: https://foodieflow.app/beta/

Core features are free forever.

Current Pro plan: £2.99/month (~$3.49)

Pro includes:

• Unlimited Foodie Assistant usage (free gets 10/week)
• Full calorie + macro tracking
• From Scratch mode with proper ingredient quantities and measurements
• Unlimited saved meals + photos
• Priority assistant responses
• Smart recipe auto-tagging
• Advanced shopping and planning tools

Questions:

1. Does £2.99/month feel too high, too low, or suspiciously cheap?
2. Should I do a 7-day trial, 14-day trial, or skip trials entirely and rely on the free tier?
3. Which feature actually sounds worth paying for?
4. Which feature sounds like it should never be behind a paywall?
5. If you landed on this app today, what would stop you downloading it?
6. Any obvious mistakes people make before launching subscription apps?

Would genuinely appreciate brutally honest feedback. Happy to answer questions about the build too.

A bit of context — I'm in my 4th year of Mechanical Engineering, working in the field alongside it, so my brain is permanently running on fumes. My partner is the same. We are both completely useless when it comes to deciding what to eat, and when two exhausted, indecisive people live together the answer is almost always "just get a takeaway" — which gets old fast, both on the wallet and the waistline.

So for our anniversary, I built an app. Not exactly roses and chocolates, but hear me out.

What it does:

• Plan meals together for the week
• Save and organise recipes
• Import recipes from websites, photos, or files
• Foodie Assistant suggests meals based on ingredients, dietary needs, mood, and cooking time
• Auto-generate shopping lists from meal plans
• Track what you already have at home so you stop buying duplicates
• Make meal prep and batch cooking easier

The unexpected part is that we now spend maybe 20 minutes every Sunday planning the week and the whole "what are we eating tonight?" problem basically disappeared.

I'm still in beta and would love input from people who've actually shipped products before.

Beta: https://foodieflow.app/beta/

Core features are free forever.

Current Pro plan: £2.99/month (~$3.49)

Pro includes:

• Unlimited Foodie Assistant usage (free gets 10/week)
• Full calorie + macro tracking
• From Scratch mode with proper ingredient quantities and measurements
• Unlimited saved meals + photos
• Priority assistant responses
• Smart recipe auto-tagging
• Advanced shopping and planning tools

Questions:

1. Does £2.99/month feel too high, too low, or suspiciously cheap?
2. Should I do a 7-day trial, 14-day trial, or skip trials entirely and rely on the free tier?
3. Which feature actually sounds worth paying for?
4. Which feature sounds like it should never be behind a paywall?
5. If you landed on this app today, what would stop you downloading it?
6. Any obvious mistakes people make before launching subscription apps?

Would genuinely appreciate brutally honest feedback. Happy to answer questions about the build too.

So a bit of context — I'm in my 4th year of a Mechanical Engineering degree, already working in the field alongside it, and honestly my brain is just permanently running on fumes at this point. Between the degree, the job, and trying to have some sort of a life, the absolute last thing I have the energy for at the end of the day is standing in the kitchen doorway staring into the fridge like something's going to magically appear.

The worst part? My partner is exactly the same. We are both completely useless when it comes to deciding what to eat, and when you put two indecisive people together who are both exhausted, the answer is almost always "just get a takeaway" — which gets old fast, both on the wallet and on your waistline.

It got to the point where we weren't even properly food shopping anymore because we'd never planned what we actually needed, so we'd just wander round the supermarket buying random things that never quite came together into actual meals. It was a mess.

So for our anniversary I built an app. Not exactly roses and chocolates but hear me out —

It basically helps us stay on top of food without having to constantly think about it:

• plan meals for the week together
• save and organise recipes in one place
• import recipes from websites/photos
• generate meal ideas
• automatically generate shopping lists based on planned meals
• track what we already have at home
• avoid buying duplicates or wasting food
• make batch cooking and meal prep way easier during busy weeks

Basically it removes the whole “what are we eating tonight?” problem before the week even starts, which turned out to be way more useful than I expected.

And genuinely, we use it every single day now. It kind of became this little routine we do together on a Sunday evening which I wasn't expecting at all, but it's been one of the nicest side effects of building it.

I'm still in the beta testing phase right now and would love to get more people trying it out — but honestly I'm also just curious whether this resonates with anyone else or if I've just been solving a very specific problem that only exists in our home? - If you'd like to give it a try go to - https://foodieflow.app/beta/

Hi everyone,

I’m looking for a few Android testers for my app FoodieFlow as part of Google Play closed testing.

FoodieFlow is a meal planning app that helps you save meals, build weekly meal plans, generate shopping lists, and import recipes into your library. I’m mainly looking for basic testing before production release.

What I need tested:

• Install through Google Play closed testing
• Open the app a few times over the testing period
• Try creating a meal, using the planner, and checking the shopping list
• Let me know if anything feels broken, confusing, slow, or badly designed

I’m happy to test your Android app in return and keep it installed as well.

Thanks, any help would genuinely be appreciated.