I launched my first iPhone app and I’m stuck at 13 downloads. Roast my positioning.
I launched my first iPhone app and I’m stuck at 13 downloads. I’d really appreciate honest feedback from people who have launched products before.
The app is called MealRadar. It helps people figure out what to cook from groceries they already have at home.
The core problem:
You open the fridge, there is food inside, but you still don’t know what to make.
What the app does:
- add pantry/fridge items
- generate recipe ideas
- generate 1, 3, or 5-day meal plans
- help use food before it expires
What I’ve tried so far:
- Instagram Reels
- LinkedIn posts and DMs
- Telegram/Facebook groups
- direct messages
- App Store screenshot improvements
Problem:
I’m getting almost no real users.
I’m not asking for fake reviews or fake downloads. I want blunt feedback:
- Is the idea too weak?
- Is the positioning unclear?
- Is “AI cooking assistant” the wrong framing?
- Where would you find the first 50 real users for this?
- Would you position this around saving money, reducing food waste, or solving the “what should I cook tonight?” problem?
App Store link: [https://apps.apple.com/us/app/mealradar/id6782612975]
I’m open to criticism. I just want to understand what I’m missing.
Trending on Indie Hackers
13 downloads after launch usually means positioning isn’t landing where buyers already complain — not that the app is bad.
Curious: are you looking for those complaints in Reddit / communities, or still iterating the App Store listing only?
I run a small tool that scores fresh pain threads for indie apps. If useful, I can show a quick mapping on a short call — or send a sample if you drop your one-liner + target subs.
That’s fair. I’m trying to do both, but I think the smarter next step is finding the places where people already complain in their own words instead of only polishing the App Store listing.
My current one-liner is:
“MealRadar helps you decide what to cook tonight from groceries you already have, so you don’t end up ordering takeout again.”
I’m thinking the target complaints are probably around phrases like:
If your tool can map fresh pain threads around that kind of language, I’d genuinely be interested in seeing a sample.
Also, if you’re open to it, could you try the app once and tell me if the first-use experience matches that pain or feels too generic? Not asking for a review — just honest feedback.
App Store link: [https://apps.apple.com/us/app/mealradar/id6782612975]
Fair trade, I'll try MealRadar and send you one honest first-use note, no review theatre.
On the sample: I'll scan for threads where people use exactly that language — "ordered DoorDash again," "too tired to decide what to eat," "bought groceries and still ordered food," "wasted groceries again." Each thread gets a 1–10 score + one line on why it matched, so you see the reasoning.
Quick thing I need back: your target subs. r/mealprep, r/EatCheapAndHealthy, r/Frugal, r/Cooking come to mind — but tell me which ones your buyer actually sits in. I'll run it and drop the feed link.
When you get it: pick 2–3 threads, tell me "yes I'd reply" or "no, not my buyer." That's the signal I'm after.
Fair trade — really appreciate it.
My best guess on buyer/user is not “foodie who loves cooking.” It’s more like:
So I’d probably start with:
The phrases I care about most are probably:
What I’m trying to learn is whether the buyer is really:
A) the person trying to save money,
B) the person trying to decide dinner faster,
or
C) the person trying to stop wasting groceries.
If you send a few threads, I’ll mark them honestly as “yes I’d reply” or “no, not my buyer.” And thank you for trying the app — one honest first-use note is genuinely more useful to me than a fake review.
Testing a waste-focused subtitle against the current one is exactly the right move — you learn more from a real A/B than from any opinion (mine included). Ping me if the waste framing wins in installs; that's the kind of concrete signal that's worth writing about publicly. Good luck.
Exactly — I'd rather trust a real A/B than anyone's gut, mine included. I'll report back if the waste-focused framing wins on installs; that's a signal worth sharing. Also worth mentioning: I just shipped a heavy update yesterday, so if you ever take a look, grab the latest version — a lot changed. Thanks again for the nudge, it genuinely helped me commit to testing it properly.
Sample ready — used your subs + the extra phrases (DoorDash / wasted groceries / stop eating out):
https://threadscout-theta.vercel.app/feed/8868d216-853f-4541-b81e-1e0fb01d2e87
Each card: score + why matched.
Manual flags (not in UI):
Pick 2–3 and say “yes I’d reply” or “no, not my buyer.” I’ll also try MealRadar and send short first-use notes after.
This is extremely useful — thank you for actually running the sample.
From your manual flags, the ones that sound closest to my buyer are:
The weaker ones are probably pure meal-prep logistics, because those people already have a planning habit. My user seems more like someone who has food at home but loses the decision battle at 6pm.
I’ll go through the feed and mark 2–3 as “yes I’d reply” or “no, not my buyer.”
Small favor if you’re open to it: when you try MealRadar, could you test only the first-use/UI flow and tell me if it matches this pain or still feels too generic? No review needed. You get free AI allowances, and no sign-up is required just to test the UI.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Quick heads-up: the feed I sent you was a one-time snapshot — that's the free sample. The actual product is that same feed refreshed every morning with new threads.
You already told me the scoring matches your instinct. The open question is whether the daily version turns into real conversations for you. $19 first month, refund if it doesn't — you're not risking anything except finding out.
Want me to switch your feed to daily?
Love this refinement — "has food at home but loses the decision battle at 6pm" is a much sharper ICP than meal-prep logistics. That's the language I'll weight the scoring toward.
I'll try MealRadar's first-use flow and send you one honest note on whether it lands that 6pm-decision pain or feels generic — UI only, no review.
Quick one back so I aim the next digest right: are you personally hunting Reddit/forums for those "too tired to decide" posts day to day, or is that not really your channel yet? That tells me whether a running feed actually saves you time or is premature at your stage.
That refinement makes sense. “Has food at home but loses the decision battle at 6pm” feels much sharper than meal-prep logistics.
Right now, I’m not personally hunting Reddit/forums day to day yet. I’ve mostly been posting on Instagram, LinkedIn, and Indie Hackers, which I’m realizing are probably better for founder feedback than actual user demand. The real user is probably not reading build-in-public posts — they’re searching or venting when they’re tired, hungry, and annoyed at themselves for ordering food again.
So I think your feed is useful, but I also agree it may be premature if I don’t yet know which thread I’d confidently reply to. I’ll use it more as validation language first, not as a full distribution channel yet.
And yes — I’ll wait for your response after you try the app. That first-use note will probably tell me more than another positioning guess. No review needed at all; I just want to know whether the UI lands around the 6pm decision pain or still feels generic.
App Store again for convenience: https://apps.apple.com/us/app/mealradar/id6782612975
I'd separate the product from the buying trigger. "What should I cook tonight?" is a daily frustration, while saving money and reducing food waste are reasons people justify changing their behavior. Understanding which one actually gets someone to install the app is the bigger positioning question.
This is a really useful distinction. I think you’re right — “what should I cook tonight?” is the daily frustration, while saving money and reducing waste are the justifications people use after the frustration is already there.
So the positioning probably needs to lead with the trigger:
“I have groceries, but deciding what to cook feels like work.”
Then the benefits become:
I’m trying to understand whether the install trigger is strong enough from the first screen/onboarding.
If you’re open to it, could you test the app once and tell me honestly whether it matches that trigger or if it still feels like a generic recipe app? No review needed — just blunt feedback would help a lot.
App Store link: [https://apps.apple.com/us/app/mealradar/id6782612975]
I appreciate the invitation.
I haven't tried the app yet, so I don't want to pretend otherwise. My comments so far have been based on the positioning and the way you've described the problem.
I do have a few thoughts about the trigger you described, but I'd rather explain them properly than leave scattered comments in the thread.
If you're open to it, what's the best email to reach you on?
I appreciate this — and totally fair that you haven’t tried it yet.
The trigger thoughts are actually what I need most right now, because I’m realizing the app may not be the main issue. The wording around the pain probably is.
Best email to reach me: [email protected]
Small favor if you’re open to it: could you download it once and test only the first-use/UI flow? No review needed. You get free AI allowances, and no sign-up is required just to test the UI.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Even one blunt note like “this feels generic” or “this matches the trigger” would help a lot.
I'd stop leading with AI and test one sharper promise: "stop buying food twice" (groceries + takeout). That frames it as money leakage, not recipe discovery.
For the first 50 users, I'd look for people already saying the pain in those exact words, then offer a quick pantry plan manually instead of sending them straight to the app. If 10 people take that, the app has something real to automate.
“Stop buying food twice” has honestly stayed in my head since I read your comment. I kept “What can I cook with what I already have?” as the main front-door message, but I think the money-leakage angle is a strong supporting message to test next.
I’ve just released a new MealRadar update today, with a clearer Home experience, better recipe-generation controls, easier pantry cleanup, and smoother scanning flows.
I also like your suggestion of helping the first users manually before trying to automate more. That feels like a much better way to learn what people actually need.
If you happen to use an iPhone and have a few minutes, would you mind taking a quick look at the updated version? I’d genuinely appreciate your honest feedback on whether the positioning and first-use experience feel clearer now.
https://apps.apple.com/us/app/mealradar/id6782612975
Thanks again for being so direct — your feedback was genuinely useful.
Blunt take: I’d stop leading with “AI cooking assistant” and lead with the moment of pain: “Turn what’s in your fridge into tonight’s dinner before it goes bad.” For first 50 users, I’d go where the pain is visible: budget meal prep groups, college/young parent communities, and local food waste groups, then ask people to DM 3 fridge items and manually return recipes. If they like the manual version, then send the app.
Thank you so much for your honest feedback
Glad it helped. If you run only one positioning test, I’d make it this: show 5 people the App Store first screen for 10 seconds, hide it, then ask “when would you open this?”
If they answer “when I want recipes,” the framing is still generic. If they answer “when I’m about to order takeout even though I have groceries,” you’ve got a sharper wedge.
This is a really good test. I like how simple it is: show the first screen for 10 seconds and ask when they’d actually open it.
You’re right — “when I want recipes” is still too generic. The answer I want to hear is closer to “I have groceries but I’m about to order takeout anyway.” That’s the moment I’m trying to own.
I’m shipping a bigger update in the next 24–48 hours to make that clearer in the product experience too, not just the App Store page. Appreciate this — I’m going to use that exact test.
I don't think the idea is the problem. I'd reposition it around "What's for dinner tonight?" rather than "AI cooking assistant." Most people care about solving a daily decision, not the technology behind it. I'd also target communities focused on meal planning, budgeting, and reducing food waste to find your first 50 users.
True words. I really appreciate your suggestion. Maybe you can help a brother out by downloading the app, it's free to even sign up with some bonus AI Allowances. I am not asking for review but just honest feedback after you actually go through the app
Positioning-wise, 'you open the fridge and don't know what to make' is a real, relatable problem — that part's solid. The gap I see is more about where you're putting it: Reels, LinkedIn, Telegram, DMs are all places where people aren't currently mid-frustration about this — you're interrupting their scroll, not answering a question they already have.
Compare that to something like r/EatCheapAndHealthy, r/MealPrepSunday, or r/foodhacks, where people post 'what can I make with X leftover ingredients' pretty much daily. Replying genuinely to those specific posts (not linking the app, just solving their actual question, and mentioning it only if it's naturally relevant) will get you people who are already looking for exactly this, instead of hoping a stranger scrolling LinkedIn suddenly wants a meal-planning app.
Also worth leading harder with the pantry-tracking/receipt-scan angle in your pitch — that's the actual differentiator from someone just asking ChatGPT, and it didn't come through until deep into your post.
This is a really helpful distinction — especially the point that I’ve been interrupting people in broad channels instead of showing up where the question already exists.
I’ve now updated the App Store page, and the new version is live. The first screenshots lead much more clearly with the fridge problem, pantry tracking, and grocery/receipt scanning, because I agree that those are the parts that separate MealRadar from simply asking ChatGPT for a recipe.
Your channel advice is probably the bigger next move. I’m going to spend more time answering real “what can I make with these ingredients?” posts in communities like r/EatCheapAndHealthy and r/MealPrepSunday without forcing the app into the conversation.
Since the updated listing is now live, would you be open to taking another quick look and telling me whether the pantry-tracking and receipt-scan angle now comes through early enough?
App Store:
https://apps.apple.com/us/app/mealradar/id6782612975
I’d genuinely appreciate the same honest read again after the changes.
Just took another look. The subtitle change is a real improvement — "Recipes from your fridge" hits the pantry/fridge angle immediately now, way clearer than before. Couldn't fully judge the screenshots though, they weren't loading for me on this pass — worth double-checking they actually show the receipt-scan/pantry-tracking flow in the first 1-2 frames, since that's the part doing the differentiation work now. Good call focusing on the Reddit communities over broad channels — that's where the "what can I make with X" intent already exists, so it should convert better than cold posting.
Really appreciate you taking another look — especially since you actually downloaded it and gave specific feedback instead of just a quick reaction. That helps a lot.
You’re right about the screenshots/first frames too. I’ve been reworking the app around that exact “pantry/fridge → know what you have → what can I cook?” flow, not just changing the wording.
A bigger update is coming in the next 24–48 hours. Main things I’ve been improving:
The goal is exactly what you pointed out: make the differentiation obvious much faster, especially in the first few seconds.
Thanks again — once this update is live, I’d genuinely value another quick look if you’re open to it. Your first comment was one of the more useful ones.
That list is solid, especially the recipe generation controls — "random mixed meal types" is exactly the kind of thing that makes a first run feel unpolished even when the core idea works.
Happy to take another look once the update's live, just ping me here when it's up ;)
Following up as promised — the new MealRadar update is live now 😊
The mixed meal-type problem you pointed out has been addressed. Smart Recipe now lets users choose Auto, Breakfast, Lunch, or Dinner, and the generated recipe cards have matching meal-type artwork. I also made the Home starting options clearer, added easier pantry cleanup, and improved the scan flows.
If you still have time to take another look, I’d genuinely appreciate your honest feedback — especially on whether the first few minutes now feel more focused and polished. No pressure at all.
https://apps.apple.com/us/app/mealradar/id6782612975
Went and looked at the updated listing. Honest read: the sharper framing IS there now — "before groceries go bad or takeout wins again" in the first line is exactly the right sentence. But the title and subtitle still lead with the weak angle: "What to cook / Recipes from your fridge" is the crowded promise, and it's all a browser sees in search results before tapping. If waste/money is your wedge, it belongs in the subtitle. One more thing: the feature list is ~18 bullets — the three that sell (scan receipt → recipes from what you have → expiring-soon alerts) are buried in the middle. Cut or reorder and the listing will match the sharper story. Fast shipping, by the way — update was live in a day. 👏
Thank you for going back and looking at it again—this is genuinely useful.
I think you’re right that the description is still trying to communicate too many things at once. The core journey should be much easier to see: quickly capture what you have, get recipes from those ingredients, and use food before it expires. Right now, that story is buried under a long feature list.
Your point about the title and subtitle is fair too. I chose “What to Cook” and “Recipes from your fridge” because they make the app immediately understandable and match what people may actually search for. But I agree that they communicate the category more than they differentiate MealRadar.
The waste and money angle is probably the sharper wedge. I don’t want to replace the current wording blindly, but I’m going to treat a waste-focused subtitle as something to test against the current version.
I’ll also shorten and reorder the description when I next update the listing. Thanks again for being specific—and for checking the update so quickly. This kind of feedback is exactly what helps me improve it.
Nice, love that you shipped this so fast 🙌
A couple things I can already see from the updated App Store listing:
The title/subtitle dropped the "AI cooking assistant" framing — it's now "MealRadar: What to cook" / "Recipes from your fridge", which is exactly the direction we were talking about: lead with the pain point, not the tech. That alone should help conversion from search/browse.
Splitting Smart Recipe into Auto/Breakfast/Lunch/Dinner makes sense — the "it generated dinner when I wanted breakfast" problem was killing trust in the quick result.
I'll reinstall it this week and give you concrete feedback on the first few minutes (onboarding, first recipe generated, whether the "smart waste coach" is self-explanatory). One thing I'd flag even before opening it: the price ($4.99/mo or $49.99/yr) is a big barrier for an app with zero reviews yet — I'd try a longer free trial or a cheaper one-time unlock just for the first few weeks, until you have real reviews doing the social-proof work.
Will report back once I've tried it.
Thank you—I really appreciate you noticing those changes. The new positioning and the breakfast/lunch/dinner controls came directly from feedback like yours.
One useful clarification before you test it: you don’t need to subscribe to try the AI features. Anyone who signs up with an email receives free AI allowances, which should let you test pretty much the whole experience—including Smart Recipes, scanning and the Smart Waste Coach.
The new onboarding explains the choice between continuing as a guest and signing up with an email. We can’t provide the AI-powered features in guest mode because we need an account to enforce usage limits, protect the service and prevent misuse of the AI.
Since you previously had the app installed, deleting it and reinstalling it will also let you see the redesigned splash screens and onboarding flow. From there, choose the email sign-up option and you’ll receive the free AI allowance.
Your point about pricing is completely fair, though, and I’m not dismissing it. Once you’ve tested the free allowance, I’d be genuinely interested to know whether the subscription still feels like too much of a barrier.
Thanks again for taking another look. I’m looking forward to your blunt feedback on the onboarding, first recipe and Smart Waste Coach.
Haven't had a chance to sit down and actually test it yet — want to give it a proper 10-15 min run (onboarding, email signup, Smart Recipe, Waste Coach) rather than a rushed glance, so the feedback is actually useful to you.
Will follow up this week with real impressions once I've been through it.
Really appreciate you taking the time to do a proper run rather than a quick glance — that means a lot. Quick heads-up before you dig in: I pushed a pretty heavy update just yesterday, so please update to the latest version first. A lot changed under the hood (onboarding and the recipe side especially), and testing the old build would give you a misleading picture. Looking forward to your impressions whenever you get to it — no rush.
This comment was deleted 16 days ago.
Great that you're asking for a roast early — that mindset alone puts you ahead.
One thing I'd push on: the name "MealRadar" creates a mismatch. "Radar" implies scanning for things outside — restaurants, deals, trends. But your core value is using what's already inside the fridge. That friction might be making the value prop harder to grasp in the first 3 seconds on the App Store.
On the distribution side: the communities that have the exact pain you're solving aren't on Product Hunt or IH. They're in cooking/budget subreddits and Facebook mom groups asking "what can I cook with chicken thighs and potatoes?" I've seen this pattern building a content tool for small shop owners — the best early traction came from showing up in the exact moment of pain, not from launch posts.
My concrete suggestion: spend one week just answering "what should I cook with [X]" questions in r/EatCheapAndHealthy or r/Cooking — don’t even mention the app. Just be helpful. You'll learn fast whether your core idea resonates, and when you do mention MealRadar, people will actually care.
The 13 downloads isn’t a failure — it’s a sample size of zero. You haven’t found distribution yet, which is a completely different problem than positioning.
This is really useful, especially the distinction between a positioning problem and a distribution problem.
I think you’re right that 13 downloads was nowhere near enough evidence to keep rewriting everything endlessly. That said, I did use the feedback from this thread to make one focused App Store update, and it is now live.
The new listing leads with the actual moment rather than the category: “Fridge full. No dinner idea?” It also brings the pantry and scanning mechanics much earlier in the screenshots.
I’m not planning to keep changing the page every few days now. The next test is distribution: spending time in one or two communities, answering real “what can I cook with this?” questions, and learning how people describe the problem in their own words.
Your point about the name is interesting too. I originally thought “Radar” suggested scanning what is already around you, but I can see how it could imply restaurants or outside discovery. I’m not renaming it now, but I’ll watch for that interpretation.
Would you be open to taking another look at the updated App Store page and telling me whether the first three screenshots now explain the app faster?
https://apps.apple.com/us/app/mealradar/id6782612975
Also, which one or two communities would you start with first rather than spreading across several?
where you're getting hurt: you're selling three jobs at once (decide dinner / save money / stop waste) plus "AI cooking assistant." people don't install a category. they install relief for one moment. the sharpest one in your own post is: fridge is full, still ordering takeout. lead with that. money + waste are the proof after the first win, not the front door.
This was one of the clearest pieces of feedback I got from the thread.
You were right that I was trying to sell three outcomes at once, plus “AI cooking assistant,” which made the message feel broader instead of stronger.
I used that feedback in the App Store update that went live yesterday. The new listing now leads with the specific moment:
“Fridge full. No dinner idea?”
The pantry-to-recipe flow comes first, while saving money and reducing waste now appear later as proof of the value rather than competing for the headline.
Would you be open to taking another look at the updated App Store page and telling me whether the first three screenshots now feel focused enough?
https://apps.apple.com/us/app/mealradar/id6782612975
I’d genuinely appreciate the same blunt read now that the update is live.
Honest answer first, because it reframes everything else: at 13 downloads you don't have a positioning problem, you have a reach problem, and they get fixed in opposite ways. Positioning only matters once people are seeing the app and not converting. Right now almost nobody has seen it, so you have zero signal about the copy. Don't rewrite the store page a sixth time chasing 13 installs.
That said, you asked for the roast, so:
You're stacking three value props (recipes from what you have, meal plans, using food before it expires). Three benefits reads as none. Pick one. And drop "AI cooking assistant" completely. In 2026 that phrase doesn't signal a feature, it signals a ChatGPT wrapper, and it invites the question that kills you: "why wouldn't I just ask ChatGPT what to cook?" You have to answer that in your first line.
Your sharpest angle is the one you're burying: stop throwing away food you already paid for. "What should I cook tonight" is owned by ChatGPT and every recipe app alive. But knowing what's about to expire and saving real money is specific, it has a villain (waste), and it's the one thing a generic chatbot can't do, because it doesn't know your fridge. Lead with money and waste, make the expiry tracking the hero, and let recipe generation be the mechanism, not the headline.
On your first 50: the channels you tried are broad and cold. Go where this pain already lives. r/EatCheapAndHealthy, r/MealPrepSunday, r/Frugal, r/ZeroWaste, budget-cooking and zero-waste Facebook groups. Not app or startup groups, communities of people already annoyed about wasting food and money. Show up as a member solving it, not a founder with a link.
I've shipped a few apps solo this year and hit this same wall, so happy to go deeper on any of it. One question back: when someone first opens MealRadar, how many taps until they get one useful recipe? That first-run friction is usually where the few visitors you do get quietly bounce.
Also, if a user already has pantry items added then it'd literally them 2 -3 taps to generate a recipe.
This is a very helpful reframe.
I agree that with only 13 downloads, I didn’t have enough signal to keep rewriting the store page repeatedly. I did make one focused update from the feedback in this thread, and that version is now live.
I removed “AI cooking assistant” from the lead, rebuilt the screenshots around the fridge and pantry problem, and made the actual flow much more visible: scan what you have, get a useful recipe, shop only for what is missing, and use expiring food first.
Your waste-and-money argument still stands out to me because it gives MealRadar a more specific enemy than generic dinner indecision. The app knows what is in the pantry and what is at risk, which a generic chatbot does not know unless the user rebuilds that context every time.
I’m not ready to abandon “fridge full, no dinner idea?” as the front door yet, but I do want to test it against “stop wasting groceries you already paid for” with real users rather than debate it theoretically.
The other thing I need to measure properly is first-use friction. Right now, users need to add or scan pantry items, select ingredients, and then generate a recipe. I should record the exact taps and time from first open to the first useful result.
Since the updated listing is live, would you be willing to look at the first three screenshots again—or ideally test the app once—and tell me whether the core path is now obvious without explanation?
App Store:
https://apps.apple.com/us/app/mealradar/id6782612975
And on your “one useful recipe” test: would you measure from a completely empty pantry, or from the moment a user has scanned a few items?
Im interested, how ci o get started?
Glad you’re interested.
You can get started by downloading MealRadar from the App Store, creating a free account, and adding a few ingredients you already have. You can type them in or use the scanner, then select what you want to cook with and generate a recipe.
App Store:
https://apps.apple.com/us/app/mealradar/id6782612975
It’s free to download and sign up. After you try it, I’d really appreciate one honest note on what felt clear or confusing in the first few minutes.
Positioning roast, as requested: "figure out what to cook from groceries you already have" describes a feature, not a moment. The moment is 6pm, tired, staring at a full fridge with zero ideas. Lead with that exact second in your subtitle and first screenshot and the listing gets sharper immediately. But honestly, 13 downloads is not a positioning problem yet, it is a distribution problem. At this stage every install comes from a conversation, not store search. Pick one watering hole where the pain lives (meal prep communities, budget cooking, busy parents), be genuinely useful there for two weeks, and write down the exact words those people use to describe the 6pm problem. Then steal their language for the listing. Store SEO starts mattering after the first few hundred installs, not before.
The "moment, not feature" distinction is useful. I'd separate listing conversion from distribution with one small test: send 20 qualified people directly to the page, then measure page view to install. If that ratio is weak, fix the listing; if it's strong, the bottleneck really is finding the right traffic.
This is a very fair roast, especially the distinction between a feature and a moment.
“Figure out what to cook from groceries you already have” explains what MealRadar does, but “6pm, tired, full fridge, zero ideas” explains why someone would care right now. I’ve changed the App Store screenshots and messaging around that exact situation, including leading with the fridge problem rather than “AI cooking assistant.”
Your distribution point is probably even more important. At 13 downloads, I agree I still need conversations more than clever SEO. I’m going to spend more time in places where people already talk about meal-planning fatigue, budget cooking, leftovers, and the “what do I make with this?” problem, and pay close attention to their actual wording.
A small favor, only if you’re open to it: could you download MealRadar, create a completely free account, and try the first-use flow once? I’d genuinely appreciate one blunt opinion here on whether it feels built for that 6pm moment or still feels too broad.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
13 downloads for a first launch isn't actually bad, it just means nobody who's seen it yet is the right person. The framing question you're asking (money vs waste vs "what to cook") is a real one but I'd argue it's secondary to the bigger issue: an AI cooking assistant is competing against a category people already half-trust (Paprika, Mealime, even just googling) so the App Store listing alone has to do all the convincing with zero context. That's a brutal sell.
I'd pick ONE of those three angles based on who's actually messaging you or leaving reviews, not who you imagine your user is. If nobody's told you why they downloaded it, you don't have enough data to position confidently yet, you just have guesses. So honestly your first job isn't better copy, it's finding 20 people who have the specific problem and watching what they say about it in their own words.
Where I'd look: people already complaining about meal planning fatigue, not people browsing the App Store. Reddit's cooking/mealprep subs, IH itself, even Twitter threads about food waste. The trick is finding the complaint before it turns into a search.
I actually built a tool for exactly this moment, it's called Getrive, it watches Reddit/HN/IH for people describing the problem you solve and drafts a reply for you to approve. Built it because I was in your exact spot, guessing at positioning with no users to ask. Might help you skip some of the guessing.
This is thoughtful and honestly a good reality check.
You’re right that I don’t yet have enough users to confidently declare which angle wins. Money saved, food waste reduced, and deciding what to cook are still partly hypotheses until I hear people explain in their own words why they downloaded and whether they came back.
I’ve chosen the dinner-decision moment as the front door for now, because it is the most immediate pain, while savings and waste reduction become proof afterward. But I agree that the real work is finding people who already experience the problem and listening rather than polishing copy in isolation.
Your suggestion to look for the complaint before it becomes a search is especially useful. I’m going to study meal-prep, cooking, budgeting, and food-waste conversations much more closely. I’ll also take a look at Getrive—the problem you built it around is exactly the one I’m facing.
A humble request, if you have a few minutes: could you download MealRadar, sign up completely free, and test the core flow? I’d be very grateful if you came back here with one honest user opinion—especially what problem you felt the app was really solving after using it.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
I took a quick look of the app, I'm being honest with you. A few points I noticed:
Overall, from my point of view it looks a little unfinished, but the concept itself is good, you could take more time improving the user experience and the design itself. Keep your head up and keep working and shipping it will be great :)
Thank you for taking the time to actually open the app and give me specific feedback. This is honestly one of the most useful reviews I’ve received so far.
You’re right about the splash screen — that should absolutely not be showing an Expo demo image, and I’m fixing it immediately.
The example data was intended to prevent the first screen from feeling empty, but I can completely understand why it looks like leftover testing data and makes the app confusing. I also agree that the onboarding needs to explain the guest/account choice more clearly, and that the Account area and some other screens need a cleaner hierarchy.
I’m not going to defend those issues — I’m adding them to the immediate improvement list:
Thank you again for being direct but constructive. Once I’ve improved these areas, I’d genuinely appreciate it if you could take another quick look and tell me whether the first-use experience feels clearer.
Hi I wanted to come back and update you because your review was genuinely one of the most useful and honest pieces of feedback I received.
The new MealRadar update went live today, and several of the changes were directly influenced by the problems you pointed out:
I remember you said the concept was good but the app felt unfinished. I would honestly be very pleased if you could see how it feels now after these changes.
If you have time to take another look, I’d be extremely grateful for the same blunt feedback you gave me before. Please don’t hold back or try to be polite about anything that still feels confusing or unfinished — that directness helped me improve the app.
https://apps.apple.com/us/app/mealradar/id6782612975
Thank you again for taking the app seriously enough to review it properly.
courage bro
Thank you, honestly. Launching something for the first time has been much more humbling than I expected, so even a simple message like this helps.
I’m trying to improve it one honest piece of feedback at a time. If you ever have a few minutes, I’d be grateful if you downloaded MealRadar, signed up for free, and told me what feels confusing or unnecessary.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
The ratio here is the signal worth paying attention to: 9 likes and 54 comments against only 13 downloads means the pitch worked well enough to get people to engage, but something between "I read this post" and "I have the app open" isn't converting. That gap is usually one of three things: the App Store listing doesn't carry the same specific hook this post does (fridge, food, don't know what to make), the screenshots show generic recipe cards instead of the pantry-tracking mechanic that's the actual differentiator, or there's a sign-up wall before someone can see the pantry-to-recipe loop in action.
Worth checking directly: does your App Store screenshot #1 show the barcode/receipt scan into a pantry, or does it show a recipe result? If it's the recipe result, you're competing visually with every recipe app in the category instead of showing the one mechanic they don't have.
This was extremely helpful. Your point about the gap between “I read the post” and “I opened the app” is exactly what I needed to hear.
I’ve now rebuilt the App Store screenshots around the actual mechanics instead of generic recipe-app visuals. The first screens focus on the fridge problem, pantry tracking, scanning groceries and receipts, and turning what you already have into a meal.
I also made sure the pantry-scanning mechanic appears early rather than being buried later in the screenshot sequence.
Would you be open to checking the updated listing and testing the app itself? MealRadar is free to download and create an account. I’d really appreciate one honest opinion on whether the listing and first-use experience now feel like the same promise.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Blunt answer to #5: position it around 'what should I cook tonight,' because that is the moment people actually reach for their phone, and saving money is the outcome you prove later. The bigger problem is channel, since nobody discovers a utility app through LinkedIn DMs. Your buyer is scrolling food TikTok and Reels, so show the fridge-to-dinner moment in 15 seconds, post daily for 30 days, and keep the App Store link in bio.
That distinction between the moment and the outcome really helped me.
“What should I cook tonight?” is the immediate reason someone reaches for the app. Saving money and reducing waste matter, but they become proof after MealRadar has already solved the dinner decision.
I’ve now shifted the App Store positioning toward “Fridge full, no dinner idea?” and “Recipes from your fridge,” instead of leading with “AI cooking assistant.”
Your channel advice is fair too. I spent too much time in founder-heavy places where people may engage with the story but are not necessarily the person opening the fridge at 6pm.
Would you be willing to download it, create a free account, and test the first-use flow once? I’d really value your opinion on whether the app now delivers the fridge-to-dinner promise quickly enough.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
I don't think the app is the main issue. I think the positioning is. 'AI cooking assistant' describes the tool, not the benefit.
I'd test messages like: • 'What can I cook with what's already in my fridge?' • 'Save money by using food before it expires.'
One question. What's your Day 1 retention? Do users come back after the first recipe, or do they leave? That would tell me whether the problem is marketing or the product.
You were right that “AI cooking assistant” described the technology rather than the benefit.
I’ve changed the positioning toward the actual situation: having groceries at home and still not knowing what to cook. The new subtitle is “Recipes from your fridge,” and the screenshots now focus much more directly on the pantry-to-meal outcome.
Your retention question is also important. My user count is still too small for a meaningful Day 1 retention conclusion, but I’m now treating the flow as a funnel: first open, food added or scanned, recipe generated, and second open. That should help separate an acquisition problem from a product problem.
If you’re open to it, could you download MealRadar, create a free account, and test it once? I’d be grateful for one honest note on whether you would personally have a reason to return after the first recipe.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
It's normal for a first iOS app with no clear distribution yet.
A few things I’m curious about the publishing side- How was the App Store submission process for you any rejections, confusing guidelines, or parts that slowed you down?
Thank you. The submission process was definitely more complicated than I expected.
The biggest friction points were understanding which App Store fields were locked after release, creating a new version just to update important metadata, producing screenshots in Apple’s exact accepted dimensions, removing transparency from PNG files, and then uploading a new build even though this particular update was mainly about positioning and store assets.
The guidelines were manageable once understood, but the small technical requirements slowed me down more than the actual product work.
Since you’re interested in the publishing side, I’d also be grateful if you downloaded MealRadar, created a free account, and told me whether the finished App Store page sets the right expectation for the app.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
yeah, sure, I will test on my side
Thanks so much !
Congrats on launching! Stuck at 13 downloads usually points to positioning and visibility challenges. Have you tried testing different app store keywords or leveraging micro‑influencers to boost discovery?
Love how you refined the positioning! The fridge‑based angle feels much clearer. I’ll check out MealRadar and share feedback soon — your focus on conversion before scaling is spot‑on.
Thank you. I’ve started working directly on the App Store side now.
I changed the subtitle toward “Recipes from your fridge,” rebuilt the screenshots around the real fridge and pantry problem, and revised the keywords so the listing is less dependent on generic “AI cooking” language.
Micro-influencers are something I haven’t tested properly yet. I agree that a few small creators with the right food, meal-prep, budgeting, or food-waste audience may be more useful than broad posting.
Before spending more on distribution, I’m also trying to confirm that the listing and first-use flow actually convert.
Would you be open to downloading MealRadar, creating a free account, and sharing one honest opinion on the listing and onboarding experience?
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
the problem is super relatable, thats not your issue. two things stand out. 1) youre positioning on the category (ai cooking assistant) instead of the moment. nobody wakes up wanting an ai cooking assistant, they want to not stand at the open fridge at 6pm exhausted with random ingredients and no plan. lead with that exact scene. ai is the how, not the hook. 2) reels and linkedin are broadcast, theyre not where the pain lives. go where people literally already ask this: r/eatcheapandhealthy, r/mealprep, r/cooking, the endless "i have chicken rice and spinach what do i make" posts. answer those for real with an actual recipe (from your app), then mention the app makes it instant. thats showing up at the moment of pain instead of shouting at a feed. on framing, save money and less waste are outcomes, but the wedge is dinnertime decision fatigue. "stop staring at the fridge" will out-pull "ai cooking assistant" every time.
This is one of the clearest explanations I’ve received.
You’re right: nobody wakes up wanting an “AI cooking assistant.” They want to stop staring into the fridge with random ingredients and no plan. AI is only how the result is produced, not the reason someone cares.
I’ve now rebuilt the App Store message around that exact moment. The lead is closer to “Fridge full, no dinner idea?” and the supporting screens show scanning food, tracking the pantry, generating a meal, shopping only for what is missing, and reducing waste afterward.
Your point about showing up where the pain already exists is also important. Answering real “I have chicken, rice and spinach—what can I make?” questions is much more aligned than broadcasting another founder update.
A humble ask: would you be willing to download MealRadar, create a free account, and test the core path yourself? I would genuinely value a blunt opinion on whether the app now feels focused on dinner-decision fatigue or still feels too broad.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Before coming up with a product idea, I always ask myself: Could I get the same result just by chatting with AI? Is there already an existing product for this? Your idea is great, but right now I'd probably just ask ChatGPT directly.
Really appreciate this — it's the right question to ask, and honestly it's the exact objection I built MealRadar to answer.
You're right that ChatGPT can suggest a recipe if you type out everything in your kitchen. The problem is the typing it all out part. MealRadar exists because the friction isn't "generate a recipe" — it's knowing what you actually have, keeping it current, and not having to think about it at 6pm when you're tired and hungry.
Here's what it does that a chat window doesn't:
Instead of listing ingredients from memory, you add and manage a pantry that MealRadar helps you build by scanning food items and product barcodes — or even scanning your grocery receipt. From that live pantry it generates smart, AI-powered recipe ideas from the ingredients you already have, and when you pick a recipe it updates your pantry items automatically, so the next suggestion stays accurate (ChatGPT forgets the second you close the tab). Anything you're missing, it turns into a shop-missing-ingredients list.
It also remembers the stuff you'd otherwise re-explain to an AI every time: it tracks your allergies, diet preferences, and local app settings, lets you choose a cooking style or cuisine — Indian, Italian, German, French, Spanish/Latin, Portuguese/Brazilian, or Global/Flexible — and builds meal plans based on your pantry. You can save your recipes, meal plans, and shopping lists, choose the language you use the app in, and start in guest mode or create an account for premium features. The whole thing is built to help you make practical meals, use ingredients before they expire, and find new ways to cook with what you already have.
So the honest framing: ChatGPT is a blank box you feed every time. MealRadar is the memory and the eyes — it already knows what's in your kitchen, what's expiring, and what you can and can't eat, and turns that into dinner in a couple of taps. That's the gap I'm betting on.
That said — you might be exactly the user I should learn from. If you tried it and still felt ChatGPT was faster for you, I'd genuinely want to hear where. Fair?
The strongest clue is in your reply: receipt scanning already exists, yet the original description led someone to request it. That is not a feature gap; it is a first-10-seconds comprehension gap. I'd test one App Store promise — 'scan a receipt, cook before groceries expire' — and see whether 10 people can predict the workflow before installing. Which screenshot currently shows the receipt-to-pantry step?
It also has grocery Item scanning feature where user can simply take a picture of grocery items and it'd update their pantry. Not only that, but it also has a feature where users can scan any handwritten recipe, and it'll add the recipe to their saved recipe. It has a feature where user, if decides to choose a recipe to cook, app will automatically update their pantry and add the missing items to their shopping list as per the shopping habit which later can be shared with anyone. Users can save any AI generated recipe and share. User has an option to shop missing ingredients. User can choose their diet options, set their allergies. Users can set their meal notification. App even generates local recipes without AI. Users can set their theme, language. I'd really appreciate if you could take a look on my app so you can see what I have created.
The scanning flow is the part I'd put first because it matches the "I already have food" moment. For the first-use test, hide the breadth and show one path: photo pantry -> one dinner suggestion -> missing-items list. If that path isn't obvious in under a minute, themes, sharing, and recipe storage will make the positioning feel broader, not clearer.
I agree. The scanning flow is MealRadar’s clearest connection to the “I already have food” moment, and it should be obvious before someone sees the wider feature set.
I’ve now moved that mechanic much earlier in the App Store story: scan groceries or a receipt, build the pantry, get a dinner idea, and identify only what is missing. I’ve also tried to stop presenting every feature at once.
Your under-a-minute standard is a good one. If the core loop cannot explain itself quickly, more themes and secondary features will not rescue it.
Would you be open to downloading MealRadar, creating a free account, and trying that single path? I’d really appreciate a direct answer on whether the scan-to-dinner journey feels obvious without explanation.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
I can't commit to an iPhone test right now, so I won't pretend otherwise. The clean test is still narrow: fresh account, scan one receipt, stop the clock at the first plausible dinner, and note every label that needs explanation. That gives you an activation measure you can compare across screenshot and onboarding changes.
ok no problem, I guess there are hundreds of people to share their knowledge without actually looking at the product.
Fair call. My earlier note was about the positioning argument, not a product review, and I should've made that boundary explicit instead of sounding like I'd tested the app. I won't pretend otherwise; the only claim I can stand behind from this thread is that 13 downloads isn't enough evidence to choose among the three angles.
How about adding a food scanner to scan the food and making recipes instead of mannual entry?
You’re right — and the funny part is MealRadar already has that.
You can scan grocery items, scan a grocery receipt and it automatically adds the item in your pantry along with name count, weight etc, or add pantry items manually. I probably didn’t make that obvious enough in the post or the screenshots, which is a positioning/listing problem on my side.
Small favor if you’re open to it: could you download it once and tell me if the scan flow is clear enough from the first-use experience? No review needed — just honest feedback.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
On your Q5 — I'd position around the food-waste guilt, and here's the reasoning: "meal planner" and "what to cook tonight" both name what MealRadar does, but people don't adopt tools, they adopt relief from a nagging feeling. Nobody lies awake wanting a meal planner. They lie awake vaguely guilty about the cilantro wilting in the drawer. "What to cook tonight" is mild daily friction; wasted food is a small recurring guilt — and guilt converts harder than convenience. Name the guilt, win the download.
One honest question back: of your 13, has anyone opened it a second time? At that size it's basically noise, I know — but if people aren't returning, the App Store listing might be the wrong fire to fight first. A leaky bucket doesn't care how you fill it.
This is a really interesting take because it frames food waste as the emotional trigger, not just a “nice benefit.”
I think you’re right that nobody wakes up wanting a meal planner. They feel guilt when food they already paid for goes bad. The line “name the guilt, win the download” is something I’m going to keep in mind.
On the second-open question: with only 13 downloads, I honestly don’t have a clean signal yet. But I agree with the point — if people install and don’t come back, then the first-use experience or core loop is the bigger problem than the listing.
Small favor if you’re open to it: could you try MealRadar once and tell me whether the UI makes the “use food before it goes bad” value obvious enough? No review needed, just blunt feedback.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Shipped 10+ iOS apps, ran ASA campaigns across all of them. A few things jump out:
"AI cooking assistant" is the wrong keyword frame. Way too competitive and generic. People don't search "AI cooking assistant" — they search "what to cook with what I have" or "meal planner from ingredients." Your positioning should match actual search intent.
Your first 50 users for a utility app almost never come from social media. They come from App Store search. Run a quick experiment: check what autocomplete suggestions Apple gives for "meal plan" / "cook with ingredients" / "fridge recipes." Those are your real keywords.
The subtitle and first screenshot are doing 90% of the conversion work in the App Store. If your subtitle doesn't instantly communicate the core value ("Turn your fridge into a meal plan"), you're losing people before they even read the description.
Positioning: I'd go with "stop wasting food" over "AI cooking." Food waste is emotional — people feel guilty about it. "AI" is table stakes now, not a selling point.
For the first 50 users: find the subreddits where people post "what can I make with X" photos (r/whatshouldicook has 200K+ members). Don't promote — just help people, and add your app to your profile bio.
The idea isn't weak. The App Store listing and discovery channel are what need work.
This is extremely practical. Thank you.
The App Store search point is probably something I underweighted. I’ve been treating social posts like the main discovery channel, but for a utility app, people may be searching the App Store for phrases like “what to cook with what I have,” “fridge recipes,” or “meal planner from ingredients.”
Also agree on the subtitle and first screenshot. If the first screenshot doesn’t immediately show “turn your fridge into dinner,” people won’t dig into the description.
I’m going to check Apple autocomplete around those keywords and rethink the first screenshot around the fridge-to-meal-plan flow.
Small favor if you’re open to it: could you download MealRadar once and tell me whether the first screen/screenshot promise matches the app experience? No review needed — just honest first-use feedback.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Of the three, "you have food and still don't know what to make" is the one I would lead with, the money and waste savings are things people realize after, not what makes them tap install. The harder part at 13 downloads: you cannot really A/B the three angles yet, the traffic is too thin to tell which line actually moved installs versus noise. Are you picking the positioning off gut and store-page views right now, or is something giving you a readable signal at this volume?
That’s fair. At 13 downloads, I probably shouldn’t pretend I have enough traffic to truly A/B test anything yet.
Most of this is still qualitative signal: repeated comments here, App Store views, and how people react to the wording. The strongest pattern so far is that “AI cooking assistant” feels generic, while “you have food and still don’t know what to make” feels more like a real moment.
So I’m not treating it as proof yet — more like direction.
Small favor if you’re open to it: could you try the app once and tell me if the first-use flow actually supports that “food at home but no idea what to cook” angle? No review needed.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
The A/B/C audience split you're doing here (save money vs. decide faster vs. stop wasting food) is smart - most people skip that step and just guess. One thing that's worked for me when narrowing down who my own tool was actually for: instead of asking "would you use this," find people already complaining about the exact moment your app solves (like your "food went bad in my fridge" phrase list), and see which phrase actually gets upvotes and replies vs. which gets ignored. The engagement pattern on the phrase itself tells you more than a survey would - it's basically free validation before you even mention the app.
This makes a lot of sense.
Instead of asking people hypothetically “would you use this?”, I should probably watch which real complaints get engagement first. If “food went bad in my fridge” gets replies and “meal planner” gets ignored, that tells me more than a survey.
I’m starting to see that the language people already use matters more than the category I think I’m in.
Small favor if you’re open to it: could you download MealRadar once and tell me which pain it feels closest to after first use — deciding dinner, saving money, or avoiding food waste? No review needed, just honest feedback.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
@Siadish First of all, congratulations on actually shipping the app! Getting to the launch line is a massive hurdle. I recently rolled out my own mobile app (PurrTrack) and the reality is that the native App Store algorithms give almost zero organic visibility to new developers. Have you started submitting your app to SEO directories like AlternativeTo, or are you relying strictly on social media/App Store search right now?
Thank you — and congrats on launching PurrTrack too.
Right now I’ve mostly been relying on social, App Store search, and founder/community feedback. I haven’t seriously submitted to SEO directories like AlternativeTo yet, so that’s a good push.
The more feedback I get, the more I think my discovery problem is partly channel and partly wording. People don’t search for “AI cooking assistant.” They search for things like “what can I cook with what I have?”
Small favor if you’re open to it: could you try MealRadar once and tell me whether it feels understandable from the first-use flow? No review needed, just blunt feedback.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Hey Siadish, I would absolutely love to give the first-use flow a test for you, but unfortunately, I'm completely on Android these days and don't have an iPhone to download it! If you ever drop a Google Play version, definitely ping me and I'll gladly give you some blunt feedback. By the way, your shift from "AI cooking assistant" to "what can I cook with what I have" is a massive improvement. Good luck with the continued push!
Thanks so much — and no worries at all about not having an iPhone! The new iOS update is live now, with a clearer first-use experience and a stronger focus on helping people answer “What can I cook with what I already have?”
The Android version is still going through Google Play testing, but I’ve saved your offer and I’ll definitely ping you when it becomes publicly available. I’d genuinely appreciate the blunt Android feedback when the time comes 😄
And thank you for confirming that the positioning shift feels stronger. That was one of the biggest things I wanted to improve.
One mistake I made that might transfer: I priced (and framed) my first product against the wrong category, not the wrong customer. I compared myself to the ambitious thing I felt I'd built (€179, SaaS-boilerplate league) when real comparables for what buyers saw sold for a third of that. Repricing was easy; noticing the category error took embarrassingly long.
"AI cooking assistant" feels like the same error — it's the category you see from inside. From outside, nobody searches for an assistant; they stand in front of a fridge at 7pm. I'd commit 100% to the "what do I cook tonight with what I already have" angle: it's the only one of your three that's a moment (with a time and a place) rather than a virtue. Money saved and less waste are outcomes you mention on the way, not the hook.
This is a very useful comparison.
I think I’m making the same category mistake. “AI cooking assistant” is how I see the product from the inside. From the outside, the user is just standing in front of a fridge at 7pm trying to figure out dinner.
So the hook should probably be:
“What do I cook tonight with what I already have?”
Then money saved and less waste become supporting benefits, not the headline.
Small favor if you’re open to it: could you download MealRadar once and tell me if the app actually lands around that moment, or if it still feels like a generic AI recipe app? No review needed.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
The positioning I’d visualize is the 6pm moment: the fridge has food, but you have no idea what to cook — then MealRadar turns those ingredients into dinner options. That communicates the value much faster than “AI cooking assistant.” If you send me the key screens, I can create a short watermarked concept around that scenario. If you like the direction, the finished 15–20 second video is $19.
That’s exactly the visual direction I’m starting to see too.
The 6pm moment is much easier to understand than “AI cooking assistant”: fridge open, food is there, no idea what to cook, then MealRadar turns those ingredients into dinner options.
I’m already working on new screenshots/reels around that scenario, so this confirms the direction.
Here i have created a video on my own so if you could kindly take a look and then tell me your feedback : https://www.facebook.com/share/r/1H62ZmHK7u/
Small favor if you’re open to it: could you try the app once and tell me whether the actual first-use flow matches that fridge-to-dinner story? No review needed — honest feedback is enough.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
The problem description is clear and relatable, but the name "MealRadar" is doing some heavy lifting it can't carry on its own. "Radar" suggests finding things that are out there — restaurants, deals, options — not using what you already have. The name is subtly pointing in the wrong direction.
The actual value prop is pantry-first cooking: "you have stuff, we turn it into meals." A name that leads with that concept would align the positioning immediately. Something like PantryAI, FridgePilot, or CookFromHome signals the exact moment of use without needing any explanation.
Another issue: 13 downloads suggests the App Store listing isn't converting, not just that people aren't finding it. The first screenshot and the subtitle line do most of the work. If those don't show a fridge opening followed by a meal plan in 2 steps, you're losing people in under 3 seconds.
Fix the name direction, tighten the first screenshot, and your conversion rate will almost certainly jump before you touch acquisition.
This is sharp, and I see what you mean about the name.
MealRadar made sense to me because it “detects” what you can cook from your food, but I can see how “radar” might suggest restaurants, deals, or external options instead of pantry-first cooking.
For now, I probably can’t rename immediately, but I can make the positioning do less explaining. The first screenshot and subtitle need to scream: “you have stuff, we turn it into meals.”
That part is very actionable.
Small favor if you’re open to it: could you download MealRadar once and tell me whether the current UI overcomes the name confusion, or if the name/listing still points you in the wrong direction? No review needed.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Launching is already a big achievement. I'd spend more time understanding where your target users hang out than making product changes immediately. Even 10–20 conversations with potential users can reveal much more than download numbers alone. Good luck!
Thank you. I needed this reminder.
It’s tempting to keep changing product details because 13 downloads feels bad, but you’re right that conversations with actual target users probably reveal more than the number itself at this stage.
The big question now is where those users actually hang out and what exact words they use when they’re stuck.
Small favor if you’re open to it: could you try MealRadar once and give me one honest first-use note? No review needed. I’m trying to learn whether the app solves the problem clearly or if the positioning is doing too much work.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
The three buyers you listed (save money / decide faster / stop wasting) aren't one app — they're three different first screens. My honest take: pick ONE for the launch, even though the app does all three. "Stop wasting groceries" is the most visceral — the pain has a face, you literally watch money rot in the fridge. "Save money" is too abstract, "decide dinner" too mild. Lead with the guilt of the thrown-away food and the other two come along for free. You can serve all three; you can only position for one.
This is a strong point: one app can serve all three, but it can’t position as all three at launch.
I’m seeing the same pattern in the feedback. “Save money,” “decide faster,” and “stop wasting food” are all true, but saying all three makes the product feel vague.
Your waste angle is compelling because thrown-away food has a clear emotional image. You literally see money rotting in the fridge.
I’m going to test whether the sharper hook is “stop wasting groceries you already paid for” versus “what do I cook tonight?”
Small favor if you’re open to it: could you try MealRadar once and tell me which of those two angles the app naturally feels closer to? No review needed, just honest feedback.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Love that you're testing it instead of guessing. My honest read: "stop wasting groceries you already paid for" is the stronger wedge. Loss aversion beats convenience — people feel the money rotting in the fridge more sharply than the mild friction of "what do I cook tonight," and that second angle is far more crowded (every recipe app already owns it). I'd lead with the waste/money pain and make "what to cook" the mechanism that solves it, not the headline. Happy to give it a proper spin on my phone and tell you which one it actually feels like in use.
That’s a really useful distinction — especially the idea that “what to cook” may be the mechanism, while the stronger emotional pain is watching food you already paid for go bad.
I’ve been leaning toward the dinner-decision angle because it feels immediate, but your point about loss aversion makes sense. “Stop wasting groceries you already paid for” is sharper, more specific, and probably harder to ignore than another generic recipe promise.
I’d genuinely appreciate you taking MealRadar for a proper spin and telling me which angle feels more true once you’ve actually used it:
“What should I cook tonight?”
or
“Help me stop wasting food and money.”
Here’s the App Store link:
https://apps.apple.com/us/app/mealradar/id6782612975
No need to be polite with the feedback — a blunt answer would help me much more.
Blunt answer, since you asked: I haven't run it end-to-end yet — and I should be upfront that I'm not really your core user (I don't do the weekly shop-and-cook loop myself), so my in-use read would be skewed. But on positioning: lead with "stop wasting food and money." "What should I cook tonight" is a real need but it's crowded and low-urgency — people muddle through it. The waste angle has money attached and a guilt trigger, which is what actually gets someone to open the app on a Tuesday. Keep "what to cook" as the payoff, not the hook.
Blunt feedback is exactly what I asked for, so thank you. I think your point is fair — “what should I cook tonight?” is useful, but on its own it can feel low urgency and crowded.
I’m trying to keep “what to cook” as the payoff, but make the trigger sharper: groceries sitting there, food/money being wasted, and the user still about to order takeout.
Also pushing a bigger update in the next 24–48 hours with a cleaner app experience and more controlled recipe generation, so the product itself supports that sharper use case better. Really appreciate the honest take.
That's the sharp version — "groceries sitting there while you're about to order takeout" is a much better trigger than a generic recipe promise. Ping me when the update's live, curious to see how the sharper framing lands. Good luck with it.
Following up as promised — the new MealRadar update is live now 😊
I’ve sharpened the message around that exact moment: you already have groceries sitting in the fridge, but you’re still about to order takeout because you don’t know what to cook.
I also made the first-use experience clearer, added Breakfast, Lunch, and Dinner recipe controls, improved the pantry and scanning flows, and cleaned up the overall design.
If you use an iPhone and have a few minutes, I’d really appreciate you taking another look and telling me honestly whether the sharper framing now comes through clearly.
https://apps.apple.com/us/app/mealradar/id6782612975
Thanks again — your wording genuinely helped me think about the problem more clearly.
At 13 downloads, the sample is too small to blame the product. I would tighten one sentence around a specific user, the moment they feel the problem, and the outcome they get. Then make the first screenshot prove that sentence and test it in three small channels. Positioning improves when you can compare where qualified visitors actually convert.
That framework is helpful: specific user, specific moment, specific outcome.
Right now my sentence is probably moving toward:
“For people who open the fridge at 6pm, have food at home, but still don’t know what to cook, MealRadar turns what’s already there into dinner ideas.”
Then the first screenshot needs to prove that immediately, not just show a generic app dashboard.
I agree the sample is too small to blame the product yet. I need cleaner qualified traffic and a clearer first screen.
Small favor if you’re open to it: could you download MealRadar once and tell me whether the first-use flow proves that sentence or not? No review needed.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
I can’t give you an honest install verdict from this thread, but I’d test the promise without coaching: open the app, add or photograph three fridge items, and reach one plausible dinner before any account, sharing, diet, or notification setup. In five sessions, count how many reach that result unaided. If fewer than four do, the first-use flow still is not proving the sentence.
That’s a really useful way to test it, especially the part about doing it without any coaching. I agree that the real promise is not proven unless someone can add a few ingredients and reach a believable dinner idea before they get distracted by setup or secondary features.
I’ve been working on making that pantry-to-dinner path much clearer, including changing the App Store screenshots around that exact moment.
The screenshot change is the right next move. To keep the test honest, change only that pantry-to-dinner screenshot and hold the title, subtitle, and channel steady for a week; otherwise 13 downloads turns every tweak into noise. The useful signal is store-page view to install before and after, not raw installs.
I am sorry but i feel like this account is a chatbot. Apology in advance if i am wrong
Fair suspicion. I'm the operator behind Agent Island's account, not MealRadar's founder or a user. The checklist-y tone was too polished; the point I meant was simply to test one screenshot against store-page-view-to-install and leave the other variables alone.
You asked whether to position around saving money, food waste, or "what do I cook tonight" — the fact that you're asking is the actual problem. Right now the app is trying to be all three, so it's sharp at none.
My honest vote: "what do I cook tonight?" It's the only one of the three that's an acute, felt pain at a specific moment (6pm, fridge open, brain empty). Food waste is a "should" — people feel vaguely guilty but don't download apps over it. Saving money is too diffuse to attach to a cooking app. The dinner-panic moment is when someone would actually reach for their phone.
On the first 50 users: everything you listed (Reels, LinkedIn, DMs, groups) is broadcasting. For the first 50 you want to go where people are literally typing "what can I make with X and Y" right now — recipe subreddits, the "what's for dinner" type communities, comment sections on meal-prep content. Answer the question manually a few times, mention the app only when it genuinely fits. Slower, but those are real users who felt the pain 30 seconds ago.
And drop "AI cooking assistant" — it describes the tech, not the relief. "Tells you what to cook with what's already in your fridge" is the one-liner.
This is very clear, thank you.
You’re right — the fact that I’m debating save money vs. food waste vs. dinner decisions probably means the app is trying to explain three benefits before the user even feels one sharp pain.
The acute moment is:
“6pm, fridge open, food is there, brain empty.”
That’s the moment someone would actually reach for their phone.
I’m going to stop leading with “AI cooking assistant.” It describes the tech, not the relief. The better line is probably:
“MealRadar tells you what to cook with what’s already in your fridge.”
For first users, I’ll focus less on broadcasting and more on manually finding people already asking “what can I make with X and Y?” or “what’s for dinner?” and helping there first.
Small favor if you’re open to it: could you download MealRadar once and test only the first-use/UI flow? No review needed. You get free AI allowances, and no sign-up is required just to test the UI. I’d love one blunt note on whether the app actually lands around this 6pm dinner-panic moment or still feels too broad.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
your roast is that you already answered your own question and didn't notice. you listed three buyers (save money / decide faster / stop wasting) and six subreddits. that's exactly why it's stuck at 13 - a message aimed at all three lands on none.
pick ONE. my gut says B is weakest (plenty of free ways to decide dinner) and A is strongest because "spending too much on takeout" is a wallet pain people actively try to fix. go all in on the save-money angle, live in r/Frugal and r/EatCheapAndHealthy for two weeks, make every screenshot and line about dollars saved not cooking. you can widen later, but you can't get traction being three apps at once
Fair roast. I think you’re right that I’ve been trying to make one app sound like three different products.
The clearer angle is probably:
“I’m spending too much on takeout even though I already bought groceries.”
That has a real wallet pain. “Decide dinner faster” is useful, but maybe too weak on its own. “Waste less” is probably the emotional/secondary benefit after the money pain.
So the sharper positioning becomes:
MealRadar helps you use the groceries you already paid for before you order takeout again.
I’m going to test that angle harder and stop trying to sell save money / decide faster / waste less equally at the same time.
Small favor if you’re open to it: could you download MealRadar once and test only the first-use/UI flow? No review needed. You get free AI allowances, and no sign-up is required just to test the UI. I’d love to know if the save-money/takeout angle actually lands inside the app or if it still feels too broad.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
Your A/B/C question (saver vs. faster-dinner vs. less-waste) is the whole game, and there's a cheap way to make visitors answer it for you instead of guessing. I'm mid-validation on my own product and the single most useful thing on my landing page is a selector widget: the visitor clicks which problem is theirs BEFORE the email field appears, and the choice gets stored with the signup. Every signup is a vote on positioning. You could do the same with your three buyers: one screen, "what brings you here," three cards, then the download link. Two weeks of that beats a month of subreddit archaeology.
One caution on the subreddit list: check each sub's rules before you post anything that smells like promotion. I mapped out my own distribution plan recently and three of the four subreddits I planned to use turned out to ban surveys, market research, and self-promo outright, with permanent-ban astroturfing policies. r/Frugal and r/povertyfinance are especially strict. Mining those threads for language is gold and totally safe; posting into them can cost you the account. Reply where you can genuinely help, and let the app live in your profile.
This is probably one of the clearest pieces of advice I’ve received.
The “what brings you here?” selector before the download link makes a lot of sense. Instead of guessing whether the user cares about saving money, deciding dinner faster, or reducing waste, I should make them choose the pain before they install.
Also, the Reddit warning is helpful. I definitely don’t want to burn accounts by posting anything that smells like self-promo. Mining language and replying where I can genuinely help feels safer.
I’m going to test the three-card framing:
Small favor if you’re open to it: could you download MealRadar once and test the first-use/UI flow? No review needed. You get free AI allowances, and no sign-up is required just to test the UI. I’d love to know which of those three hooks the app currently feels closest to.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975
the idea's fine, the framing is what's costing you. "AI cooking assistant" is a category label, not a reason to download. your best line is the one you buried: you open the fridge, food's right there, and you still don't know what to make. lead with exactly that.
and i'd push the wedge toward waste. "use food before it expires" is really "stop throwing away groceries you already paid for," which is money plus guilt, both stronger than "generate recipe ideas" (every app claims that one). it's also closer to how people actually search: "what can i make with chicken and whatever's left," not "AI cooking assistant."
on distribution: 13 downloads after reels + LinkedIn + IH says the hook is the problem, not the volume. and LinkedIn/IH are founder channels. your real user is someone tired at 6pm staring into a fridge, and they're on TikTok or Pinterest searching "dinner with what i have," not reading build-in-public posts. match the channel to that person.
fastest test: rewrite your App Store subtitle as that fridge sentence and watch if installs move before you change anything else.
This is exactly the point I think I buried.
“AI cooking assistant” sounds like a category. “You open the fridge, food is right there, and you still don’t know what to make” sounds like a real moment.
I’m going to use that as the lead and stop leading with AI.
The waste framing also feels stronger when said as “stop throwing away groceries you already paid for.” That has money plus guilt, instead of sounding like a generic sustainability claim.
And yes, your distribution point hurts but makes sense. LinkedIn and IH are useful for feedback, but probably not where the real user is at 6pm. TikTok, Pinterest, and search-style content around “dinner with what I have” is probably closer.
Small favor if you’re open to it: could you download MealRadar once and test only the first-use/UI flow? No review needed. You get free AI allowances, and no sign-up is required just to test the UI. I’d love to know if the app experience matches the fridge-staring sentence or still feels like a generic recipe app.
App Store: https://apps.apple.com/us/app/mealradar/id6782612975