Search the app store for a meal planner and the results lean on one of two habits: browsing recipes for dinners you had not thought of, or logging what you already ate. Both are useful habits. Neither was built for a week where Tuesday is a heavy session and Thursday is a rest day, which is the week you are actually trying to feed.
Quick answer: five things to look for in a training meal plan app
- Hard, easy and rest day awareness. The app should know your days are not interchangeable, and shape the food accordingly.
- Carbohydrate placed around your sessions. Not just a daily total, but where in the day the food sits relative to training.
- One grocery list for the week. Consolidated across every planned meal, not a list per recipe.
- A prep plan, not just recipes. An order of operations for the session where you actually cook.
- Check-off execution. Deciding once and ticking through it, rather than recording after the fact.
These five criteria are deliberately about planning and executing a training week, not overall product quality. If your main need is discovering recipes or measuring what you eat, browsing or logging is the better habit to lean on. The columns describe ways of working rather than named apps, and several apps implement more than one of them.
Why the category confusion matters
The three ways of working are not competing at the same job, which is why comparing them on recipe count or interface polish tells you very little. They answer three different questions: what could I cook, what did I eat, and what am I eating this week. Individual apps often do more than one of them, and the bigger ones do all three. Only the third one has to know that Tuesday is heavy.
Browsing recipes is built for finding dinners you had not thought of. Logging after the fact is built for finding out what you are actually eating. Planning the week ahead is built for deciding a week of eating around the sessions in it. Across five criteria, browsing recipes does none and part of two, logging after the fact does none and part of two, and planning the week ahead does five of them. Where a column says a tool is not built for something, that is a statement of scope, not a fault.
These columns describe ways of working, not specific apps. A given app may implement more than one of them, and several do, so treat the rows as descriptions of an approach rather than a verdict on any product.
None of that is a criticism of logging as a way of working. It is a statement about scope.
The same goes for browsing recipes. A good one is genuinely useful when the problem is boredom, and boredom is a real problem in a prepped week. It stops being the right instrument when the question changes from what could I make to how much of it, on which day, and bought when.
Logging is an excellent way to find out what you are actually eating, and if you do not know that yet, it is the right place to start. The mismatch appears later, once you already know your numbers and the problem has quietly changed from measurement to execution.
The five criteria, one at a time
On hard, easy and rest day awareness, browsing recipes is not what it is for, logging after the fact is not what it is for, and planning the week ahead does this. On carbohydrate placed around sessions, browsing recipes is not what it is for, logging after the fact does this in part, and planning the week ahead does this. On one consolidated grocery list, browsing recipes does this in part, logging after the fact is not what it is for, and planning the week ahead does this. On a prep plan, browsing recipes does this in part, logging after the fact is not what it is for, and planning the week ahead does this. On check-off execution, browsing recipes is not what it is for, logging after the fact does this in part, and planning the week ahead does this.
1. It knows your days are different
A training week is rarely seven copies of the same day. An app that treats it as one repeating target may fit poorly at both ends: short on the day you needed the most support, and generous on the day you needed the least. Look for something that asks what kind of day each one is before it decides what you eat. For many athletes that single distinction does more than any recipe library, because a generic daily target has no way to express it. That distinction is the same one set out in a weekly plan built around training.
2. It places food around the session, not just across the day
This is the criterion most often missing, and the one most often assumed. An app can be scrupulous about a daily total and still have no idea when you train, which leaves it unable to help with the part of the day that tends to matter most to how a session feels.
Two people can hit an identical daily total and have completely different days, because one ate most of it hours after training and the other did not. Placement matters most when recovery time is short or daily intake is inadequate; with adequate intake and enough time before the next session, comfort and consistency usually matter more than the clock1. An app worth using should at least know when you train.
3. It produces one grocery list, consolidated
A shopping list built recipe by recipe is how you end up buying coriander three times and no rice. A planner that has decided the whole week can add the week up: one list, one shop, quantities that reflect what the plan actually needs.
The test is easy to run in a shop doorway. Open the app, look at the list, and see whether the same ingredient appears once with a sensible quantity or four times in four places. A list that has been consolidated tends to be shorter than you expect, because a week of real cooking reuses the same eight or ten things.
4. It tells you what to cook first
Recipes describe a dish. A prep plan describes an afternoon. Those are different documents, and only one of them survives contact with a Sunday where you also have laundry on.
The gap between a plan and a fed week is usually a Sunday afternoon. Recipes do not help much there; an order does. Oven on, protein in, grain in one pot, cold assembly last. Look for an app that treats preparation as a scheduled step rather than an exercise left to the reader, the way a prep sequence does.
Order matters more than hours here. Most of a prep block is waiting on an oven, and an app that knows that can overlap the jobs instead of listing them end to end. What you want to see is a sequence with a shape: the long job started first, the short jobs slotted into the gaps, and assembly last.
5. It lets you check off rather than record
Logging asks you to remember, weigh and enter something after every meal. Over a six-day training week that tax is often what quietly ends an attempt, and it depends on the person: some people log happily for years, and if you are one of them this criterion may matter less to you than the other four.
Checking off asks nothing except that you eat the thing you already decided on. The decision moved to Sunday, where you had time for it. The practical difference shows up on a Wednesday evening when you are tired: recording is one more job, and ticking is not.
How to actually run the comparison
Take one real week, the one coming up, and try to produce it in whatever you are evaluating. Not a demo week: yours, with the session you dread on the day it actually falls. A short trial usually shows which job the tool is built to do. A browse-led tool will give you seven attractive dinners with no relationship to Tuesday. A log-led one will sit there waiting for you to have eaten something. Neither is malfunctioning; both are doing what they were built to do, which is the point.
Give it a fair run, too. A week is the smallest useful unit here, and something that looks thin on Monday sometimes turns out to be what still has you fed on Friday. Judge it on whether the week held, not on how the first screen looked.
Then look at what you are holding. Do you have a list you could shop from, an order you could cook in, and a day-by-day plan that treats Tuesday and Sunday differently? If any of those three is missing, you have found the gap, and it is usually the same gap: the tool is measuring or suggesting, where you needed something to decide.
None of this removes the thinking altogether. Something still has to know your targets, and something still has to notice when the week changes. What a good one does is move the thinking to a moment when you have time for it, and keep it there.
What this does not tell you
A criteria list is a shape, not a verdict. Plenty of athletes are well served by logging plus their own spreadsheet, and something that answers all five may still be wrong for you if the food it suggests is food you will not eat. Treat the five as questions to ask, not a scorecard to total up.
Two things the list deliberately leaves out are price and recipe count, because neither alone tells you whether the plan will work for your week. A tool with forty recipes you will actually cook beats one with four thousand you will not, and the cheapest option is the one you abandon in March.
Where Mero fits
Everything above describes a category rather than a product, and the honest reason for writing it is that the category barely exists yet. Browsing and logging each answer a real question well, and a calendar bolted onto either one does not turn it into a plan for a training week.
Mero matches carbohydrate placement to hard, easy, and rest days and to when you train, at the time the plan is generated. The planner is designed to produce one grocery list for the week and a prep order for Sunday. It is also designed to turn each day into a checklist you work through rather than a log you fill in afterwards. Mero is not yet publicly available; join the Mero waitlist for availability updates.
The training meal plan page sets out the hard, easy and rest structure, and the planner page covers where the numbers come from.