Most nutrition apps act as rearview mirrors, tracking past data without providing a path forward; KEXBI replaces manual logging with a signal-responsive engine that manages your physiological state.
If you are evaluating nutrition software, you have likely realised that the market is saturated with digital ledgers. You are familiar with the routine: apps that require you to scan barcodes, weigh food to the gram, and stare at a static dashboard of numbers.
The question is not which app has the best charts or the largest database. The question is: what does the software actually do with your data?
When KEXBI was engineered, the objective was not to build another calorie tracker. The objective was to build an autonomous chrononutrition engine. To understand why that distinction matters, here is where each generation stops, and where KEXBI begins.
MyFitnessPal is the legacy heavyweight of the industry. It operates as a rules-based ledger. The system provides a static target derived from a generic formula and asks the user to log their food. It does not know if a user's metabolism has adapted to a prolonged deficit. It does not know if the user slept poorly. It simply counts backwards from a static number.
Cronometer serves as the clinical upgrade to this basic system. For individuals who need to track 84 different micronutrients down to the milligram, Cronometer is exceptional. But it shares the same fatal architectural flaw as MyFitnessPal: it is a rearview mirror. It displays exactly what happened yesterday, but it possesses zero autonomy to construct a biological protocol for tomorrow. Furthermore, both systems will silently allow a user to set a caloric deficit so aggressive that it risks severe endocrine disruption.
MacroFactor effectively solved the static formula problem. By continuously analysing a user's weight trend against their logged food intake, its deterministic algorithm accurately calculates shifting metabolic rates. It is an excellent, mathematically sound tool for retrospective weight management.
However, MacroFactor is intentionally "adherence neutral." The platform provides a weekly numerical target and leaves the execution entirely to the user. It does not factor in chronobiology; it makes no distinction whether daily carbohydrates are consumed pre-workout or in one sitting at 11:00 PM. It explicitly ignores wearable data, meaning that a crashed Heart Rate Variability (HRV) or severely degraded sleep architecture will never alter the spreadsheet of numbers it assigns. Crucially, if a user wishes to drop their calories into the physiological danger zone, MacroFactor will allow them to override its soft warnings and do it. It is a highly advanced calculator, not a clinical guardian.
One structural consequence of that adherence neutrality: the platform cannot produce a shopping list. A list requires meals, quantities, a periodised week and a pantry. MacroFactor gives you a number and refuses to prescribe. It is not a limitation of effort. It is what "adherence neutral" means.
Every food tracker in the category, from MyFitnessPal to Cronometer to MacroFactor, operates on a shared architectural assumption: the food has to exist first. You buy it, you cook it, you eat it, then the app has something to grade. Their entire value arrives downstream of every decision that mattered.
Which means on Saturday morning, standing in the aisle, the single highest-leverage moment of the week, the moment that determines what is physically possible to eat for the next seven days, the app that is supposed to manage your nutrition has nothing to say. You buy roughly what you always buy. Then you spend the week improvising against a number, and the app grades you on Sunday.
KEXBI inverts the order. The week is planned before you shop. Which means the shopping list is not an add-on to the plan. The shopping list is the plan, in physical form. It is the plan you can push around a trolley. That reframe converts an abstract claim (timed fuelling, chrononutrition) into something you can hold. It is very hard to disbelieve a plan you have already bought the ingredients for.
This is not a feature a tracker can bolt on. To generate a real shopping list you must first know:
The comparison table below scores those capabilities row by row. This chapter is what those rows feel like to a user.
Batch cooking on Sunday and cooking fresh on Wednesday need different shopping. Different quantities, different perishables, different formats. Your week is built to the mode you chose, and the shopping follows from the meals. Different mode, different meals, different shop. That is the difference between "here are seven recipes" and "here is your week, the way you actually run it."
Two things this is not. It is not a meal-kit service. Nothing is bought on your behalf, no products are pushed, no affiliate cart sits behind the download button. And it is not a checklist you assembled by hand from recipes you picked. The list is derived from the periodised week the engine already built for you, and it comes to you separated: what you need to buy, and what you already keep as pantry staples. You judge the rest.
Eight moments across a training week. What a tracker does at each. What KEXBI does at each. Everything in the KEXBI column is drawn from the live Weekly Plan flow.
| Moment | A food tracker | KEXBI |
|---|---|---|
| Friday planning | Nothing. | One sitting. The week is planned around your training, your clock, your pantry, your tastes. You choose: batch prep, or cook fresh. |
| Saturday, the shop | Silent. You buy what you always buy. | You shop the plan. The list arrives split into what to buy and what you already keep, so the trolley matches the week ahead. |
| Sunday prep | Nothing. | Two batch cooks, about three hours, done. Or nothing at all, if you chose cook-fresh. |
| Monday to Friday, meals | Eat, then search a database to log it. It tells you what you did. | Grab and go. Every meal already right, already timed to the session. |
| The hard session | Same daily number as your rest day. | The day was built heavier and placed around the workout. |
| 9pm, 40 g of protein short | You improvise. Nothing in the fridge fits. | Does not happen. The food for that meal was bought on Saturday. |
| Thursday, out of the one thing | Unplanned shop, or a compromised day. | Flagged before the week started. |
| Sunday night review | A week of red and green. You know how you did. You still do not know what to do next week. | Next week is already building. |
One plan. Rebuilt when your signals change.
KEXBI does not track what you ate. It tells you what to eat, timed to your biology, built from your kitchen. KEXBI delivers a timed protocol, generated autonomously by 26 logic nodes, built directly from the food already available in your kitchen via the Shadow Pantry.
Other applications read sleep and HRV metrics merely to display a graph. KEXBI reads Apple Health data and acts upon it. If a user's Sleep Impact Score drops, the system flags the degraded state, and the next rebuild prioritises physiological repair over fat loss.
Human metabolism operates on a circadian axis. Eating the exact same macronutrients at 8:00 AM versus 11:00 PM yields entirely different physiological responses. KEXBI uses chronotype and location-aware solar data to distribute fuel across four specific biological windows.
Other applications allow users to starve themselves. KEXBI enforces hard, clinical safety guardrails calculated against individual Lean Body Mass. The user cannot override the Safety Sentinel. The system will not compromise the endocrine system for a faster drop on the scale.
Platforms like MyFitnessPal rely on gamification, arbitrary streaks, and dopamine triggers to maintain user engagement. KEXBI shipped silence on purpose. Every notification sent is a necessary decision point, not a distraction.
Every dimension shown. No cherry-picking. The full table is the proof.
| Dimension | MyFitnessPal | Cronometer | MacroFactor | KEXBI (Cohort 001) |
|---|---|---|---|---|
| A · Core Function | ||||
| Fundamental Role | Digital food diary and calorie counter based on standard formulas. | High-precision micronutrient tracker and clinical diet analysis tool. | Deterministic diet coach adjusting targets via weight-trend algorithms. | Autonomous chrononutrition engine managing timed fuel, hydration, and recovery. |
| Energy Calc. Method | Static formulas (Mifflin-St Jeor) + wearable exercise calories. | Static formulas + wearable exercise calories. | Adaptive algorithm (weight trend + logged food intake). | Dynamic algorithm (biosignals, training load, body composition). |
| Target Adjustments | Manual, or prompts every 10 lbs lost. | Manual. | Weekly, based on algorithm output. | Real-time / upon signal change (~3 min). |
| B · Nutrition Tracking | ||||
| Manual Logging | Search, Barcode, Meal Scan (vision). | Search, Barcode, AI Photo logging. | Search, Barcode, AI Photo logging. | Unnecessary (system generates meals for the user). |
| Meal Generation | Premium+ suggests static meal plans. | No. | No. | Yes. Generates timed daily plans. |
| Pantry Integration | Basic (checks off existing items for lists). | No. | No. | Yes (Shadow Pantry preferences shape meal selection). |
| Macro Tracking | Yes. | Yes. | Yes. | Yes. |
| Micro Tracking | Basic vitamins/minerals. | Extremely deep (84+ nutrients). | Standard vitamins/minerals. | Yes (macro + micronutrient tracking). |
| Food Quality Scoring | No composite scoring. | Yes (Nutrition Scores based on groups). | No composite scoring. | Yes (Fuel Score & Drag Score / GI risk). |
| C · Timing & Periodisation | ||||
| Daily Distribution | No (user-managed). | No. | No (adherence-neutral). | Yes. Distributed across 4 biological windows. |
| Training Windows | No. | No. | No. | Yes (morning, mid-session, evening, pre-sleep). |
| Circadian Biology | No. | No. | No. | Yes (DLMO, MSFsc chronotype integration). |
| Carb Periodisation | No. | Yes (via manual Macro Scheduler). | Yes (via manual Collaborative mode). | Yes. Autonomously scales by training day. |
| Chrononutrition | No. | No. | No. | Yes (solar calculator for location-aware timing). |
| D · Wearable Integration | ||||
| Connected Wearables | Apple Health, Garmin, Fitbit, etc. | Apple Health, Garmin, Whoop, Oura, etc. | Apple Health, Health Connect. | Apple Health (bridging Garmin, Whoop, Oura). |
| Data Actually Read | Steps, HR, Workouts, Sleep. | Steps, HR, HRV, Sleep, SpO2, Temp. | Steps, Weight. | Sleep staging, HRV, RHR, Training Load. |
| Plan Modification | Adds false "calories burned" to daily total. | Display only / Adds burned calories. | Ignored for TDEE calculations. | Actively rebuilds nutrition and recovery plan. |
| E · Hydration | ||||
| Tracks Hydration? | Yes (manual entry). | Yes (manual entry widget). | Yes (manual entry). | Yes (full hydration architecture). |
| Calculates Targets? | Static flat goal. | Static flat goal. | Static flat goal. | Yes (dynamic). |
| Factors Included | None. | None. | None. | Body weight, load, thermals, weather, gastric limit. |
| Times Hydration? | No. | No. | No. | Yes (timed protocol + Shirreffs 150% post-workout). |
| F · Sleep & Recovery | ||||
| Reads Sleep Data? | Yes (display only). | Yes (display only). | No. | Yes. |
| Adjusts Nutrition? | No. | No. | No. | Yes (sleep data directly modifies next-day plan). |
| Sleep Impact Score | No. | No. | No. | Yes (3-sector: Performance, Repair, Fuel). |
| Prioritises Recovery | No. | No. | No. | Yes (in next-day plan generation). |
| G · Body Composition | ||||
| Tracks Trends | Basic plotting. | Basic plotting. | Advanced trend-weight smoothing. | TrendEngine (7-day weight trend variance guard). |
| LBM/FFM in Calcs | No. | No. | No. | Yes (Boer formula or direct comp input). |
| Goal Projections | Basic linear. | Basic linear. | Advanced algorithmic. | Advanced fat-loss projection. |
| H · Physiological Safety | ||||
| Minimum Cal Floor | 1,200 (F) / 1,500 (M). Static. | None. | "Standard" 1,200 or uniquely low estimate. | Yes. Dynamic, based on individual LBM/FFM. |
| EA / RED-S Logic | No. | No. | No. | Yes (Energy Floor Alert at 30 kcal/kg FFM). |
| Hormonal Fat Floor | No. | No. | Soft floor in 'Coached' mode only. | Yes (hard floor at 0.66 g/kg to protect endocrine function). |
| Fat-loss Limiter | No. | No. | Soft warning. | Yes (hard cap to prevent lean mass catabolism). |
| Safety Sentinel | No. | No. | No. | Yes (dedicated Safety Sentinel blocks all violations). |
| LBM-Aware Floors | No (static for all weights). | No. | No. | Yes. |
| Warns Underfuelling | Yes (if closing diary <1,000/1,200). | No. | No. | Yes. Actively blocks the unsafe protocol. |
| User Overrides? | Yes. | Yes. | Yes (via Collaborative / Manual mode). | No. ("Protects metabolism from ambition"). |
| I · AI / Automation | ||||
| System Type | Rules-based. | Rules-based. | Deterministic ML. | LLM + Deterministic Hybrid. |
| Logic Nodes | 0. | 0. | 0. | 26 (20 cloud, 5 on-device, 1 voice). |
| Generates Plans? | Suggests generic Premium meals. | No. | No. | Yes. |
| Rebuilds on Signals | No. | No. | No (updates weekly on weigh-in). | Yes. User-triggered, ~3 min full recalculation on signal change. |
| J · Shopping / Kitchen | ||||
| List derived from a planned week | Shopping-list feature exists (Premium+), but not derived from a periodised plan. | No. | No. Gives a number, prescribes nothing. | Yes. Quantities from the periodised week ahead, split into buy vs already-keep. |
| Adapts to batch-prep vs cook-fresh | No. | No. | No. | Yes. |
| Shopping Lists | Yes (Premium+). | No. | No. | Yes (consolidated across protocols). |
| Pantry Inventory | Basic item exclusion. | No. | No. | Yes (Shadow Pantry, a persistent preference model of what you keep). |
| Builds from Pantry | No. | No. | No. | Yes. |
| K · Platform & Pricing | ||||
| Platforms | iOS, Android, Web. | iOS, Android, Web. | iOS, Android. | iOS only (iPhone 16+, iOS 18+, TestFlight Beta). |
| Free Tier | Yes (Ads, basic logging). | Yes (Ads, limited 7-day history). | No (7-day trial only). | No. |
If the goal is to manually scan barcodes and hit a generic daily number, MyFitnessPal is free. If the goal is to track micronutrients on a highly precise spreadsheet, Cronometer is unmatched. If the goal is to use the best weight-trend algorithm to adjust weekly caloric targets, MacroFactor is superb.
But for a system that autonomously manages fuel, hydration, and recovery, timed to circadian biology, rigorously safeguarded against metabolic damage, and delivered as the food you actually shop for and cook, there is only one option.
KEXBI is currently iOS only (iPhone 16+, iOS 18+) and restricted to closed beta. The length of this table is the argument.