Ask someone what they're making for dinner and you rarely get a recipe name back. You get "chicken and rice," "pasta with whatever veg we have," or "the salmon thing with broccoli." Households think in building blocks — a protein, a vegetable, a carb, maybe a sauce — long before they think in named dishes. Most meal planning software doesn't work that way.
In 2026, recipe apps are excellent at discovery and guided cooking. Where they often struggle is the boring middle of the week: planning five nights quickly, using what you already bought, and turning that plan into a shop without retyping ingredients. Component-based planning targets exactly that gap.
How recipe-first apps organise your food
Apps like Paprika, Mealime, or the recipe hubs built into appliances like Cookidoo and Samsung Food are, at their core, content libraries. Every dish is a discrete recipe card: a title, a photo, a fixed ingredient list, a method. Search and filtering work by tag — "vegetarian," "under 30 minutes," "high protein" — but the atomic unit is always the whole recipe. If you want to swap the vegetable in a recipe, you're editing a recipe, not remixing a component.
That model is great for content discovery. It's less great for a family that already knows it eats chicken-broccoli-rice on Tuesdays and wants to plan a week quickly, or for spotting that three different dinners this week all use cucumber that's about to go off.
Recipe-first apps also tend to assume you'll live inside their library. Your Cookidoo collection, your Samsung Food saves, your YouTube favourites — each in its own silo. Planning across them means mental juggling, not one weekly view.
Thinking in components instead
A component-based approach flips the atomic unit. Instead of "Recipe #4821," the building blocks are components — protein, vegetable, carbohydrate, sauce, and so on — and a meal is just a useful combination of them, with an optional link out to wherever the actual recipe lives. This has a few concrete effects:
- Filtering gets faster. You can filter your whole meal library by "uses chicken" or "uses broccoli" without reading a single recipe description.
- Ranking gets simpler. A free, deterministic ranking engine can score meals by how many of your selected components they cover — no AI required, no content curation needed.
- Receipt matching becomes possible. If a component is linked to an item you actually buy, the planner can notice "you bought cucumbers this week" and surface cucumber-based meals automatically — something a pure recipe database has no way to do, because it doesn't know what's in your fridge.
- Near-duplicates stop being a problem. "Cucumber" and "Cucumbers," "Chicken" and "Chicken breast" — components can be grouped for filtering without forcing you to clean up your data first.
Components match how people answer "what's for dinner?" — and how grocery receipts list what you actually purchased.
A concrete example: one week, two approaches
Recipe-first week: Search "quick chicken dinner." Save three different recipes with overlapping ingredients written three different ways. Manually merge shopping list lines. Hope you use the broccoli before it turns.
Component-first week: Filter library by chicken + broccoli. Drag "chicken stir-fry" and "tray bake" onto Mon/Wed — same protein, different sauces. Planner notes cucumber in recent purchases; surfaces a salad meal for Thursday. Shop the Week merges garlic once. List sorts by aisle.
Same household, less friction.
Component-based planning in practice
Onboarding from receipts
The fastest way to seed components isn't typing — it's planning from what you already buy. Top grocery items become proposed components; you confirm in a few taps. Your library starts grounded in reality.
Meals as combinations + links
A meal might be: salmon + asparagus + new potatoes, with a link to the YouTube video you actually follow. The planner stores the combination and the schedule; the recipe stays at the source. You can bulk-import from Cookidoo, Samsung Food, or YouTube without copying full methods into yet another app.
Ranking without AI
Coverage scoring — how many of your selected or recently purchased components does this meal use? — handles most suggestion needs deterministically. AI meal planning fills gaps (draft a quick meal from eggs + spinach) but doesn't need to run every time you plan Tuesday.
Shopping lists from components
Ingredients attached to meals roll into Shop the Week. Receipt-aware price estimates attach to list lines when components map to items you've bought before.
When recipe-first still wins
Component-based planning isn't a replacement for beautiful recipe apps — it's a different layer:
- Trying a new cuisine — browse, photos, reviews matter; recipe libraries shine.
- Appliance-guided cooking — Cookidoo on Thermomix, Samsung Food on a connected oven — the method lives in the appliance app.
- Baking and precision — ratios and steps matter; a component card saying "cake" isn't enough.
The split that works for many households: discover and cook in recipe apps; plan the week and shop in a component-first planner.
Comparison at a glance
| Question | Recipe-first app | Component-based planner |
|---|---|---|
| What's the atomic unit? | Recipe card | Component combination |
| Best for… | Discovery, guided steps | Weekly board, rotation |
| Filter by ingredient? | Tags / search text | Native component filters |
| Knows what you bought? | Rarely | Via receipt-linked components |
| Where recipes live | Inside the app | Often linked out |
| Shopping list merge | Per-recipe export | Shop the Week across plan |
See also meal planning apps vs. recipe box apps for the planning-layer framing.
Common mistakes
Treating components as a full recipe replacement. Keep the link to the real method. Components answer "what" and "when"; the source answers "how."
Over-splitting components. You don't need seventeen types of onion. Group for planning; detail lives in the recipe.
Ignoring receipt links. Components without purchase data still help filter; components with receipt data unlock waste reduction ranking ("use the cucumber you bought").
Choosing an app that makes you re-enter ingredients for every meal. Import and extraction should populate components once; planning should reuse them.
FAQ
Can I use components if I mostly cook from Cookidoo?
Yes — import meals as links plus structured ingredients. Plan the week in the component planner; tap through to Cookidoo when it's time to cook.
Do I lose nutrition and cost estimates?
Not if ingredients are attached to meals. Week-level nutrition and cost views work from the same structured data — components are the index, ingredients are the quantities.
Is component planning only for simple dinners?
It's especially strong for repeat weeknight cooking. Complex one-off dinner parties can stay as full recipes in your library — you don't have to componentise everything.
What's free in SpendScan?
The shopping list — aisle sort, regular buys, receipt check-off, estimates — is free forever. Component-based meal planner, library, ranking from purchases, Shop the Week, and AI are Pro with a 7-day free trial.
You don't lose the recipes — you keep them elsewhere
Component-based planning doesn't mean giving up on recipes. Meals can link out to wherever the actual recipe lives — Cookidoo, Samsung Food, YouTube, a blog — while the planner itself stays focused on when and what fits the week. That's a deliberate design choice: a planning layer instead of another recipe box competing with the ones you already trust. See more on that trade-off in why a planning layer beats another recipe app.
Try it
SpendScan's meal planner is built component-first: onboarding seeds your components from your grocery receipts, and the free ranking engine and drag-and-drop week board both work from the same building blocks. The shopping list that comes out the other end stays free regardless of which plan you're on. Pro features — full library, AI generation, bulk import — include a 7-day free trial; the list does not.