Abstract
ReciMe lets people pull recipes straight out of Instagram, TikTok and Pinterest into one organized, meal-planned, shoppable place — a genuinely sticky idea with 2.6M+ installs. But its own reviewers describe the two things the app is actually for — importing a recipe correctly and then being able to open it again — failing constantly, alongside a paywall that stays hidden until after a forced review and a long setup questionnaire. The idea has real pull; the execution around reliability and pricing transparency is what's pushing people back to screenshots and notes apps.
Background
ReciMe (ReciMe: Recipes & Meal Planner) imports recipes from social media and other apps, builds grocery lists and weekly meal plans, and calculates nutrition — free to download, with a subscription required for unlimited imports, nutrition calculation, and unlimited social-media imports.
What it does
Pulls a recipe's ingredients and steps out of an Instagram/TikTok/Pinterest post or screenshot, then organizes it into cookbooks, meal plans, and grocery lists.
What broke
Reviewers describe a wave of "Oh no, something went wrong" errors that block opening or editing saved recipes — some tie it to a specific recent version — plus imports that regularly drop or garble ingredients and instructions, and Instagram's own share-sheet integration disappearing entirely for one paying reviewer.
Why it is soft
The free tier caps out at 5 imports a week and the subscription price isn't shown until after a forced review prompt and a multi-question setup flow — several reviewers call this deceptive regardless of whether it's disclosed deep in the store listing's terms.
Strengths
When it works, reviewers are genuinely enthusiastic — not just tolerant. Several describe switching phones just to keep their ReciMe recipe collection, and the core promise (stop screenshotting recipes into a gallery graveyard) clearly resonates as a daily habit, not a one-time download.
So impressed with the ease of using this app. I now don't have to screenshot my TikTok and other apps recipes as well as having the ability to save them in one place in individual cookbook titles that you create. Best money I've spent on a app.😃
Market gap
Import reliability
The most repeated complaint: recipes that show as saved but throw "something went wrong" when opened, imports missing ingredients or instructions entirely, and edits that spin forever without saving.
Hidden paywall
A long questionnaire and a forced review prompt happen before the price is shown at all, and the free tier's 5-imports-a-week cap is reached fast — several reviewers call the sequencing itself deceptive.
Billing trust
A recurring cluster reports being charged without a clear opt-in moment, charges continuing after a decline or cancellation attempt, and no visible in-app way to cancel.
Feature gaps
A saved meal plan can only be deleted and rebuilt, not edited in place, and nutrition figures don't recalculate when serving size changes — both called out repeatedly as busywork the app was supposed to remove.
Instagram importing is completely broken. ReciMe disappeared from Instagram's full share app list. I reported this by email, and my factual bug report was deleted from ReciMe's Facebook group. Second major issue I've had as a paying member within the last month.
Avoid this app. I was charged without my knowledge, and the subscription process is misleading. Google Play showed no active subscription, yet I was still billed. When I tried to cancel, I was given the runaround instead of a clear way to stop the charges. The whole experience felt deceptive and frustrating. I would never recommend an app that makes billing so confusing and canceling so difficult. Use at your own risk.
- Make import reliability the core product bet, not a background feature — an AI-assisted extraction fallback and active monitoring for platform share-sheet changes, so "something went wrong" is rare rather than routine.
- Disclose the price and the free-tier limit before the setup questionnaire and review prompt, not after.
- Let a meal plan be edited in place, and put subscription cancellation fully inside the app rather than routing through email or a third-party billing page.
Build complexity
Assumes one part-time solo developer, no funding, no team. Recipe extraction is the one workstream harder than a typical clone — it needs an AI-assisted fallback, not just HTML scraping, since captions and screenshots aren't structured data. This is an estimate, not a guarantee.
| Workstream | Weeks |
|---|---|
| Recipe import: web/caption scraping + AI extraction fallback | 3 |
| Grocery list + editable meal plan | 2 |
| Nutrition calculation (recalculates on serving change) | 1 |
| Accounts, subscription, in-app cancel, honest paywall | 1.5 |
| Polish, QA, store submission | 0.5 |
| Total | 8 |
Expected revenue
Assumes a single paid tier priced in the range reviewers themselves cite (roughly $40/year), with a genuinely usable free tier and organic/ASO-only acquisition rather than paid ads. This is an estimate, not a promise.
| Installs | Activated | Retained (D30) | Paid | MRR |
|---|---|---|---|---|
| 40,000 | 20,000 | 3,000 | 600 | $3,300 |
Biggest challenges
Recipe import isn't a one-time build — it's an ongoing arms race against social platforms changing their share sheets and markup, exactly the failure that took down ReciMe's Instagram integration for a paying reviewer. A solo builder inherits that maintenance burden indefinitely, not just at launch. The other real cost is trust: getting subscription consent and cancellation unambiguous from day one, since billing-trust complaints are exactly what erodes word-of-mouth fastest in a habitual, daily-use app like this.
AI angle
This is a genuine angle, not a bolt-on: recipe extraction from a screenshot or a social caption is squarely an LLM-vision task now, not bespoke regex scraping — using it as the primary extraction path (with the old HTML-scraping approach as a fallback) directly fixes ReciMe's most common complaint, garbled or missing ingredients. The same approach can normalize units across a shopping list ("1/2 onion" four times becoming "2 onions") — a smaller but repeatedly requested fix.
Conclusion
Build it. The underlying idea is proven at 2.6M+ installs and the complaints are almost entirely execution — import reliability and paywall transparency — not a flawed concept. Modern AI extraction closes the hardest technical gap cheaper than ReciMe's own scraping approach, and there's no deep moat protecting the incumbent from a more reliable, more honest competitor.
8 weeks
solo build to v1
~$40/yr, single tier
pricing & model
$3,300/mo
estimated MRR at month 12
2.6M installs, thin moat
the fact that decided it