Health & wellbeing · US iPhone listing

ASO Audit: MyFitnessPal

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

4/10Recognisable. Not convincing.

MyFitnessPal opens with a leadership claim and nutrition labels floating over lunch. The next frame adds ingredient records. Neither shows the person checking a portion or saving the entry. The effortless part is mostly implied.

ASO Audit: MyFitnessPal illustration: Separate meal components become one complete plated meal.
Gabriel Machuret in an ASO Guru T-shirt: waiting for the finished result.

Gab’s verdict · 4/10Gabriel Machuret

Editorial illustrationThe salad has numbers. The logging step is missing.See the actual listing screenshots ↓
Listing snapshot · what I checked

What I actually checked

One storefront, one language and a dated capture. This is an independent editorial audit, not a client case study.

Store & market
Apple App Store · United States
Language & device
en-US · iPhone
Captured
30 September 2026
Creative reviewed
First 3 still screenshots; video and other devices excluded
Observed app name · 29/30 characters

MyFitnessPal: Calorie Counter

Observed subtitle · 29/30 characters

AI Nutrition & Macros Tracker

Gab’s take · Five criteria. Two points each.

Why this gets 4/10

The nutrition information makes the tracking purpose understandable. Keep that clarity. The missing piece is the logging and review action, not a reason to pretend the whole listing is useless. Show one input, a readable portion check and the saved result. Keep sample data clearly labelled. A photograph surrounded by numbers is not proof of accurate or effortless tracking.

  1. Reason to care

    1/2

    Food and nutrition information establishes a relevant tracking use case. The number-one claim still distracts from a specific logging benefit.

  2. Product evidence

    1/2

    Nutrition data appears without capture, correction or saving.

  3. Readable at a glance

    1/2

    Split food imagery and small nutrient labels weaken standalone clarity.

  4. A useful sequence

    1/2

    The food and nutrient views introduce related tracking information, but the repeated output leaves the input-and-review process incomplete.

  5. A reason to choose

    0/2

    Numbers and leadership claims do not establish accuracy or ease.

0: not earned · 1: useful but incomplete · 2: clearly demonstrated. Judged on the dated opening creative; public metadata provides context. These points assess creative execution, not private conversion or ranking performance. Read the scoring criteria · See all ten verdict levels

Three things worth your attention

The screenshot teardown

Inspect the numbered original, read the problem, then compare the proposed fix. The publisher’s creative stays unchanged.

What the visitor sees → what I’d change

The salad stands in for the process

Look at the original: A food photograph carries nutrient labels beneath a category-leadership claim.

Why I’m flagging it: A category claim and nutrient labels hide the actual input.

Brief this change

Lead with a food-entry action and a specific logging benefit.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The second frame still skips checking

Look at the original: The shared composition adds food-entry cards with portions and calorie values.

Why I’m flagging it: Ingredient cards show values without a correction or save step.

Brief this change

Enlarge the portion review and adjustment controls.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The chart arrives without a logged meal

Look at the original: An actual summary interface shows how logged information can be reviewed.

Why I’m flagging it: The report does not complete the preceding example.

Brief this change

Show the same meal's saved entry and its actual summary update.

See how the proposed sequence fits together ↓
Figure 1. First three still screenshots from the US iPhone listing, captured 30 September 2026. Creative belongs to the app publisher and is reproduced for analysis. Publisher claims inside screenshots are not independently verified.

What I’d put on the table

Proposed copy for discussion. These are not current listing fields or tested winners.

Observed listing

MyFitnessPal: Calorie Counter

AI Nutrition & Macros Tracker

Proposed alternative

MyFitnessPal: Calorie Counter

Log food. Review your macros.

Name 29/30 · Subtitle 29/30 characters
Metadata comparison. A proposed alternative to review against the current listing.

Retain the familiar descriptive name and make the subtitle describe two observable tasks. This focuses on workflow rather than implying that automation removes the need to check an entry.

The tradeoff: The alternative removes explicit AI positioning and may underrepresent assisted logging for users seeking it. Validate that acquisition intent and current entitlements before deciding whether task clarity deserves the limited subtitle space.

Gab’s proposed direction

Give each screenshot a job.

Read the sequence from top to bottom on mobile, left to right on desktop. These are message-layout sketches, not screens from MyFitnessPal or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Add the food you want to log

    Illustrative layout · verify the real flow

    Put this in the frame: A verified current entry workflow, with the actual input method and access context shown.

    Why it earns the space: Explain the starting action rather than implying that a photo alone guarantees exact information.

  2. 02Show useful evidence

    Proposed headline

    Check the entry and portion

    Illustrative layout · verify the real flow

    Put this in the frame: The real review/edit controls before saving, using clearly illustrative data.

    Why it earns the space: Make the user’s checking step visible and avoid promising nutritional precision from the creative.

  3. 03Move the decision forward

    Proposed headline

    Review your recorded pattern

    Illustrative layout · verify the real flow

    Put this in the frame: The current summary corresponding to the example entries, without a promised health outcome.

    Why it earns the space: Connect the inputs to a useful record while keeping illustrative goals distinct from advice.

The test: Does an explicit input-and-review opening pair convert better than the current food-and-nutrient composition? The sketch gives the designer a direction; the actual product and access conditions decide what can ship.

Want this level of detail for your app?

Bring the listing. I’ll help you decide what to keep, what to fix and what to test.

Talk to Gabriel →
Compare three alternatives

Three alternatives—and what they make clearer

Observed competitor metadata

Lose It! – Calorie Counter ↗

Food Tracker for Weight Loss

Lose It! names calorie counting and food tracking, with a weight-loss-oriented subtitle.

The lesson: Compare the logging job without borrowing outcome promises that this public evidence cannot substantiate.

Observed competitor metadata

Cronometer: Calorie Counter ↗

Nutrition, macro, diet tracker

Cronometer pairs calorie counting with nutrition, macros and diet tracking.

The lesson: Nutrition terminology is shared across the category. The clarity of input and review can be a more useful distinction.

Observed competitor metadata

Lifesum: AI Calorie Counter ↗

Food Diary & Macro Tracker App

Lifesum includes AI calorie counting, a food diary and macro tracking in its metadata.

The lesson: An AI label does not explain accuracy, access or the user’s checking role; show those workflow details where relevant.

Competitor comparison. US listing names and subtitles captured 30 September 2026. These are positioning comparisons, not ranking or revenue comparisons.
Keyword ideas and their evidence

The keyword questions I’d investigate

Intent candidates grounded in the listing—not fabricated search-volume or difficulty scores.

food diary / calorie counter

Visitor’s job: Record food and inspect a running summary.

Evidence: The observed name and the third screenshot establish counting and nutrition reporting.

Decision: Research the user’s logging job and vocabulary without assuming a weight-loss goal for every visitor.

macro tracker / nutrition log

Visitor’s job: Review the composition of recorded meals.

Evidence: The third frame explicitly displays macro proportions and a food list.

Decision: Validate this intent against the actual product and avoid presenting sample targets as universally appropriate.

meal scan / AI food logging

Visitor’s job: Reduce manual work when recording a meal.

Evidence: The name/subtitle and food-recognition-like creative invite investigation of assisted logging.

Decision: Confirm the exact current feature, plan and review steps before making speed or accuracy claims; the stills alone do not verify the mechanism.

The unseen keyword field may already cover some of these terms. Build an evidence-backed keyword shortlist before making a metadata change.

What the selected reviews tell us

What three reviewers can teach us

Three 2024–2025 accounts were selected for repeat entry, setup effort and portion flexibility. They are positive overall but contain specific research questions. They do not establish current feature availability, nutritional accuracy, current price or health outcomes.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 17 July 2024–11 August 2025. No sentiment percentage is calculated.

16 April 2025 · 5/5 stars

“food favorites”

An April 2025 reviewer valued reusing food entries and described meal-planning features.

What I’d investigate: Investigate repeat logging and plan access. Their reported value does not verify current pricing or health effectiveness.

Listing review source · Review ID 12549620037

17 July 2024 · 5/5 stars

“a bit of work”

A July 2024 reviewer described initial setup effort becoming easier with continued use.

What I’d investigate: Test whether the listing honestly explains the input/reuse workflow; do not reuse their personal weight account as an outcome promise.

Listing review source · Review ID 11504243245

11 August 2025 · 5/5 stars

“half of a portion”

An August 2025 reviewer requested more flexible family portions in meal planning.

What I’d investigate: Verify current portion controls and separate meal planning from the core logging workflow before changing acquisition copy.

Listing review source · Review ID 13003257698

A displayed review can be old, unusually positive or internally inconsistent with its star rating. These accounts suggest questions; they do not establish current defects or typical customer experience. Use the Review Research Desk to keep evidence and interpretation separate.

What I’d do first

01

The salad stands in for the process

A category claim and nutrient labels hide the actual input.

Deliverable: Lead with a supported food-entry action and a specific logging benefit.

Creative brief and current-product check
02

The second frame still skips checking

Ingredient cards show values without a correction or save step.

Deliverable: Enlarge the supported portion review and adjustment controls.

Creative brief and current-product check
03

The chart arrives without a logged meal

The report does not complete the preceding example.

Deliverable: Show the same meal's saved entry and its actual supported summary update.

Creative brief and current-product check
Open the full test plan

One test worth running

Does an explicit input-and-review opening pair convert better than the current food-and-nutrient composition?

Audience
Eligible US English iPhone default-page visitors, without assuming a diagnosis, diet or weight goal for any individual.
Control
Current connected first-two screenshot composition, with the remaining sequence unchanged.
Treatment
Replace the pair with verified input and entry-review screens; keep the summary frame, metadata, offers and remaining creative fixed.
Method
Use eligible App Store product page optimization after product verification and comprehension research. This is a two-frame concept comparison, not an isolated test of one label or a nutritional-accuracy study.
Primary measure
Platform-reported download conversion for eligible randomized traffic.
Guardrails
Check in separate interviews whether visitors understand required review, feature access and that illustrated data are examples. Do not measure or infer health outcomes from this store test.
Decision rule
Predefine the useful effect and sample plan using actual traffic. Reject a misleading concept even if attention improves; retain control when the conversion evidence is inconclusive.
What could muddy the result
Plan changes, new assisted-entry features, seasonal fitness campaigns and shifts in logging versus meal-planning intent may affect interpretation.

Check Apple’s current product page optimization guidance and custom product page guidance before configuring a test. Write your experiment brief.

How the ten-point scale works

So, does their ASO suck?

1–3: thumbs down · 4–6: thumbs up and down · 7–10: thumbs up

  1. 1/10

    Yeah. It really does!

    The basics need a serious rethink.

  2. 2/10

    I hope no agency is getting paid for this.

    Too many obvious things have been left unfinished.

  3. 3/10

    The app deserves better.

    There is a useful product here. The listing needs to show it.

  4. 4/10MyFitnessPal is here

    Recognisable. Not convincing.

    Some basics work, but the opening wastes attention and under-explains the benefit.

  5. 5/10

    Fine. A dangerous place to stop.

    There is usable creative here, but too much of the sales argument is left to the visitor.

  6. 6/10

    Useful. Still leaving too much unsaid.

    Real strengths, undermined by meaningful gaps in the opening story or execution.

  7. 7/10

    Good. The product proof earns it.

    A clear, useful demonstration with specific refinements still needed.

  8. 8/10

    Good. Now sweat the details.

    The main promise is clear and supported. Refinement matters more than reinvention.

  9. 9/10

    Whoever did this knows their stuff.

    Clear positioning, thoughtful choices and very few loose ends.

  10. 10/10

    Okay, now you’re showing off.

    An unusually clear, convincing storefront worth learning from.

An editorial verdict on the captured storefront, not a measured ASO score or an assessment of an agency’s private work.

Try this on your app · worksheet and assignment

Your ASO assignment

  1. Lead with a supported food-entry action and a specific logging benefit.
  2. Enlarge the supported portion review and adjustment controls.
  3. Show the same meal's saved entry and its actual supported summary update.

What would change my mind?

  • Current assisted-entry, portion and plan-access verification.
  • Actual conversion baseline and logging-versus-planning acquisition mix.
  • Recent newcomer comprehension and broader review research.
Sources and capture dates

Sources and scope

No private analytics, search-rank dataset or internal keyword field was supplied. Review quotations are short excerpts; explanations are our summaries. App names and screenshots belong to their respective owners. We are not affiliated with MyFitnessPal. Read our editorial methodology.

Your app. Your priorities.

Get an audit you can actually use.

Send your listing, market and the problem you want to solve. I’ll explain the scope and fee before work starts. Your budget should buy decisions, not a longer PDF.

Apply the method to your app

Build a relevant keyword shortlist, plan your screenshot sequence or get help with the creative decisions.

More app teardowns

Browse the complete app teardown library →

Enough theory. Your app next.

Let’s fix what’s holding your listing back.

Send your app link, target market and the problem. We’ll start there.