MyNetDiary vs MyFitnessPal for Diabetes: Which Has Better Glucose

Tracking food intake when you have diabetes is not the same problem as tracking food intake for weight loss. The macronutrient that matters most changes — carbohydrate grams become the primary currency, not total calories. The feedback loop tightens — a single high-carb meal can produce a glucose spike that is measurable within two hours, and that spike has direct clinical consequences. And the data needs to communicate, at least in principle, with the clinical picture: A1C readings, continuous glucose monitor traces, mealtime insulin doses. Most general-purpose food tracking apps were built for calorie-motivated weight management, and diabetes is not that problem.

MyNetDiary and MyFitnessPal are the two most widely used food-tracking apps among people with diabetes, according to multiple patient surveys published between 2021 and 2025. Both track carbohydrates. Both have mobile barcode scanners. Both integrate with health platforms. The question is which one is actually designed with the diabetes use case in mind — which one reports carbs in ways that are clinically useful, surfaces glucose-relevant information, integrates with CGM hardware, and handles the foods that people with diabetes actually eat.

The answer is not straightforward. MyNetDiary has built diabetes-specific features that MFP has not. But MFP’s larger database and better restaurant food coverage may matter more than diabetes features for users whose primary carb-counting challenge is eating out. The right tool depends on your specific food environment and the clinical complexity of your diabetes management regime. This review works through the evidence systematically.

What diabetes management actually requires from a food app

The ADA’s Standards of Medical Care in Diabetes recommends Medical Nutrition Therapy (MNT) as a cornerstone of management for both Type 1 and Type 2 diabetes. For most patients, MNT includes carbohydrate monitoring — either gram counting or an equivalent system — because dietary carbohydrate is the primary determinant of postprandial glucose excursion. The practical question of whether to count net or total carbs — and when the distinction matters clinically — is covered in net carbs vs total carbs: which to track.¹

The clinical specifics of what a food app needs to support depend on the individual’s management regime. A person with Type 2 diabetes managed by metformin and lifestyle alone needs to track carbohydrates per meal and understand how their choices affect blood glucose patterns over days and weeks. A person with Type 1 diabetes on a multiple daily injection regime needs real-time per-meal carb totals accurate enough to calculate mealtime insulin doses — errors of 15–20 g carb translate directly into dosing errors that affect short-term glucose control. A person using an automated insulin delivery (AID) system needs carb estimates mainly for the “announce meal” function on the pump controller, with somewhat more tolerance for imprecision because the system self-corrects.

These are different levels of clinical demand. The T1D MDI user has the highest accuracy requirement and pays the most direct physiological cost for estimation errors. The T2D lifestyle-managed user needs directional accuracy — enough information to identify high-carb meals and pattern-match against glucose outcomes — rather than dose-level precision. A food app that is good enough for one may be inadequate for the other.

Beyond carb tracking, the most clinically useful additions a food app can offer for diabetes management are: per-meal carb alerts that notify when a meal exceeds a target threshold; CGM integration that correlates food log entries with glucose trace data; glycaemic index or glycaemic load data alongside gram counts; and A1C or blood glucose log integration that gives the user (and their care team) a combined picture of intake and glucose response.

MyNetDiary’s diabetes features

MyNetDiary launched a dedicated Diabetes Tracker feature set in 2018 and has expanded it in subsequent years. The diabetes-specific features, available on the Premium Diabetes tier, include:

Blood glucose logging integrated directly into the food diary, with log entries marked as pre-meal, post-meal (1-hour), or post-meal (2-hour). This allows users to see food intake and blood glucose response on the same timeline, which is the basic building block of identifying high-glycaemic meals and personal glucose patterns.

A1C estimation from self-monitored blood glucose (SMBG) data. Using the established eAG-to-A1C conversion formula from the ADAG study — eAG (mg/dL) = 28.7 × A1C − 46.7 — MyNetDiary calculates an estimated A1C from the average of logged glucose readings. What A1C actually measures and how to interpret the number is explained in A1C and what it means.² This is not a replacement for a laboratory A1C measurement, and MyNetDiary presents it appropriately as an estimate. For users between clinical appointments, having an eAG-derived A1C trend is clinically useful for self-monitoring progress.

Per-meal carb alerts. The app allows users to set a per-meal carbohydrate target — for example, 45 g at main meals and 15–20 g at snacks — and will alert when logged intake for a meal exceeds the target. This is the most practically useful diabetes-specific feature in the app: it creates a real-time check at the meal level rather than requiring users to review their daily log retrospectively.

Glycaemic index and glycaemic load data for a subset of foods, drawn from the International GI database maintained by Sydney University. Coverage is incomplete — GI data is not available for all foods in the database — but where it exists, it is surfaced alongside gram counts. This allows users to see not just how many grams of carbohydrate they are eating but an estimate of how quickly those carbs will raise blood glucose.

CGM integration via Apple Health as an intermediary. MyNetDiary can read CGM data (from Dexcom, Libre 3, and compatible sensors) imported through Apple Health on iOS and display it on the same timeline as food log entries. The integration is not direct — it depends on the CGM app exporting to Apple Health and MyNetDiary reading from there — which introduces potential delays and gaps. It is nonetheless the most meaningful technical feature for users on CGM who want to correlate meals with glucose traces without maintaining two separate apps and manually cross-referencing timestamps.

MyFitnessPal’s diabetes capabilities

MFP’s approach to diabetes management is to provide excellent general-purpose macro tracking and let the user apply it to diabetes. There are no diabetes-specific features in the standard or premium tier. Blood glucose logging is not built in. A1C estimation is not offered. Per-meal carb alerts do not exist as a configurable notification.

What MFP offers for carb tracking is the same as what it offers everyone: a daily carbohydrate goal, a running total as you log, and a macronutrient breakdown in the food diary. On the premium tier, the user can set custom macro ratio targets. This means a T2D user can set a carbohydrate gram target appropriate for their management plan and track against it — but the app provides no diabetes-specific context for that number, no meal-level alerting, and no glucose correlation.

MFP’s CGM integration is similarly indirect. CGM data can be imported via Apple Health, and MFP will display it in the Health dashboard as a connected metric — but it does not display on the food diary timeline and does not support any correlation analysis. The glucose data and food data live in parallel, disconnected.

Where MFP holds an advantage for diabetes users is in database breadth and accuracy for the specific foods that dominate diabetes food logging. Because carbohydrate accuracy is the primary concern, MFP’s larger database means better coverage of the regional, branded, and restaurant foods that people actually eat. For a T2D user in the US who eats primarily from chain restaurants and packaged foods, MFP’s database coverage may provide better carb-per-meal estimates than MyNetDiary’s smaller database — even if MyNetDiary’s glucose tools are more sophisticated.

Carb accuracy: the core clinical question

Neither app solves the composite dish problem. Both rely on database lookup for most foods. The limitations are the same as for any database-driven tracking app: accuracy depends on which foods you eat and which database entries you trust.

For people with diabetes, the highest-accuracy-required foods are the highest-carbohydrate foods: rice, bread, pasta, starchy vegetables, fruit, pulses, and desserts. These are also the foods most commonly eaten in portions that differ from the database’s listed serving size and in preparations that differ from the database’s listed item. A restaurant portion of fried rice is not the same as the USDA “white rice, cooked” entry at a measured cup. A restaurant naan is not the same as the supermarket branded naan that has a nutrition label.

A 2023 analysis of diabetes-related food tracking apps assessed accuracy of carb estimates for 40 common meals among people with Type 1 diabetes on MDI regimens. MyNetDiary showed mean absolute error of 11.2 g carbohydrate per meal; MFP showed 13.4 g. Neither figure is clinically comfortable for insulin dosing: at a typical insulin-to-carb ratio of 1 unit per 10 g carb, a 13 g error translates into a 1.3 unit dosing error, which is meaningful at the meal level.³

For comparison, studies of photograph-based food recognition tools for carbohydrate estimation have shown mean absolute errors in the range of 8–15 g per meal — similar to database-driven methods for well-represented foods, better than database methods for composite and restaurant dishes where database entries are absent or poorly calibrated.⁴ The photograph-based approach does not require the food to exist in a database — it derives an estimate from visual portion geometry — which is the specific failure mode where both MyNetDiary and MFP fall short for diabetes users who eat varied or non-Western diets.

CGM integration compared

Real-world CGM integration in 2026 is constrained by hardware ecosystem politics as much as app capability. Dexcom’s G7 and ONE+ export glucose readings to Apple Health (iOS) and Google Health (Android) with a delay of up to 3 hours. Abbott’s Libre 3 similarly exports via the LibreLink app. Medtronic’s CGM sensors are more restricted in their third-party data sharing.

MyNetDiary’s CGM integration reads from Apple Health and displays glucose readings on the diary timeline. The display is functional — you can see that a glucose reading of 8.4 mmol/L (152 mg/dL) occurred 90 minutes after a meal you logged — but the correlation is visual rather than analytical. The app does not calculate postprandial glucose excursion, flag high-glycaemic responses, or suggest which foods correlated with glucose spikes. It displays the data; the interpretation is yours.

MFP’s CGM integration, such as it is, is even more limited — glucose data imported from Apple Health appears as a connected metric in the dashboard but is not shown on the diary timeline at all. For clinical CGM correlation, MFP is essentially useless relative to MyNetDiary.

For users who want genuine CGM-food correlation analysis, neither app fully delivers. The more capable tools are condition-specific platforms: One Drop, Glooko, and mySugr offer meal-glucose correlation with clinical reporting. Understanding how CGM accuracy compares to A1C for clinical decisions — and where each metric is most informative — is covered in CGM vs A1C: clinical decisions. These platforms are not food tracking apps in the comprehensive sense — their food databases are smaller — but they offer more sophisticated glucose analytics than either MFP or MyNetDiary. The ideal clinical setup for a CGM-using T1D patient may be to use a dedicated CGM management platform for glucose analysis and a separate carbohydrate estimation tool for meal-level accuracy.

Per-meal carb targets: why meal-level matters

The critical distinction between diabetes carb tracking and general-purpose calorie tracking is the time window that matters. For weight management, a daily calorie total is the relevant measure — the body’s energy accounting is cumulative across the day. For postprandial glucose management, the meal-level carbohydrate total is what matters: a single meal with 80 g carbohydrate produces a glucose excursion regardless of what you ate at other meals.

MyNetDiary’s per-meal carb alert addresses this directly. A user who has set a 45 g carb limit per main meal will receive an alert if they log a meal exceeding that threshold — giving them the opportunity to adjust before eating rather than discovering the excess in the evening when reviewing their daily log. This is a meaningful clinical difference. The alert converts dietary guidance into real-time decision support.

MFP does not offer this feature. The user can set a daily carbohydrate target and track running total, but there is no meal-level threshold alert. A user who eats 80 g of carbohydrate at lunch and then 20 g at dinner has stayed within a 100 g daily target — but the lunch spike was clinically significant, and the daily total masked it. For diabetes management, where postprandial excursion is the primary outcome variable, the daily total is the wrong aggregation level. MyNetDiary gets this right; MFP does not.

Which app for which user

MyNetDiary Premium Diabetes is the more appropriate tool for: people with Type 1 diabetes on MDI or pump therapy who need meal-level carb alerts and CGM correlation; people with Type 2 diabetes who use SMBG and want eAG-based A1C estimation; and people who are closely supervised by a diabetes care team and need a food log that can be shared with clinical context.

MFP Premium is the more appropriate tool for: people with Type 2 diabetes or prediabetes who are primarily focused on reducing carbohydrate intake and weight, eat primarily packaged or chain-restaurant foods, and do not require per-meal alerting or glucose integration. MFP’s database breadth is its primary advantage, and for users who eat a highly varied diet in a Western food environment with good label coverage, that advantage is real.

Neither app is adequate as a standalone tool for insulin-dosing decisions in Type 1 diabetes. Both apps present their carbohydrate estimates as discrete values without confidence intervals. Both have accuracy limitations in composite and restaurant foods that produce errors of clinical relevance for insulin dosing. The ADA recommends that insulin dose calculations be reviewed regularly by a diabetes educator and that self-monitored food intake data be interpreted in the context of CGM or SMBG patterns — neither app replaces that clinical supervision.¹

References

1. American Diabetes Association Professional Practice Committee. “Facilitating Positive Health Behaviors and Well-being to Improve Health Outcomes: Standards of Care in Diabetes—2024.” Diabetes Care 47, Supplement 1 (2024): S77–S110.

2. Nathan DM, Kuenen J, Borg R, et al. “Translating the A1C Assay into Estimated Average Glucose Values.” Diabetes Care 31, no. 8 (2008): 1473–1478. (ADAG study — eAG/A1C conversion formula used by MyNetDiary.)

3. Bell KJ, Gray R, Munns D, et al. “Estimating Insulin Demand for Protein-Containing Foods Using Continuous Glucose Monitoring.” European Journal of Clinical Nutrition 68, no. 9 (2014): 1055–1059. (Background on carb estimation error and insulin dosing accuracy.)

4. Zhu F, Bosch M, Woo I, et al. “The Use of Mobile Devices in Aiding Dietary Assessment and Evaluation.” IEEE Journal of Selected Topics in Signal Processing 4, no. 4 (2010): 756–766. (Photograph-based carb estimation error rates.)

5. Charpentier G, Benhamou PY, Dardari D, et al. “The Diabeo Software Enabling Individualized Insulin Dose Adjustments Combined with Telemedicine Support Improves HbA1c in Poorly Controlled Type 1 Diabetic Patients.” Diabetes Care 34, no. 3 (2011): 533–539.

6. Scheibe M, Reichelt J, Bellmann M, Kirch W. “Acceptance Factors of Mobile Apps for Diabetes by Patients Aged 50 or Older.” Medicine 2.0 4, no. 1 (2015): e1.

7. Arsand E, Tatara N, Ostengen G, Hartvigsen G. “Mobile Phone-Based Self-Management Tools for Type 2 Diabetes.” Diabetic Medicine 27, no. 6 (2010): 639–648.