# Competitor user research: MacroFactor, Lifesum, and MyFitnessPal

**Prepared for:** Unnamed memory-first calorie tracking product
**Research date:** 23 July 2026  
**Decision refresh:** 26 July 2026
**Product direction:** [Living Product Vision v0.2](../product/calorie-app-prd-v0.2.md)  
**Primary question:** Which features do users value most, what causes friction or churn, and how should those findings shape the current product vision?

## 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.

| Tier | Meaning |
|---|---|
| **Very high** | Repeated across at least four independent sources, or a 100+ score discussion corroborated elsewhere |
| **High** | Repeated across three sources, or a strongly engaged request corroborated elsewhere |
| **Medium** | Appears in two independent sources or a smaller multi-user thread |
| **Emerging** | One clear source or a narrower use case |

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](https://www.reddit.com/r/MacroFactor/comments/15u5j6t/read_this_first_setup_faqs_and_app_feedback/) and in a [2026 discussion about removed request posts](https://www.reddit.com/r/MacroFactor/comments/1srs36i/i_love_this_app_but_will_this_ever_be_fixed/).
- **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

| Product | Core promise | Current public signal | Community shorthand |
|---|---|---|---|
| **MacroFactor** | Adaptive nutrition coaching based on observed intake and weight trend | About 4.8/5 from roughly 19K US App Store ratings; premium and ad-free | “The tracker that does the math for me” |
| **Lifesum** | Attractive, lifestyle-oriented nutrition guidance and meal plans | About 4.7/5 from roughly 145K US App Store ratings | “The beautiful tracker that helps me eat better” |
| **MyFitnessPal** | Comprehensive food, exercise, and nutrition tracking at global scale | About 4.7/5 from roughly 2.3M US App Store ratings | “The database where all my history already lives” |

Sources: [MacroFactor App Store](https://apps.apple.com/us/app/macrofactor-macro-tracker/id1553503471), [Lifesum App Store reviews](https://apps.apple.com/us/app/lifesum-ai-calorie-counter/id286906691?see-all=reviews), and [MyFitnessPal App Store](https://apps.apple.com/us/app/myfitnesspal-calorie-counter/id341232718).

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.

| Product | Rank | Request | Observable signal |
|---|---:|---|---|
| **MacroFactor** | 1 | Better regional food and barcode coverage | Repeated across at least four European/international discussions; July 2026 label OCR addresses part of the need |
|  | 2 | Unified 100 g search and consistent gram defaults | Central complaint in a roadmap thread with a score around 35 and a team response around 68 |
|  | 3 | Desktop/web access | Repeated long-running request, especially for recipe work, analysis, and accessibility |
|  | 4 | Meal suggestions that fit remaining macros | Visible roadmap item with multi-user support |
| **Lifesum** | 1 | Restore classic search and make AI optional | A score around 36 is exceptional in the small subreddit; corroborated by update threads and App Store reviews |
|  | 2 | Log recipes by total batch weight and grams eaten | At least five distinct Reddit discussions from 2022–2026 |
|  | 3 | Restore full history and self-service export | At least three distinct discussions; some users explicitly call the 30-day limit a deal breaker |
|  | 4 | Custom meal categories and better pre-logging | Repeated across shift-work, fasting, and general feature-request discussions |
| **MyFitnessPal** | 1 | Restore or toggle the compact daily diary | Multiple 2026 threads with scores around 216, 303, 108, and 31, plus a cross-switching thread around 278 |
|  | 2 | Keep barcode scan in core logging or lower the price | The original cross-community backlash reached roughly 3,800; later regional threads repeat the objection |
|  | 3 | Clean the database and make corrections effective | Repeated across database, premium, correction, and switching discussions |
|  | 4 | Restore copy, multi-select, rearrange, and per-meal totals | Repeated in update-loss threads and the official feature forum |
|  | 5 | Let users disable AI commentary, streaks, and pop-ups | Repeated in Reddit, App Store reviews, and the feature forum |

## 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](https://macrofactor.com/macrofactor/) and [App Store listing](https://apps.apple.com/us/app/macrofactor-macro-tracker/id1553503471).

### Features users appreciate most

| Appreciated feature | Frequency | Evidence and interpretation |
|---|---:|---|
| **Adaptive expenditure and weekly coaching** | Very high | This is the clearest reason users choose and stay. Users describe personalized expenditure as the missing piece that static activity multipliers could not provide. A recent newcomer praised understandable expenditure and calorie targets that did not leave them starving; a long-time comparison calls the algorithm a game changer. [New user thread](https://www.reddit.com/r/MacroFactor/comments/1u0tos2/new_to_tracking_love_the_app/), [comparison with MyFitnessPal](https://www.reddit.com/r/MacroFactor/comments/1kgp4l5/how_do_you_guys_like_macrofactor_compared_to/), [long-term MFP switcher review](https://www.reddit.com/r/MacroFactor/comments/1j0ljvq/a_detailed_review_from_a_long_term_1414_day/). |
| **Fast food logging** | Very high | Speed mode, recent foods, copy/paste, recipes, barcode shortcuts, and a responsive UI are repeatedly praised. Users say logging becomes much easier after the first week and can take seconds for familiar foods. [Fast logger discussion](https://www.reddit.com/r/MacroFactor/comments/v740hz/what_is_the_fastest_food_logger_we_designed_a/), [2025 speed benchmark discussion](https://www.reddit.com/r/MacroFactor/comments/1nqatrq/new_app_insight_is_macrofactor_still_the_fastest/), [new-user comparison](https://www.reddit.com/r/MacroFactor/comments/y29zgw/giving_it_a_try/). |
| **Adherence-neutral feedback** | High | Users value that the app adjusts from what they actually ate instead of punishing missed targets. One discussion describes the system as rewarding honest logging; another recent post emphasizes that over- or under-target days do not “break” the algorithm. [Aha-moment thread](https://www.reddit.com/r/MacroFactor/comments/1jaf19q/whats_been_your_biggest_aha_moment_from_using/), [algorithm reassurance](https://www.reddit.com/r/MacroFactor/comments/1uwevwu/psa_you_cant_mess_up_the_algorithm/). |
| **Trend weight and rich, explainable analytics** | High | Users appreciate smoothing daily weight noise and seeing expenditure, deficit, and nutrition relationships. The new weight-trend algorithm drew positive reactions, especially for handling water-weight fluctuation. [Weight Trend V2 discussion](https://www.reddit.com/r/MacroFactor/comments/1up3cgz/582_new_ai_custom_food_creation_label_scanning/), [App Store reviews](https://apps.apple.com/us/app/macrofactor-macro-tracker/id1553503471?see-all=reviews). |
| **Recipe creation, import, and sharing** | High | Recipe workflows have become a retention feature. The 2025 importer launch received strong engagement, and the 2026 photo/text import expansion was welcomed. Users also value sharing recipes with a partner. [Recipe importer release](https://www.reddit.com/r/MacroFactor/comments/1m96gw6/release_522_recipe_importer/), [photo/text import release](https://www.reddit.com/r/MacroFactor/comments/1s9taxj/576_new_ai_photo_and_text_recipe_import_options/), [food sharing discussion](https://www.reddit.com/r/MacroFactor/comments/193jxii/can_i_share_food_information_with_other_users/). |
| **Visible product iteration and developer responsiveness** | High | Users notice frequent releases, detailed explanations, direct support, and delivery of requested features. Favorites, widgets, recipe import, label scanning, and regional improvements are visible proof. [Favorites release](https://www.reddit.com/r/MacroFactor/comments/1j3dd4v/release_440_favorite_foods/), [widgets release](https://www.reddit.com/r/MacroFactor/comments/175f0k2/release_230_widgets/), [label-scanning update](https://www.reddit.com/r/MacroFactor/comments/1up3cgz/582_new_ai_custom_food_creation_label_scanning/). |
| **AI that remains inspectable and editable** | Medium–high | Users respond better because AI results are assembled from identifiable foods and can be corrected before logging. This preserves precision rather than replacing it. [AI logging beta](https://www.reddit.com/r/MacroFactor/comments/1jmx5k6/release_500_aipowered_food_logging_now_in_beta/). |

### Pain points

| Pain point | Frequency | Why it matters |
|---|---:|---|
| **Partial logging can distort expenditure** | High | MacroFactor can handle missing days, but not a day where breakfast and lunch are logged and dinner is omitted. This is the product’s acknowledged “Achilles heel.” It increases the cost of imperfect adherence and can confuse casual users. [Official subreddit FAQ](https://www.reddit.com/r/MacroFactor/comments/15u5j6t/read_this_first_setup_faqs_and_app_feedback/), [2025 speed discussion](https://www.reddit.com/r/MacroFactor/comments/1nqatrq/new_app_insight_is_macrofactor_still_the_fastest/). |
| **International and regional food coverage is uneven** | High | European users still report missing branded products or relying on MyFitnessPal as a feeder database. Label scanning reduces the pain, but users still want first-pass recognition. [European database discussion](https://www.reddit.com/r/MacroFactor/comments/1cqwdfc/eu_database_added/), [Portugal user workaround](https://www.reddit.com/r/MacroFactor/comments/1s7qey4/how_to_find_naturalunbranded_foods/), [Europe comparison](https://www.reddit.com/r/MacroFactor/comments/1nzphp0/new_app_insight_macrofactor_vs_myfitnesspal_which/). |
| **The system has a learning curve** | Medium–high | New users can feel overwhelmed by program types, expenditure behavior, timeline logging, settings, and analytics. Several positive reviews still say the app takes a week or longer to become intuitive. [MFP comparison thread](https://www.reddit.com/r/MacroFactor/comments/1kgp4l5/how_do_you_guys_like_macrofactor_compared_to/), [App Store reviews](https://apps.apple.com/us/app/macrofactor-macro-tracker/id1553503471?see-all=reviews). |
| **A seven-day trial may end before the core value appears** | Medium | The algorithm needs enough nutrition and weight data to become convincing. A user can reach the end of the trial before recommendations feel meaningfully personalized. This concern appears in the [setup and feedback thread](https://www.reddit.com/r/MacroFactor/comments/15u5j6t/read_this_first_setup_faqs_and_app_feedback/). |
| **Some old quality-of-life requests stay on the roadmap for years** | Medium–high | Long-time subscribers call out unified 100 g search, default gram servings, trend widgets, and web access. The team says roadmap age does not determine priority. [Missing-roadmap discussion](https://www.reddit.com/r/MacroFactor/comments/1n01rgk/waiting_on_missing_roadmap_features/). |
| **Desktop and web access remain limited** | Medium | Desktop matters for recipe building, data review, accessibility, and people who log while working. Mac users have a workaround, but it is not a complete web product. [Desktop request](https://www.reddit.com/r/MacroFactor/comments/15o5u9r/any_updates_on_bringing_mf_to_desktop/). |
| **Health and wearable pipelines can be fragile** | Medium | Health Connect, Samsung Health, Garmin, and scale pathways can duplicate or omit data. Some failures sit outside MacroFactor, but users experience the whole chain as one product. [Health Connect release discussion](https://www.reddit.com/r/MacroFactor/comments/1b7dl5i/release_265_health_connect/), [Garmin request](https://www.reddit.com/r/MacroFactor/comments/1qlgkog/garmin_integrations/). |

### Most repeated wishes

| User wish | Demand | Current state |
|---|---:|---|
| **More complete regional food coverage** | High | Label scanning improved substantially in July 2026, including non-English labels, but users still want barcodes to resolve without creating an item. |
| **Unified 100 g search and consistent default units** | High | Repeated by long-term users; still a visible roadmap frustration. |
| **A full desktop or web experience** | Medium–high | Especially useful for recipes, retrospective analysis, coaches, and accessibility. |
| **Meal suggestions that fit remaining calories and macros** | Medium | A visible roadmap item and a natural extension of coaching. [Suggestion discussion](https://www.reddit.com/r/MacroFactor/comments/1l79d4w/macrofactor_workouts_coming_jan_2026/). |
| **Simpler explanations during the first two weeks** | Medium | Users need to understand ramp-up, missing days, partial logging, scale noise, and why targets change. |
| **More direct wearable integrations** | Medium | Garmin is a recurring example, though platform-level limitations complicate delivery. |

### 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](https://www.reddit.com/r/MacroFactor/comments/175f0k2/release_230_widgets/).
- **Favorite foods** were described by the team as the feature users rallied around most. [Favorites release](https://www.reddit.com/r/MacroFactor/comments/1j3dd4v/release_440_favorite_foods/).
- **Recipe import** launched to strong engagement and was followed by photo and text import. [URL importer](https://www.reddit.com/r/MacroFactor/comments/1m96gw6/release_522_recipe_importer/) and [photo/text importer](https://www.reddit.com/r/MacroFactor/comments/1s9taxj/576_new_ai_photo_and_text_recipe_import_options/).
- **Nutrition-label scanning** now helps close international database gaps and drew strong praise in July 2026. [Label-scanning update](https://www.reddit.com/r/MacroFactor/comments/1up3cgz/582_new_ai_custom_food_creation_label_scanning/).

### 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](https://lifesum.com/features/), [how-it-works page](https://lifesum.com/how-it-works), and [premium description](https://help.lifesum.com/en/article/what-do-i-get-when-i-buy-premium-1vzq8pz/).

### Features users appreciate most

| Appreciated feature | Frequency | Evidence and interpretation |
|---|---:|---|
| **Attractive, friendly visual design** | Very high | This is Lifesum’s most durable advantage. Users repeatedly describe it as more appealing and less dated than alternatives. Older positive reviews praise its colors, motion, graphs, and ease; even people who leave often miss the UI. [App Store reviews](https://apps.apple.com/us/app/lifesum-ai-calorie-counter/id286906691?see-all=reviews), [long-history and alternatives thread](https://www.reddit.com/r/lifesum/comments/1amd23y/any_good_alternatives_to_lifesum_app_for_tracking/). |
| **Food quality feedback, meal ratings, and Life Score** | High | The smiley ratings and broader food-quality framing motivate some users to improve choices beyond calories. A user credits the app with their most consistently nutritious eating and specifically likes weekly seafood tracking. [Plant-based tracker suggestion](https://www.reddit.com/r/lifesum/comments/10pox8m/suggestion_plant_based_meal_weekly_tracker/), [App Store reviews](https://apps.apple.com/us/app/lifesum-ai-calorie-counter/id286906691?see-all=reviews). |
| **Meal plans, recipes, and programs** | High | Users like having ideas, structure, and diet-specific plans. Recipes can be the reason to subscribe. The strength is inspiration and reduced planning burden, not rigorous coaching. [Shopping-list discussion](https://www.reddit.com/r/lifesum/comments/1h86jtt/shopping_list/), [official meal-plan description](https://lifesum.com/how-it-works). |
| **Classic barcode, search, recent-food, and repeat-meal workflows** | High | The backlash to the new AI experience reveals how valued the older manual flow was. Users describe the previous app as fast, clean, and easy to use. [New-update feedback](https://www.reddit.com/r/lifesum/comments/1irj2gc/thoughts_on_new_update/), [premium regression thread](https://www.reddit.com/r/lifesum/comments/1q6onr4/premium_made_the_app_worse/). |
| **All-in-one lifestyle tracking** | Medium | Water, weight, fasting, exercise, habits, recipes, and food live in one visually consistent product. This appeals to users who want guidance rather than a technical macro tool. |
| **Photo or text logging for rough estimates** | Medium, polarized | Some users like multimodal logging when precision is impossible or speed matters. The value drops sharply when AI becomes the default or replaces verified search. [Meal-category discussion](https://www.reddit.com/r/lifesum/comments/1i21i1s/meal_cataories/), [App Store reviews](https://apps.apple.com/us/app/lifesum-ai-calorie-counter/id286906691?see-all=reviews). |

### Pain points

| Pain point | Frequency | Why it matters |
|---|---:|---|
| **Premium AI makes basic logging harder** | Very high | Users report hidden product search, four or five steps where two previously worked, slow AI, inaccurate recognition, misplaced meal categories, and difficulty editing results. A January 2026 post reached a score in the mid-30s, unusually high for this small subreddit, and accumulated later cancellation comments. [Premium regression thread](https://www.reddit.com/r/lifesum/comments/1q6onr4/premium_made_the_app_worse/), [new-update feedback](https://www.reddit.com/r/lifesum/comments/1irj2gc/thoughts_on_new_update/), [App Store reviews](https://apps.apple.com/us/app/lifesum-ai-calorie-counter/id286906691?see-all=reviews). |
| **Bugs, freezing, logout, missing entries, and lost history** | High | Complaints include quick-track entries not appearing, freezes, repeated logout, disappeared calories, premium entitlements not showing, and AI scans failing. These failures directly undermine diary trust. [Premium regression thread](https://www.reddit.com/r/lifesum/comments/1q6onr4/premium_made_the_app_worse/), [new-update feedback](https://www.reddit.com/r/lifesum/comments/1irj2gc/thoughts_on_new_update/). |
| **Recipes cannot be logged naturally by total cooked weight and grams eaten** | High | This request recurs from 2022 through 2026. Users resort to treating each gram as one “serving” or estimating equal portions. It is a precision failure in a calorie tracker. [Serving-size thread](https://www.reddit.com/r/lifesum/comments/yfmz8d/serving_size/), [recipe workflow thread](https://www.reddit.com/r/lifesum/comments/1hqmbst/how_to_use_recipes/), [custom recipe request](https://www.reddit.com/r/lifesum/comments/1clhk5k/question_about_custom_recipe_serving_sizes/), [portions-in-grams thread](https://www.reddit.com/r/lifesum/comments/14pjst5/recipe_portions_in_grams/). |
| **Only 30 days of food history are visible in-app** | High | Long-term users discovered they could no longer inspect older meals. Support can send a CSV, but users cannot self-export, restore, or browse the data. For people correlating food with symptoms, this is a deal breaker. [Alternatives thread](https://www.reddit.com/r/lifesum/comments/1amd23y/any_good_alternatives_to_lifesum_app_for_tracking/), [old-entry support response](https://www.reddit.com/r/lifesum/comments/1jp1ds0/looking_at_old_entries/), [data-missing thread](https://www.reddit.com/r/lifesum/comments/1e867ew/data_missing/). |
| **Food data can be inaccurate and difficult to correct** | High | Users report mismatched macros, rigid validation, missing foods, and corrections that do not produce a usable result. Manual re-entry defeats the point of tracking. [Nutrition-value comparison](https://www.reddit.com/r/lifesum/comments/1dbjb1w/completely_wrong_nutrition_value_compared_to/). |
| **Price increases, ads, and inconsistent subscription presentation** | High | Users reacted strongly to annual pricing near €100/£100, the introduction of ads, and multiple differently priced annual plans. Several explicitly cancelled. [Price-increase thread](https://www.reddit.com/r/lifesum/comments/1b1fbxk/lifesum_raised_premium_pricing_for_100/), [ads discussion](https://www.reddit.com/r/lifesum/comments/1e67b2n/theres_ads_now/), [renewal confusion](https://www.reddit.com/r/lifesum/comments/1jxh0m7/renewing_premium/). |
| **Rigid meal categories and poor pre-logging behavior** | High | Users want to remove unused meals, create their own, plan future days, and assign items correctly after AI entry. Shift workers and intermittent fasters are poorly served by breakfast/lunch/dinner assumptions. [Custom meal groups](https://www.reddit.com/r/lifesum/comments/utivdn/suggestion_hidedisable_meal_groups/), [meal-category discussion](https://www.reddit.com/r/lifesum/comments/1i21i1s/meal_cataories/), [feature request collection](https://www.reddit.com/r/lifesum/comments/1dtyryu/suggestions_feature_requests/). |
| **Health integrations are inconsistent** | Medium–high | Apple Health and Google Fit/Health Connect users report delayed, missing, or incorrect energy and nutrition values. Water import is also a long-running request. [Apple Health sync](https://www.reddit.com/r/lifesum/comments/mtxvv8/apple_health_syncing_issue/), [Google Fit sync](https://www.reddit.com/r/lifesum/comments/p6c15d/lifesum_not_syncing_with_google_fit_at_all/), [2026 calorie mismatch](https://www.reddit.com/r/lifesum/comments/1q396if/calories_sync_broken_with_google_fit/), [water import](https://www.reddit.com/r/lifesum/comments/kyr93d/water_data_import_in_lifesum/). |
| **Life Score and food ratings can become discouraging** | Medium | The motivational layer can feel moralizing or inconsistent when healthy foods still generate a poor score, a large single meal is penalized, or macros do not adapt to exercise. [App Store reviews](https://apps.apple.com/us/app/lifesum-ai-calorie-counter/id286906691?see-all=reviews), [custom meal-group discussion](https://www.reddit.com/r/lifesum/comments/utivdn/suggestion_hidedisable_meal_groups/). |

### Most repeated wishes

| User wish | Demand | Product requirement implied |
|---|---:|---|
| **Restore a visible manual search and classic logging flow** | Very high | Search, barcode, recents, favorites, and manual creation should coexist with AI. |
| **Make AI optional, editable, and transparent** | Very high | Never force a probabilistic estimate when the user knows the exact brand or weight. |
| **Support total recipe weight and gram-based portions** | High | A recipe needs raw ingredients, final cooked weight, arbitrary grams eaten, and recalculated nutrition. |
| **Restore complete history and self-service export** | High | Users should browse, export, and migrate all their data without contacting support. |
| **Allow custom meal categories or a time-based diary** | High | Support shift work, fasting, grazing, meal prep, and fewer or more than four meal slots. |
| **Improve editing and repeat logging** | High | Multi-select recents, add the same food twice, edit meal assignment, save quick-add items, and keep favorites easy to find. |
| **Make the food database correctable** | High | Show source, allow local overrides, and close the correction loop. |
| **Make meal plans practical for households** | Medium | Adjust servings, repeat meals, swap ingredients, consolidate shopping lists, and account for different household calorie needs. |
| **Provide reliable health and water sync** | Medium–high | Show last-sync status, data source, duplicates, and recovery actions. |
| **Offer desktop or web access** | Medium | Useful for workplace logging and recipe preparation. [Windows request](https://www.reddit.com/r/lifesum/comments/13rz0tn/will_there_be_ever_an_interface_i_can_use_in/). |

### 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](https://www.myfitnesspal.com/), [premium feature list](https://support.myfitnesspal.com/hc/en-us/articles/360032625951-What-are-the-features-of-MyFitnessPal-Premium), and [barcode support page](https://support.myfitnesspal.com/hc/en-us/articles/360032624771-How-do-I-use-the-barcode-scanner-to-log-foods).

### Features users appreciate most

| Appreciated feature | Frequency | Evidence and interpretation |
|---|---:|---|
| **Enormous food and barcode catalogue** | Very high | Even frustrated users say MyFitnessPal finds products that alternatives miss, especially regional and branded foods. This creates powerful lock-in. [Current App Store reviews](https://apps.apple.com/us/app/myfitnesspal-calorie-counter/id341232718?platform=ipad&see-all=reviews), [2026 lost-functionality thread](https://www.reddit.com/r/Myfitnesspal/comments/1rr4vsp/a_list_of_functionalities_lost_since_the_new/), [MacroFactor European workaround](https://www.reddit.com/r/MacroFactor/comments/1s7qey4/how_to_find_naturalunbranded_foods/). |
| **The classic compact daily diary** | Very high | The 2026 redesign backlash is strong evidence of affection for the old one-screen view: meal-separated foods, per-meal calories, exercise, and remaining calories visible together. [Facelift critique](https://www.reddit.com/r/Myfitnesspal/comments/1su1sgi/why_the_app_facelift_sucks/), [new-update critique](https://www.reddit.com/r/Myfitnesspal/comments/1suvznx/new_update_is_terrible/). |
| **Saved foods, recipes, meals, copy, and repeat logging** | High | Long-time users have years of custom foods and reusable meals. Copying a day or meal made tracking efficient and is a major reason switching feels expensive. [Replacement discussion](https://www.reddit.com/r/loseit/comments/1sumcht/myfitnesspal_replacement_recommendations/), [lost-functionality thread](https://www.reddit.com/r/Myfitnesspal/comments/1rr4vsp/a_list_of_functionalities_lost_since_the_new/). |
| **Long-term history and accumulated personal data** | High | Users return because previous foods, recipes, weight records, and diary history remain available. The history becomes a personal asset. [App Store reviews](https://apps.apple.com/us/app/myfitnesspal-calorie-counter/id341232718?see-all=reviews), [2026 update discussion](https://www.reddit.com/r/Myfitnesspal/comments/1suvznx/new_update_is_terrible/). |
| **Web access and broad integrations** | High | Garmin, Fitbit, Apple Health, Health Connect, watches, and a desktop website make MyFitnessPal a hub. Integration reliability varies, but breadth is a competitive advantage. [Fitbit issue thread](https://www.reddit.com/r/Myfitnesspal/comments/1jiw2au/known_issue_connecting_and_syncing_with_fitbit/), [Garmin switching discussion](https://www.reddit.com/r/Myfitnesspal/comments/1sw9mzt/syncing_with_garmin/). |
| **Simple calorie and macro accountability** | High | Users value the basic feedback loop: log intake, see remaining calories and macros, and learn which foods affect progress. [App Store listing and reviews](https://apps.apple.com/us/app/myfitnesspal-calorie-counter/id341232718). |
| **Meal planning, custom goals, reports, and newer health tools** | Medium | Some premium users praise personalized meal plans, grocery lists, configurable nutrient goals, reports, and GLP-1 support. [App Store reviews](https://apps.apple.com/us/app/myfitnesspal-calorie-counter/id341232718). |

### Pain points

| Pain point | Frequency | Why it matters |
|---|---:|---|
| **The 2026 redesign makes the diary slower and less readable** | Very high | Multiple highly engaged threads describe oversized cards, hidden full-day detail, more scrolling, more taps, missing per-meal totals, lost multi-select and copy actions, and poor information density. Scores in the sample include roughly 216, 303, 108, and 278 in a cross-switching thread. [Facelift critique](https://www.reddit.com/r/Myfitnesspal/comments/1su1sgi/why_the_app_facelift_sucks/), [layout backlash](https://www.reddit.com/r/Myfitnesspal/comments/1svfgmm/whoever_chose_this_new_layout_needs_fired_and_asap/), [complaint-coordination thread](https://www.reddit.com/r/Myfitnesspal/comments/1sutzgk/everyone_submit_complaints_about_the_new_update/), [replacement discussion](https://www.reddit.com/r/loseit/comments/1sumcht/myfitnesspal_replacement_recommendations/). |
| **The crowd-sourced food database is broad but unreliable** | Very high | Users see duplicates, outdated entries, impossible serving units, incorrect macros, and even errors on verified items. Reports appear not to change the record. Breadth reduces search failure but increases decision time and distrust. [Database accuracy discussion](https://www.reddit.com/r/Myfitnesspal/comments/1kiiath/does_premium_have_more_accurate_food_data/), [database cleanup thread](https://www.reddit.com/r/Myfitnesspal/comments/19fhv7g/do_you_think_they_will_ever_clean_up_the_database/), [food correction thread](https://www.reddit.com/r/Myfitnesspal/comments/1tgn317/food_corrections/). |
| **Ads, premium price, and the barcode paywall feel extractive** | Very high | Barcode scan was a beloved free feature and users helped build the database. Moving it behind premium generated one of the largest threads in the evidence set, with a score around 3,800 in r/loseit. Regional inconsistency adds confusion. [Barcode announcement reaction](https://www.reddit.com/r/loseit/comments/wwif5p/myfitnesspal_news_barcode_scanner_no_longer/), [2024 regional change](https://www.reddit.com/r/Myfitnesspal/comments/1fv6x9y/they_made_barcode_scanning_a_premium_feature_and/), [2026 UK change](https://www.reddit.com/r/Myfitnesspal/comments/1t266m8/does_anyone_know_what_happened_to_the_free/). |
| **AI commentary can feel judgmental or irrelevant** | High | Users object to unsolicited carb commentary or advice that assumes a diet style. The problem is not only accuracy; it is loss of agency. [Layout and commentary backlash](https://www.reddit.com/r/Myfitnesspal/comments/1svfgmm/whoever_chose_this_new_layout_needs_fired_and_asap/), [current App Store reviews](https://apps.apple.com/us/app/myfitnesspal-calorie-counter/id341232718?platform=iphone&see-all=reviews). |
| **Sync, duplication, login, and sluggishness are recurring** | High | Fitbit outages, Health Connect duplicates, delayed transfers, repeated logouts, and duplicate meal items undermine confidence. [Fitbit issue](https://www.reddit.com/r/Myfitnesspal/comments/1jiw2au/known_issue_connecting_and_syncing_with_fitbit/), [Google Health duplicates](https://www.reddit.com/r/Myfitnesspal/comments/1tz83s6/duplicate_foods_synced_from_myfitnesspal/), [saved-meal duplicates](https://www.reddit.com/r/Myfitnesspal/comments/15xxxso/foods_in_my_meals_are_duplicating_on_their_own/), [App Store review](https://apps.apple.com/us/app/myfitnesspal-calorie-counter/id341232718?platform=ipad&see-all=reviews). |
| **Users feel trapped by accumulated data** | High | Seven to fourteen years of recipes, foods, streaks, and history make departure costly even when the current product frustrates them. This is retention through switching cost, not delight. [New-update critique](https://www.reddit.com/r/Myfitnesspal/comments/1suvznx/new_update_is_terrible/), [Garmin switching discussion](https://www.reddit.com/r/Myfitnesspal/comments/1sw9mzt/syncing_with_garmin/). |
| **Common workflows are fragmented across Recent, Frequent, My Foods, Meals, and Recipes** | Medium–high | Users want one search across their own data and quicker reuse. The current official feature forum contains requests to unify these lists and simplify copy. [Feature suggestion forum](https://community.myfitnesspal.com/en/categories/feature-suggestions-and-ideas). |

### Most repeated wishes

| User wish | Demand | Product requirement implied |
|---|---:|---|
| **Restore the classic diary or provide a compact-view toggle** | Very high | A full day should fit on one page with expandable detail, per-meal totals, and remaining calories. |
| **Restore copy, multi-select, rearrange, and swipe workflows** | High | Repeat logging must optimize for muscle memory and one-to-many actions. |
| **Clean and verify the food database** | Very high | Rank trusted entries, show provenance and market, standardize units, support local correction, and close reports. |
| **Return barcode scanning to core logging or price premium fairly** | Very high | Users see barcode as an input method, not advanced coaching. |
| **Let users disable AI commentary, streaks, and pop-ups** | High | Coaching and motivation should be opt-in and configurable. |
| **Improve health sync and expose status** | High | Show source priority, last successful sync, duplicate detection, and repair. |
| **Preserve and export all history** | High | Make switching and backup possible; retention should come from value, not captivity. |
| **Track more micronutrients and added sugar** | Medium | Current feature requests include added sugars, magnesium, vitamin K, phosphorus, and configurable protein/fiber views. [Feature suggestion forum](https://community.myfitnesspal.com/en/categories/feature-suggestions-and-ideas). |
| **Share foods or meals directly with a partner** | Medium | Households want to avoid duplicate entry. This appears in the official feature forum. |
| **Scan a nutrition label when a local barcode is missing** | Emerging | This is particularly useful outside major markets and reduces manual creation. [Feature suggestion forum](https://community.myfitnesspal.com/en/categories/feature-suggestions-and-ideas?page=2). |

### 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

| Dimension | MacroFactor | Lifesum | MyFitnessPal | Product opportunity |
|---|---|---|---|---|
| **Adaptive coaching** | Best; personalized and adherence-neutral | Mostly plan- and rule-based | Broad coaching features, but can feel generic or judgmental | Explainable adaptive targets with coaching off by default |
| **Logging speed** | Excellent after learning | Classic flow was strong; current premium AI adds friction | Classic flow was strong; 2026 redesign weakens it | Memory-first repeat, barcode, search, and reviewable voice entry |
| **Food coverage** | Curated but weaker internationally | Mixed coverage and correction friction | Widest coverage | Open sources plus local overrides, provenance, and label OCR |
| **Food data trust** | Generally stronger, though not perfect | Inconsistent | Major duplicate and accuracy problem | Verified source hierarchy and closed-loop corrections |
| **Visual design** | Clean and technical | Most attractive and friendly | Familiar but increasingly cluttered | Warm, compact, and configurable |
| **Daily diary** | Powerful time-based timeline | Attractive but rigid meal groups | Classic diary was best for density | Today Command Centre plus a one-screen compact log |
| **Recipes** | Strong and improving | Major gram/serving weakness | Useful and sticky, with update regressions | Batch weight, grams eaten, arbitrary servings, share |
| **History/export** | Strong analytics and portability | Only 30 days visible; support-mediated CSV | Long history is a major asset | Unlimited browsing and one-tap export |
| **Integrations** | Modern platform approach | Broad but unreliable in reports | Broadest ecosystem, uneven reliability | Transparent sync state and conflict repair |
| **Monetization sentiment** | Users accept premium because value is differentiated | Price and premium UX create resentment | Ads, high price, and barcode gating create resentment | Keep core input methods available; pricing strategy remains open |
| **AI sentiment** | Positive when inspectable and optional | Negative when forced and inaccurate | Negative when intrusive or judgmental | Voice/AI creates reviewable drafts; explanations show evidence and confidence |
| **Product trust** | High due to visible iteration and explanation | Declining after unresolved basics and AI shift | Mixed; strong history, weak recent UX trust | Stable core, public changelog, migration guarantees |

## 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.

## 8. Recommendations for the product

### P0: make the daily loop indispensable

1. **Make the Meal Template the reusable centre of product memory.**
   - A Food Log Event preserves what was recorded. A Meal Group organizes selected events. A Meal Template stores a person’s chosen reusable foods, portions, timing, source, and usual edits.
   - Users can repeat, edit as a new version, duplicate, and share a template without changing prior Food Log Events.
   - The product suggests familiar Meal Templates from context such as time, day, and recent behaviour.
   - Repeating a usual meal should take no more than two taps.

2. **Combine the Today Command Centre with a compact full-day log.**
   - Show calories remaining, protein remaining, daily progress, every entry, and per-meal subtotals on one screen or within one tap.
   - Place one suggested next action and one helpful insight above the log without pushing the record out of reach.
   - Support named meal slots and a time-based view.
   - Let users remove, rename, and reorder meal slots.

3. **Use exact inputs before probabilistic ones.**
   - Keep repeat, barcode, and search permanently visible.
   - Use voice as a shortcut that produces an editable draft, not an unquestioned log.
   - Label estimated foods, portions, and nutrition values.
   - Ask for confirmation when uncertainty could materially change calories or protein.

4. **Protect data integrity at capture time.**
   - Show the source and serving basis for every database result.
   - Prefer verified entries and let users correct a food locally.
   - When a barcode fails, offer manual creation or nutrition-label capture without losing context.
   - Keep an undo history for edits, repeated meals, and shared Meal Templates.

5. **Make recipes and prepared meals gram-native.**
   - Distinguish a reusable recipe or Meal Template from immutable Food Log Events.
   - Store ingredient weights and final cooked batch weight.
   - Allow arbitrary servings and arbitrary grams consumed.
   - Preserve the source recipe and preparation notes.

6. **Guarantee complete history and export.**
   - Browse every day since account creation.
   - Export Food Log Events, Meal Groups, Meal Templates, recipes, weight, measurements, photo metadata, and recommendations without contacting support.
   - Use portable CSV for common records and JSON for complete backup.
   - Make deletion and retention controls understandable.

### P1: make the weekly loop trustworthy

7. **Build validation into Weekly check-in.**
   - Identify suspicious or incomplete days before interpreting the week.
   - Let users mark a day complete, incomplete, intentionally untracked, or correct it.
   - Show which days the recommendation uses and which it excludes.
   - Never adjust a target silently.

8. **Give one explainable recommendation.**
   - Connect the recommendation to observed intake, weight trend, adherence, and the user’s goal.
   - State confidence and the evidence window.
   - Let the user accept, defer, or reject it.
   - Celebrate consistency without treating a missed target as failure.

9. **Make photos and measurements serve the journey.**
   - Present comparable dates and measurement conditions.
   - Separate observed change from interpretation.
   - Keep photo visibility private by default.
   - Avoid implying that correlation proves a food or behaviour caused a body change.

10. **Make guidance configurable and non-moralizing.**
    - Highlight objective gaps such as protein, fiber, or sodium.
    - Avoid “good/bad” food labels and diet assumptions.
    - Let users hide streaks, calorie visibility, insights, or recommendations independently.

### P2 and future: expand only after the core loop works

11. **Test pattern detection as hypotheses, not facts.**
    - Require enough repeated observations before surfacing a pattern.
    - Show the supporting days and exceptions.
    - Let users dismiss, correct, or save a pattern.

12. **Add collaboration and integrations with explicit control.**
    - Coach access uses granular, revocable permissions.
    - MCP writes remain attributed, reviewable, and undoable.
    - Shared Meal Templates retain origin and allow independent portion edits.
    - Health integrations expose source, last successful sync, duplicates, and recovery.

### Do not copy

- Lifesum’s forced AI-first logging flow.
- MyFitnessPal’s oversized diary cards and hidden daily overview.
- MacroFactor’s vulnerability to partially logged days without an explicit validation step.
- Any database that accepts duplicate public foods without provenance.
- Advice that comments on a user’s macros without knowing their plan.
- History limits or support-mediated export.
- Recipe portions defined only as equal servings.
- Silent recommendation or integration failures.

## 9. Comparison with Product Vision v0.2

The vision has a strong organising model. The 26 July decision refresh resolves the top-level IA and record model; implementation still needs testable trust and safety acceptance criteria.

| PRD area | Competitor evidence | Assessment | Change for the next PRD |
|---|---|---|---|
| **Vision: most frictionless tracker for serious nutrition users** | Repeat logging and compact diaries drive retention; “serious” users range from macro-focused athletes to people managing weight or health | Strong direction, broad audience | Define the first target segment and the job that makes them “serious” |
| **Today / Food / Journal** | Competitors fragment logging, coaching, and history; MacroFactor’s decision loop is the clearest differentiated value | Confirmed top-level model | Keep Today as the live decision surface, Food as the authoritative daily record, and Journal as the longitudinal plan record |
| **Memory over prediction** | Recent foods, saved meals, recipes, and copy workflows are universally valued; forced prediction creates backlash | Strongly validated | Make reuse rate and repeat-log speed core success metrics |
| **Today Command Centre** | Users want remaining calories and a complete daily view; large insight cards can bury the diary | Valid with a design tension | Keep the compact log visible and cap the surface at one action plus one insight |
| **Repeat, voice, barcode, search** | Repeat and barcode are validated; voice is promising but less proven in this evidence set | Mostly validated | Treat voice as an editable draft and test it against tap count, correction rate, and confidence |
| **Food Log Event / Meal Group / Meal Template** | Saved meals and recipes create retention and reduce switching; sharing also has demand | Confirmed separation of history, grouping, and reuse | Validate identity, versioning, portions, source, recipe relationship, sharing, and copy semantics in implementation |
| **Weekly check-in** | MacroFactor proves the value of adjustment; partial logging is its acknowledged weakness | Differentiated and well targeted | Preserve incomplete-day states, evidence windows, recommendation confidence, and user approval |
| **Photos and measurements** | Long-term progress matters, but competitor evidence here is thinner than food and weight evidence | Plausible, not yet validated | Research privacy expectations, comparison workflows, retention, and whether this belongs in the initial release |
| **Pattern detection** | Users value insights when explainable and dislike generic or moralizing commentary | Good future direction | Set minimum evidence thresholds and always show supporting observations |
| **Privacy, ownership, and data integrity** | History limits, lock-in, database errors, and opaque sync directly erode trust | Critical and validated | Turn principles into requirements for export, deletion, provenance, correction, access, and recovery |
| **Coach, MCP, and AI coaching** | Collaboration has demand; intrusive automation creates backlash | Correctly deferred | Keep outside the initial critical path until logging memory and weekly validation are reliable |

### Resolution status after the decision refresh

1. **Beachhead audience — resolved.** Start with English-speaking serious repeat trackers; clinically supervised workflows remain outside the initial audience.
2. **Record model — resolved at product level.** Food Log Events preserve history, Meal Groups organize selected events, and Meal Templates are explicitly reusable.
3. **Recommendation contract — proposed and documented.** Required inputs, manual-only safety, confidence, explanation, approval, and rollback live in the v0.1 algorithm specification and still require clinical validation.
4. **MVP boundary — resolved.** The daily memory loop, Today/Food/Journal IA, and trustworthy free core precede advanced pattern detection, coaching, and MCP.
5. **Acceptance criteria — still required.** Privacy, ownership, safety, accessibility, and data-integrity principles need implementation-level tests.

### Suggested MVP requirements

- Users can repeat a usual Meal Template in two taps or fewer.
- Users can see calories remaining, protein remaining, and every daily entry without leaving Today.
- Voice entries remain drafts until the user confirms foods and portions.
- Users can mark a day complete, incomplete, intentionally untracked, or corrected.
- Weekly recommendations identify included days, excluded days, evidence, and confidence.
- Every food record exposes source and serving basis.
- Users can correct a food locally and reuse it immediately.
- Recipes accept total cooked weight and grams consumed.
- Users can browse and export their complete history.
- Users can disable suggested actions and helpful insights without losing tracking functionality.

### Success metrics to add

- median taps and time to repeat a usual meal;
- percentage of logs created from existing Meal Templates;
- voice-draft confirmation, edit, and abandonment rates;
- barcode resolution rate and local-correction rate;
- percentage of weeks with validated completeness before recommendation;
- recommendation acceptance, deferral, rejection, and later reversal rates;
- Today task-completion time for calories remaining, protein remaining, and last logged meal;
- complete-history retrieval and export success rates;
- percentage of users who disable insights or recommendations;
- eight-week retention for the chosen serious-nutrition segment.

## 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](https://www.reddit.com/r/MacroFactor/comments/15u5j6t/read_this_first_setup_faqs_and_app_feedback/)
2. [New to tracking, love the app](https://www.reddit.com/r/MacroFactor/comments/1u0tos2/new_to_tracking_love_the_app/)
3. [Fast food logger discussion](https://www.reddit.com/r/MacroFactor/comments/v740hz/what_is_the_fastest_food_logger_we_designed_a/)
4. [2025 food-logging speed benchmark](https://www.reddit.com/r/MacroFactor/comments/1nqatrq/new_app_insight_is_macrofactor_still_the_fastest/)
5. [Favorite foods release](https://www.reddit.com/r/MacroFactor/comments/1j3dd4v/release_440_favorite_foods/)
6. [Widgets release](https://www.reddit.com/r/MacroFactor/comments/175f0k2/release_230_widgets/)
7. [Recipe importer release](https://www.reddit.com/r/MacroFactor/comments/1m96gw6/release_522_recipe_importer/)
8. [AI photo and text recipe import](https://www.reddit.com/r/MacroFactor/comments/1s9taxj/576_new_ai_photo_and_text_recipe_import_options/)
9. [AI-powered food logging beta](https://www.reddit.com/r/MacroFactor/comments/1jmx5k6/release_500_aipowered_food_logging_now_in_beta/)
10. [Label scanning and Weight Trend V2](https://www.reddit.com/r/MacroFactor/comments/1up3cgz/582_new_ai_custom_food_creation_label_scanning/)
11. [Waiting on missing roadmap features](https://www.reddit.com/r/MacroFactor/comments/1n01rgk/waiting_on_missing_roadmap_features/)
12. [European food database](https://www.reddit.com/r/MacroFactor/comments/1cqwdfc/eu_database_added/)
13. [Desktop request](https://www.reddit.com/r/MacroFactor/comments/15o5u9r/any_updates_on_bringing_mf_to_desktop/)
14. [Recipe and food sharing](https://www.reddit.com/r/MacroFactor/comments/193jxii/can_i_share_food_information_with_other_users/)
15. [Health Connect discussion](https://www.reddit.com/r/MacroFactor/comments/1b7dl5i/release_265_health_connect/)

### Lifesum community

1. [Premium made the app worse](https://www.reddit.com/r/lifesum/comments/1q6onr4/premium_made_the_app_worse/)
2. [Thoughts on the new update](https://www.reddit.com/r/lifesum/comments/1irj2gc/thoughts_on_new_update/)
3. [Suggestions and feature requests](https://www.reddit.com/r/lifesum/comments/1dtyryu/suggestions_feature_requests/)
4. [Recipe serving size](https://www.reddit.com/r/lifesum/comments/yfmz8d/serving_size/)
5. [How to use recipes](https://www.reddit.com/r/lifesum/comments/1hqmbst/how_to_use_recipes/)
6. [Custom recipe serving sizes](https://www.reddit.com/r/lifesum/comments/1clhk5k/question_about_custom_recipe_serving_sizes/)
7. [Alternatives and historical data](https://www.reddit.com/r/lifesum/comments/1amd23y/any_good_alternatives_to_lifesum_app_for_tracking/)
8. [Looking at old entries](https://www.reddit.com/r/lifesum/comments/1jp1ds0/looking_at_old_entries/)
9. [Premium price increase](https://www.reddit.com/r/lifesum/comments/1b1fbxk/lifesum_raised_premium_pricing_for_100/)
10. [Wrong nutrition values](https://www.reddit.com/r/lifesum/comments/1dbjb1w/completely_wrong_nutrition_value_compared_to/)
11. [Custom meal groups](https://www.reddit.com/r/lifesum/comments/utivdn/suggestion_hidedisable_meal_groups/)
12. [Meal categories and multimodal tracking](https://www.reddit.com/r/lifesum/comments/1i21i1s/meal_cataories/)
13. [Google Fit sync](https://www.reddit.com/r/lifesum/comments/p6c15d/lifesum_not_syncing_with_google_fit_at_all/)
14. [Apple Health sync](https://www.reddit.com/r/lifesum/comments/mtxvv8/apple_health_syncing_issue/)
15. [Windows/web request](https://www.reddit.com/r/lifesum/comments/13rz0tn/will_there_be_ever_an_interface_i_can_use_in/)

### MyFitnessPal and cross-switching communities

1. [Why the app facelift sucks](https://www.reddit.com/r/Myfitnesspal/comments/1su1sgi/why_the_app_facelift_sucks/)
2. [Layout backlash](https://www.reddit.com/r/Myfitnesspal/comments/1svfgmm/whoever_chose_this_new_layout_needs_fired_and_asap/)
3. [List of functionality lost in the update](https://www.reddit.com/r/Myfitnesspal/comments/1rr4vsp/a_list_of_functionalities_lost_since_the_new/)
4. [New update is terrible](https://www.reddit.com/r/Myfitnesspal/comments/1suvznx/new_update_is_terrible/)
5. [Replacement recommendations](https://www.reddit.com/r/loseit/comments/1sumcht/myfitnesspal_replacement_recommendations/)
6. [Barcode scanner paywall announcement reaction](https://www.reddit.com/r/loseit/comments/wwif5p/myfitnesspal_news_barcode_scanner_no_longer/)
7. [Regional barcode and price change](https://www.reddit.com/r/Myfitnesspal/comments/1fv6x9y/they_made_barcode_scanning_a_premium_feature_and/)
8. [Premium and food-database accuracy](https://www.reddit.com/r/Myfitnesspal/comments/1kiiath/does_premium_have_more_accurate_food_data/)
9. [Database cleanup discussion](https://www.reddit.com/r/Myfitnesspal/comments/19fhv7g/do_you_think_they_will_ever_clean_up_the_database/)
10. [Food correction requests](https://www.reddit.com/r/Myfitnesspal/comments/1tgn317/food_corrections/)
11. [Duplicate saved meals](https://www.reddit.com/r/Myfitnesspal/comments/15xxxso/foods_in_my_meals_are_duplicating_on_their_own/)
12. [Fitbit sync incident](https://www.reddit.com/r/Myfitnesspal/comments/1jiw2au/known_issue_connecting_and_syncing_with_fitbit/)
13. [Google Health duplicate foods](https://www.reddit.com/r/Myfitnesspal/comments/1tz83s6/duplicate_foods_synced_from_myfitnesspal/)
14. [Garmin and switching friction](https://www.reddit.com/r/Myfitnesspal/comments/1sw9mzt/syncing_with_garmin/)
15. [Feature suggestions and ideas](https://community.myfitnesspal.com/en/categories/feature-suggestions-and-ideas)

### Official and App Store sources

- [MacroFactor official features](https://macrofactor.com/macrofactor/)
- [MacroFactor App Store](https://apps.apple.com/us/app/macrofactor-macro-tracker/id1553503471)
- [Lifesum official features](https://lifesum.com/features/)
- [Lifesum current feature updates](https://help.lifesum.com/en/article/what-is-new-these-are-the-latest-additions-to-our-app-1vy6mk1/)
- [Lifesum App Store reviews](https://apps.apple.com/us/app/lifesum-ai-calorie-counter/id286906691?see-all=reviews)
- [MyFitnessPal official product page](https://www.myfitnesspal.com/)
- [MyFitnessPal premium features](https://support.myfitnesspal.com/hc/en-us/articles/360032625951-What-are-the-features-of-MyFitnessPal-Premium)
- [MyFitnessPal 2026 Today-tab explanation](https://support.myfitnesspal.com/hc/en-us/articles/39985611667341-Introducing-the-brand-new-Today-tab)
- [MyFitnessPal App Store](https://apps.apple.com/us/app/myfitnesspal-calorie-counter/id341232718)