Memory beats prediction.

Executive summary#

The current product vision is pointed at the right problem. Its strongest ideas—memory over prediction, reusable Meal Templates, a Today/Food/Journal structure, and validation before algorithm changes—directly answer the failures users describe in competing products.

The opportunity is not an “AI calorie tracker” in the way the category now uses that phrase. It is a memory-first nutrition decision system: exact when exact data exists, assistive when uncertainty exists, and progressively more useful as it learns the user’s routines.

Across the three communities, users consistently reward five things:

1. Fast repeat logging with search, recent foods, copy, recipes, and barcode scan.
2. Accurate nutrition data with clear units and easy corrections.
3. A compact daily diary that shows the whole day, meal totals, and calories remaining.
4. Reliable history, export, and health-platform syncing.
5. Coaching that explains what is happening without judging the user.

Each competitor owns a different part of that value:

• MacroFactor owns adaptive coaching. Users most value its expenditure algorithm, weekly calorie adjustments, fast logging, weight trend, adherence-neutral tone, and responsive product team. Its main gaps are international food coverage, the requirement for complete food logging, a learning curve, and long-standing requests for desktop access and more consistent gram-based search.
• Lifesum owns visual motivation. Users historically love its approachable design, meal ratings, Life Score, recipes, plans, and habit trackers. Recent sentiment is much weaker because its premium AI experience adds steps, hides familiar search workflows, and can generate inaccurate entries. Long-running requests for gram-based recipe portions, complete history, export, flexible meal categories, and dependable sync remain unresolved.
• MyFitnessPal owns breadth and habit lock-in. Its enormous food catalogue, barcode coverage, saved foods and recipes, long history, web access, and wearable ecosystem keep people using it. Its 2026 redesign produced the sharpest backlash in the sample: users say the daily diary became less dense, common actions take more taps, and important copy or multi-select workflows disappeared. Database duplication, ignored corrections, ads, price, and the barcode paywall compound the frustration.

The strategic opening for the unnamed product is a frictionless, explainable tracker for serious nutrition users:

• Today turns logged food into a clear next action without hiding the compact daily record;
• Food owns the detailed day-by-day record, reconciliation, and selected-item actions;
• Journal connects validated weeks, plan evidence, weight, photos, and measurements without overstating causality;
• familiar meals become reusable memory, not repeated search work;
• barcode and search remain exact first-class paths, while voice creates a reviewable draft;
• food data and recommendations expose source, confidence, and corrections;
• coaching celebrates consistency, stays non-moralizing, and can be turned off;
• history and export remain permanent because the user owns the data.

The PRD is strongest at the product-loop level. Competitor evidence supports its current Food Log Event, Meal Group, and Meal Template model, recipe batch-weight handling, data provenance, complete history/export, review states for voice or AI estimates, and measurable safeguards around incomplete weekly data.

1. Method#

Sources#

The synthesis prioritizes:

• Reddit discussions in r/MacroFactor, r/lifesum, and r/Myfitnesspal;
• cross-switching discussions in r/loseit, where users explain why they leave one tracker for another;
• current official product and support pages;
• current Apple App Store listings and selected reviews;
• App Store metadata already saved in this repository.

The named evidence set in the appendix contains 45 community threads, plus official and App Store sources. Most evidence comes from 2024–2026. Older threads are included only when the same request remains current or when they reveal a durable product strength.

How frequency is reported#

This is directional product research, not a representative survey. “Frequency” combines repetition across independent discussions with visible engagement.

Reddit scores are snapshots and should not be treated as exact demand counts. They are most useful for comparing salience within a community.

Important sampling caveats#

• MacroFactor’s subreddit is closely moderated by its team. Pure feature requests are routed to a separate roadmap, so Reddit undercounts request volume. The team explicitly explains this routing in its setup and feedback post and in a 2026 discussion about removed request posts.
• Lifesum’s subreddit is small. Repetition across several low-score threads can be more meaningful than one score alone.
• MyFitnessPal’s 2026 redesign dominates recent conversation. It is a genuine churn signal, but it temporarily makes the sample more negative.
• App Store ratings aggregate many years and versions. They show scale and broad satisfaction, not current feature sentiment.

2. Market snapshot#

Sources: MacroFactor App Store, Lifesum App Store reviews, and MyFitnessPal App Store.

The products are not interchangeable:

• MacroFactor is the strongest decision engine.
• Lifesum is the strongest visual and lifestyle wrapper.
• MyFitnessPal is the strongest catalogue and ecosystem.

Highest-signal requests at a glance#

This ranking is based on repeated independent mentions and visible engagement, not a claim about the total customer base.

3. MacroFactor#

Product position#

MacroFactor estimates a user’s real-world energy expenditure from logged intake and weight trend, then adjusts calorie and macro targets. The company positions the product as premium, ad-free, science-backed, and fast to log. Its current feature set includes adaptive programs, micronutrients, barcode and label scanning, AI-assisted logging, recipe import, health-platform integration, widgets, and weight-trend analytics. See the official feature page and App Store listing.

Features users appreciate most#

Pain points#

Most repeated wishes#

Historically high-demand requests that MacroFactor delivered#

This matters because it builds product trust:

• Home-screen widgets were identified as the number-one roadmap request before release. The launch post received a score near 200. Widgets release.
• Favorite foods were described by the team as the feature users rallied around most. Favorites release.
• Recipe import launched to strong engagement and was followed by photo and text import. URL importer and photo/text importer.
• Nutrition-label scanning now helps close international database gaps and drew strong praise in July 2026. Label-scanning update.

MacroFactor takeaway#

MacroFactor proves that users will pay for a tracker when the product produces a decision they cannot easily make themselves. Its moat is not calorie storage; it is the trusted loop from honest input to understandable adjustment.

The product should emulate MacroFactor’s loop and tone, not its complexity. Weekly check-in is the right place to explain uncertainty, show why a target changed, and ask users to validate incomplete inputs before any recommendation changes.

4. Lifesum#

Product position#

Lifesum presents nutrition as an attractive lifestyle experience. Its public feature set includes classic and AI-assisted food tracking, programs, meal plans, recipes, Life Score, water and habit tracking, and health integrations. See the official features, how-it-works page, and premium description.

Features users appreciate most#

Pain points#

Most repeated wishes#

Lifesum takeaway#

Lifesum demonstrates that design can make nutrition tracking feel humane and motivating. It also shows how quickly that advantage disappears when a redesign increases action count or makes exact data harder to reach.

The product should borrow Lifesum’s warmth, not its scoring rigidity. “Celebrate consistency over perfection” is a stronger principle than rating food. Positive feedback can highlight patterns such as protein, fiber, and produce without labeling a meal “bad.” Voice and AI should be additional input modes, never the only obvious path.

5. MyFitnessPal#

Product position#

MyFitnessPal is the scale incumbent. It combines a vast food database, food and exercise diary, web access, recipes, goals, reports, wearable integrations, meal planning, AI coaching, voice and meal scan, fasting, and GLP-1 support. The current free product remains ad-supported; barcode scanning is officially a premium feature. See the product page, premium feature list, and barcode support page.

Features users appreciate most#

Pain points#

Most repeated wishes#

MyFitnessPal takeaway#

MyFitnessPal shows that database breadth, durable history, and repeat workflows can create a decade-long habit. It also shows the danger of changing the core diary to promote reporting, coaching, ads, or AI.

The Today Command Centre should treat the diary as a high-frequency instrument. Every visual element must justify the space or tap it consumes. Suggested actions and helpful insights should layer onto a stable compact log, not displace it.

6. Cross-competitor comparison#

7. What users are really asking for#

7.1 Certainty before novelty#

Users prefer an exact barcode, known food, recipe, or weight to a plausible AI estimate. AI is valuable for restaurant meals and forgotten photos, where uncertainty already exists. It is harmful when it replaces an exact path.

Design rule: present search, barcode, recents, favorites, and recipes before or alongside AI. Label every estimate and make it editable.

7.2 Fewer actions for repeated behavior#

Food tracking is repetitive by nature. The best products learn the user’s routine:

• repeat yesterday;
• copy a meal;
• multi-select recent items;
• remember the usual portion;
• favorite multiple portion presets;
• share the household meal;
• pre-log future days.

Design rule: optimize repeat logs before optimizing first-time discovery.

7.3 Trustworthy data, not just a large database#

MyFitnessPal proves that breadth has value, but duplication makes each search a verification task. MacroFactor proves that curation builds trust, but international gaps create manual work. Lifesum shows how difficult corrections make a mediocre database worse.

Design rule: every result should expose source, market, serving basis, and confidence. Let users save a corrected local version immediately even if global moderation takes time.

7.4 A dense diary is a feature#

Large cards and progressive disclosure can look modern but perform poorly in a high-frequency utility. Users want to answer three questions at a glance:

1. What have I logged?
2. How much have I used?
3. What remains?

Design rule: keep the whole day and per-meal totals visible. Offer detail on tap, not by default.

7.5 Ownership creates long-term trust#

Lifesum’s 30-day history limit and MyFitnessPal’s lock-in both create anxiety. Users increasingly expect export, backups, and interoperability.

Design rule: unlimited history, CSV/JSON export, and deletion are product features, not compliance footnotes.

7.6 Motivation must be configurable#

One person loves a streak or smiley; another finds it obsessive. One wants macro coaching; another intentionally eats high carbohydrate. Fixed “healthy” judgments fail across contexts.

Design rule: separate facts from advice. Let users turn off streaks, ratings, commentary, and calorie visibility independently.

10. Recommended positioning direction#

Working positioning—without a product name#

A memory-first calorie tracker for serious nutrition users. It makes daily logging fast, shows what to do next, and turns trustworthy weekly data into one explainable recommendation.

Why this can win#

• It takes MacroFactor’s trusted decision loop and adds explicit incomplete-data validation.
• It takes Lifesum’s approachable guidance without making scores or AI the gatekeeper.
• It takes MyFitnessPal’s reusable history and repeatability without relying on clutter or lock-in.
• It connects daily action, weekly strategy, and long-term change in one coherent loop.

The product promise to protect#

Remember what works. Show what changed. Recommend only what the data can support.

Appendix A: source index#

MacroFactor community#

1. Setup, FAQs, and app feedback
2. New to tracking, love the app
3. Fast food logger discussion
4. 2025 food-logging speed benchmark
5. Favorite foods release
6. Widgets release
7. Recipe importer release
8. AI photo and text recipe import
9. AI-powered food logging beta
10. Label scanning and Weight Trend V2
11. Waiting on missing roadmap features
12. European food database
13. Desktop request
14. Recipe and food sharing
15. Health Connect discussion

Lifesum community#

1. Premium made the app worse
2. Thoughts on the new update
3. Suggestions and feature requests
4. Recipe serving size
5. How to use recipes
6. Custom recipe serving sizes
7. Alternatives and historical data
8. Looking at old entries
9. Premium price increase
10. Wrong nutrition values
11. Custom meal groups
12. Meal categories and multimodal tracking
13. Google Fit sync
14. Apple Health sync
15. Windows/web request

MyFitnessPal and cross-switching communities#

1. Why the app facelift sucks
2. Layout backlash
3. List of functionality lost in the update
4. New update is terrible
5. Replacement recommendations
6. Barcode scanner paywall announcement reaction
7. Regional barcode and price change
8. Premium and food-database accuracy
9. Database cleanup discussion
10. Food correction requests
11. Duplicate saved meals
12. Fitbit sync incident
13. Google Health duplicate foods
14. Garmin and switching friction
15. Feature suggestions and ideas

Official and App Store sources#

• MacroFactor official features
• MacroFactor App Store
• Lifesum official features
• Lifesum current feature updates
• Lifesum App Store reviews
• MyFitnessPal official product page
• MyFitnessPal premium features
• MyFitnessPal 2026 Today-tab explanation
• MyFitnessPal App Store