深度竞品分析 · 9 家头部对手 · 67 条引用
The cooking-app market is bifurcated. Western apps either organize recipes (ReciMe[1], Paprika[2], Kitchen Stories[1]) or plan meals (Mealime[1], Samsung Food[1]); only SuperCook seriously addresses "cook with what you have," and it has no AI assistant, no nutrition layer, and no household model[2]. Chinese apps (下厨房[1], 香哈[1]) dominate UGC recipes but treat the fridge as out-of-scope. Yummly, the closest historical analogue to Pick & Cook, was shut down by Whirlpool on 2024-12-20[1], leaving ~20M cooks orphaned[7]. The pantry-first × AI × anti-waste quadrant is open.
Pick & Cook is the only product whose KPI is "did you actually use up your food?" SuperCook has the search, but no nutrition / no AI / no household[2]. Make our use-up score the headline metric on home, in onboarding, and in App Store screenshots — and quantify it ("Cooks who use Pick & Cook waste 31% less food, $X/month saved"). This is a defensible position that no rival can copy quickly without rebuilding their data model.
Yummly's shutdown left users without a bulk-export option (top complaint on Reddit / Plan to Eat[7][8]). Ship a one-click "Import from Yummly screenshot" using our existing Photo→Recipe OCR, and run a 30-day "Yummly Refugee" campaign. The infrastructure is already built — only the campaign and a 1-screen migration funnel are net-new.
下厨房 has 11.99M MAU[4] but no pantry, no anti-waste, and a recurring UGC-quality complaint ("做出来不好吃"[4]). Pick & Cook's 22-cuisine catalog (incl. Chinese) + bilingual mission + Apple HealthKit + Photo OCR is uniquely positioned for diaspora households (US/CA/AU/UK Chinese families) and second-tier Chinese cities where 下厨房's e-commerce push has eroded trust[4]. This is a low-cost beachhead — no new product work, just a localised landing page and ASO in zh-Hans / zh-Hant.
We profiled 8 active competitors (4 US/Western, 2 EU, 2 China) plus the recently shut-down Yummly as a cautionary tail. Together these cover 99% of the household-cooking-app conversation in 2025.
April Dunford's Obviously Awesome frame in five fields: For [user] who [problem], unlike [alternatives], we are [the only thing that does X], because [proof]. Reading these in sequence reveals where each player has actually planted a flag — and where Pick & Cook can plant its own without overlap.
For busy households who open the fridge and don't know what to cook, unlike recipe organizers (ReciMe, Paprika) or generic meal planners (Mealime, Samsung Food), Pick & Cook is the only AI-powered, pantry-first cooking app that turns "what's already in your fridge" into "dinner tonight" while quantifying the waste it just helped you avoid, because we combine a 1,889-ingredient pantry catalog[1], dual-scoring rule + Nomi AI engine, Photo→Recipe OCR, Apple HealthKit, and a use-up score that no rival ships[2].
面向 每天打开冰箱不知道做什么菜的家庭用户,不同于 菜谱整理工具(ReciMe、Paprika) 和 泛用型周餐计划工具(Mealime、Samsung Food),Pick & Cook 是唯一一款"以冰箱库存为起点"的 AI 烹饪 App — 把"冰箱里有的食材"直接转化成"今晚就能上桌的菜",并量化为你避免的食物浪费,因为我们结合了 1,889 种食材的库存目录[1]、规则引擎 + Nomi AI 双重评分、菜谱拍照 OCR、Apple HealthKit 集成,以及一个市面上独此一份的"用尽分数"[2]。
Two axes that matter for our category: X = how seriously the product treats "use what you have / reduce waste" as a primary job-to-be-done. Y = depth of AI / intelligence beyond keyword search. The upper-right quadrant — AI × Use-up — is empty. Chart rendered with matplotlib from the per-competitor scores in .local/research/_combined.json.
✓ ships natively · 部分 partial/paywalled · ✗ not offered · ●●●●○ after row label = how often buyers mention this capability unprompted in our 67-source corpus (5=every review thread, 1=niche) · [N] → per-competitor source list on the final page.
| Capability | Pick & Cook | ReciMe | Paprika 3 | Samsung Food | Mealime | SuperCook | Kitchen Stories | 下厨房 | 香哈菜谱 |
|---|---|---|---|---|---|---|---|---|---|
| Pantry Management ●●●●● | ✓ 1,889-ingredient catalog, freshness tracking, post-cook auto-deduction | ✗ ReciMe focuses on recipe capture, not pantry inventory tracking [1] | ✓ Pantry section tracks quantities, purchase dates, and expiration dates; pantry items auto-removed from grocery list [1] | ✓ 'Food List' with Vision AI photo capture (Pro) and Family Hub fridge sync | ✗ explicitly does not track pantry or fridge inventory | ✓ virtual pantry with 2,000+ ingredients in categories, voice input supported [1] | ✗ no pantry inventory; closest is paid 'Ingredient Search' that suggests recipes from ingredients you type in [3] | ✗ there is no native fridge/pantry inventory; the only pantry-adjacent flow is the '菜篮子' (basket) which is a recipe-ingredient → shopping list bundling feature, not stock tracking [7] | ✗ no fridge/pantry inventory; product copy mentions only ingredient lists per recipe [12] |
| Recipe Import (URL/Photo/Social) ●●●●● | ✓ Photo→Recipe Draft via GPT-4.1-mini Vision OCR + URL/manual | ✓ flagship feature: URL, Instagram/TikTok/YouTube/Facebook/Pinterest share, photo/image OCR, paste text, import from Paprika/Notes/Notion/Evernote [1] | 部分 auto-downloads from hundreds of websites and a browser bookmarklet; manual entry; no native TikTok/Instagram or photo OCR import [1][3] | ✓ save any recipe from any website via web clipper/extension and mobile share sheet | ✗ closed catalog of curated Mealime recipes; no web-clipper or user-imported recipes | ✗ recipes are aggregated from 18k partner sites; users cannot import their own URLs/photos [1][2] | 部分 Plus tier lets you save recipes from any URL on the web into in-app Cookbooks; no photo/OCR import documented [3] | ✗ community is closed UGC; users author recipes inside the app; no URL/photo/screenshot import of external recipes is exposed | ✗ UGC authoring inside app only; no external URL/photo OCR import surfaced |
| Barcode Scanning ●●○○○ | ✓ FDC + Open Food Facts dual-source lookup | ✗ not part of the product [1] | ✗ not advertised as a feature [1] | 部分 Vision AI photo recognition is the primary capture path; barcode scanning not prominently advertised | ✗ not part of product | 部分 iOS app added an 'AI Food Scanner' that photographs fridge/pantry to identify ingredients; no UPC barcode flow documented [2] | ✗ not a documented feature [1][3] | ✗ no barcode/UPC scanner for groceries reported in product reviews | ✗ not a documented feature |
| Smart Shopping List ●●●●● | ✓ auto-merge + Best Next Buy / Smart Restock / Pantry Gap Fill engines | ✓ auto-aisle smart grocery list, but no merge/customization [1][3] | ✓ smart auto-consolidating grocery list (e.g. 2 eggs + 3 eggs = 5 eggs), custom aisles, multiple lists [1] | ✓ one-click conversion of any recipe or meal plan into a smart, shareable list with grocery delivery from 23 retailers | ✓ auto-generated, store-categorized list with delivery via Instacart, Amazon Fresh, Kroger, Walmart, Thrifty Foods | ✓ missing ingredients from any recipe can be added to an in-app shopping list [1] | 部分 historically core feature; was removed during a major update and reintroduced; users still complain about reliability [1][2] | ✓ '菜篮子' one-click adds all ingredients of a recipe to a shopping basket [7] | ✓ 一键添加 ingredients to a 购物清单 from any recipe [12] |
| Meal Planning Calendar ●●●●○ | 部分 Cook Mode + recommendations, no full calendar yet | ✓ weekly drag-and-drop calendar (breakfast/lunch/dinner), one week view only [1][3] | ✓ calendar with breakfast/lunch/dinner/snacks/custom types, day/week/month views, reusable menus [1][3] | ✓ drag-and-drop weekly planner; Pro adds AI-personalized weekly plans tied to health goals | ✓ core product; personalized weekly plan in minutes (note: more recipe-picker than calendar planner) | 部分 has a 'menu' section to organize dishes for the week, but no calendar/schedule view [5] | ✗ not a documented core feature [1] | 部分 节气/时令 ('seasonal/solar-term') recommendations and curated daily 榜单 (rankings) but no calendar-based weekly meal plan [7] | 部分 三餐营养推荐 (breakfast/lunch/dinner curated by certified nutritionists) but no editable weekly planner [12] |
✓ ships natively · 部分 partial/paywalled · ✗ not offered · ●●●●○ after row label = how often buyers mention this capability unprompted in our 67-source corpus (5=every review thread, 1=niche) · [N] → per-competitor source list on the final page.
| Capability | Pick & Cook | ReciMe | Paprika 3 | Samsung Food | Mealime | SuperCook | Kitchen Stories | 下厨房 | 香哈菜谱 |
|---|---|---|---|---|---|---|---|---|---|
| Nutrition Tracking ●●●○○ | ✓ per-recipe + Apple HealthKit integration | 部分 auto calc of calories/protein/carbs/fats per recipe (premium); no daily intake log [1] | ✗ does not auto-calculate nutrition; user must enter manually in notes [3] | ✓ health scores and nutrition info on 218,500+ recipes; Pro ties planning to personal health profile and goals | 部分 full macros/micros and calorie filters are Pro-only; basic nutrition shown for free recipes | ✗ not a documented feature [1][2] | 部分 recipes display basic nutrition info per serving but no daily tracking [1] | 部分 has 减脂餐 and health-menu customization content, but no per-day calorie/macro tracker [7] | 部分 health/养生 categorization, calorie info per recipe, but no day-level intake tracker [12] |
| AI Recommendations ●●●●○ | ✓ Nomi AI (OpenAI) + dual-scoring rule engine + craving prediction | ✗ ReciMe is an organizer, not a discovery/recommendation engine [1] | ✗ no AI/discovery engine; user-driven library [1] | ✓ Food AI personalization, dietary substitutions, ingredient swaps for nutrition | 部分 rule-based personalization across 200+ preferences and 119 dislikable ingredients; not generative AI | ✓ AI ingredient-matching plus iOS photo-based ingredient recognition [2] | 部分 Plus tier 'For You' feed personalizes via questionnaire; not a real-time AI chatbot [3] | 部分 personalized feed on home (推荐/关注 tabs) and category 榜单, plus seasonal recs; no LLM/AI generation surfaced as marketed feature [7] | 部分 '智能推荐' personalized recs based on taste preferences and browsing history [12] |
| Waste Reduction Focus ●●●○○ | ✓ core differentiator: use-up score, expiry tracking, mission-level KPI | ✗ does not explicitly target food waste; no 'use-it-up' workflow [1] | 部分 pantry expiration-date tracking can flag aging items, but no explicit anti-waste workflow [1] | ✓ Pro plans prioritize ingredients nearing use-by date and auto-replenish shopping list | ✓ plans engineered to cross-use ingredients and minimize leftover spoilage | ✓ explicitly markets 'use what you have, save hundreds on grocery bills, no more wasted leftovers' [1] | 部分 Plus 'Ingredient Search' is marketed as helping reduce food waste by cooking with what's on hand, but it is not a primary product pillar [3] | ✗ food-waste reduction is not an explicit product theme (no use-it-up / expiry features documented) | ✗ food-waste reduction is not a stated theme; only 食材相克 (food incompatibilities) content [12] |
| Community Recipes (UGC) ●●○○○ | ✓ BYOR + Teach Wizard moderation pipeline | ✗ no built-in feed of new dishes; users only see recipes they import [1] | ✗ no community feed; recipes shared only via email between Paprika users [1] | ✓ 192,000 community notes, 5,400+ public food communities with 4.5M members (incl. Jamie Oliver) | ✗ curated in-house recipe catalog only; no community/UGC recipes | ✗ aggregates from publisher sites, no UGC or social layer [1] | 部分 community recipes exist and can be browsed/commented on, but uploading new community recipes was moved to web-only [1][2] | ✓ core differentiator; 300万+ recipes with reviews, 作品 (cooking-result photos) and follow graph [5] | ✓ UGC community + cumulative '8亿人次' served (2015 self-report) [16] |
| Chinese Localization ●●○○○ | ✓ bilingual mission, EN+ZH legal docs, 22-cuisine catalog incl. Chinese | ✗ no evidence of Simplified/Traditional Chinese localization on App Store/Play listing [2][6] | ✗ App Store listings do not advertise Chinese localization; UI primarily English [4] | 部分 supports 26 languages including Chinese in product/ingredient recognition; full Mainland China app store presence not confirmed | ✗ English-only; no Chinese localization or Mainland China presence | 部分 supports 20 languages including Chinese on the aggregator side, but no PRC-market localization [1] | ✓ China is one of Kitchen Stories' core markets; app has historically shipped a Chinese-language version [1] | ✓ Simplified Chinese first; an overseas '下厨房海外版' iOS app exists for diaspora users [5] | ✓ Simplified Chinese only, China-mainland focus |
Kano sorts features into Must-Be (absent = uninstall), Performance (more = better satisfaction, linear), and Delight (unexpected joy, asymmetric upside). Mapping the 9 competitors' user complaints reveals which buckets are saturated and which still pay off.
The whitespace argument is only credible if grounded in actual user pain. Below: the two most-frequent 1–2★ complaint themes per competitor, drawn from App Store / Google Play / Reddit / Sitejabber / MIIT regulatory notices. Right side: trap questions a P&C salesperson can ask a prospect already on a rival app, designed to surface exactly these gaps.
| ReciMe |
|
|---|---|
| Paprika 3 |
|
| Samsung Food |
|
| Mealime |
|
| SuperCook |
|
| Yummly† |
|
| Kitchen Stories |
|
| 下厨房 |
|
| 香哈菜谱 |
|
/yummly-refugees with side-by-side feature comparison, GDPR export pledge, and a 60-day premium trial. ASO: bid on "Yummly alternative", "Yummly replacement" keywords on App Store Search Ads.Citation conventions. Inline [N] markers throughout the deck refer to the numbered source list under the corresponding competitor section below. So [2] in a sentence about Paprika points to entry [2] under "Paprika 3" here, not a global counter.
Methodology. Five parallel research streams across product copy, App Store / Google Play listings, third-party reviews, regulatory notices (MIIT 工信部), and industry data (Jiguang 极光, 易观). All claims are tied to numbered citations. Tiers: 1 = primary / regulatory / official, 2 = major media / Crunchbase / NEEQ filings, 3 = blogs / company copy. Cross-checked across ≥2 sources where possible. Where data could not be verified we wrote "unknown — low confidence" rather than fabricate.
Citation count: 67 sources across 9 competitors, gathered in May 2026.
Every cooking app captures one step of the household food cycle. Pick & Cook is designed to close the full 9-step loop from "user opens app" to "purchase confirmed → pantry updated", then back into the next recipe decision. Each rotation makes the next recommendation smarter and the next purchase more useful — and produces a measurable cash-flow signal (declared intent, then confirmed buy) that we can validate before taking on any delivery integration risk.
The smallest possible product change that proves users buy ingredients because of Pick & Cook — without any delivery API. The user opens a recipe, adds missing items to a shopping list, switches to Store Mode while physically in the store, taps Done Shopping, then confirms what they bought to update the pantry. Four screens, one closed loop, zero integrations.
The 4-screen MVP only matters if every step emits an event. Below: the 9 analytics events that instrument the §11 loop, then the 5 transition benchmarks that define early success — the thresholds below which we treat the no-delivery purchase-intent hypothesis as falsified.
| # | Event | What it proves | Why we need it |
|---|---|---|---|
| 1 | recipe_viewed | Opens a recipe detail page from any surface | Anchors transition T1 — denominator for "Recipe View → Add Missing". |
| 2 | missing_items_card_shown | Recipe Detail surfaces ≥1 missing ingredient | Gating event — without it, no buy intent is possible. |
| 3 | missing_items_added_to_shopping | User taps "Add N missing to shopping" CTA | Numerator for T1 — first declared purchase intent. |
| 4 | shopping_list_opened | User opens the Smart Shopping List screen | Denominator for T2; proves the list is consulted, not abandoned. |
| 5 | store_mode_entered | User taps "Start shopping at store" — Store Mode active | Numerator for T2 — high-fidelity "I am in the store right now" signal. |
| 6 | shopping_item_checked | User checks an item off in Store Mode (per-item) | Per-item granularity behind T3; lets us see partial-trip conversion. |
| 7 | shopping_done | User taps "Done shopping" inside Store Mode | Numerator for T3 — the trip closed under our roof. |
| 8 | purchase_confirmed | User confirms ≥1 bought item on the Confirmation screen | Numerator for T4 — the moment we measure realised purchase. |
| 9 | pantry_updated_from_shopping | Confirmed items auto-merge into pantry; loop closes | Mechanical close-out + the input to the next week's recommendations. |
| ID | Transition | Events | Benchmark | Why this floor |
|---|---|---|---|---|
| T1 | Recipe View → Add Missing Items | #1 → #3 | ≥ 10% | Of users who view a recipe, 1-in-10 should add at least one missing ingredient. Below this, Missing Items Card design or pantry seeding has failed. |
| T2 | Shopping List → Store Mode | #4 → #5 | ≥ 20% | A fifth of shopping-list opens should escalate into a real store trip. Lower = list is a wishlist, not an action plan. |
| T3 | Store Mode → Done Shopping | #5 → #7 | ≥ 30% | Of trips that start in Store Mode, ~1-in-3 should complete with Done Shopping. Lower = friction in-store (battery, screen-off, lost signal). |
| T4 | Done Shopping → Add to Pantry | #7 → #8/#9 | ≥ 70% | Of completed trips, the strong majority should confirm purchases. Below 70% means the Confirmation UX (Screen 4) is the bottleneck, not user intent. |
| T5 | Repeat weekly use | #1 (W2) / #1 (W1) | ≥ 15% | Of users who completed the loop in week 1, 15%+ should repeat in week 2. Floor for retained pantry-intelligence value. |
If the §13 funnel clears its kill criteria, four monetisation paths become available. They are ranked by capex required (lowest first) and all assume the loop has been validated — none should ship before §16's 30-day plan returns a green light.
A validation phase is defined as much by what it refuses as what it ships. Each "no" below is paired with the trigger that would re-open it. None of these are forever; all are deferred until the §11 loop produces evidence.
Four weeks. One falsifiable hypothesis: households will declare grocery intent and confirm purchases inside Pick & Cook at rates high enough to support §14's monetisation paths. Each week has one deliverable, one owner, and one decision gate. We do not ship §14 until week 4 returns a green light.