Health & fitness · US iPhone listing

ASO Audit: WaterMinder

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

5/10Fine. A dangerous place to stop.

WaterMinder says tracking takes a simple tap and uses a crowded device collage to explain it. Show the tap. Then show what changes. The water drop mascot cannot do the product demonstration on its own.

ASO Audit: WaterMinder illustration: Water glasses follow a daily path beside a body-shaped water vessel.
Gabriel Machuret in an ASO Guru T-shirt: squinting at unreadable details.

Gab’s verdict · 5/10Gabriel Machuret

Editorial illustrationSeveral devices. One missing tap.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
1 October 2026
Creative reviewed
First 3 still screenshots; video and other devices excluded
Observed app name · 29/30 characters

Water Tracker by WaterMinder®

Observed subtitle · 30/30 characters

Drink More, Hydration Reminder

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

Why this gets 5/10

The reminder and logging purpose is understandable. A simple utility can sell a simple benefit. The overlapping devices and mixed units make the demonstration busier than the job itself. Use one consistent amount and unit from reminder through logging to history. Enlarge the useful controls and reduce device overlap. More hardware does not automatically make the benefit more persuasive.

  1. Reason to care

    1/2

    Reminder utility is clear but the motivation is generic.

  2. Product evidence

    1/2

    Notifications and totals appear without one logging action.

  3. Readable at a glance

    1/2

    Overlapping devices and mixed units create unnecessary density.

  4. A useful sequence

    1/2

    Reminder-to-history is plausible but the central tap is missing.

  5. A reason to choose

    1/2

    Watch integration is concrete but mostly presented as device artwork.

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 notification needs a response

Look at the original: Both devices display a prompt to drink water.

Why I’m flagging it: Two reminders demonstrate prompting without the next action.

Brief this change

Show one readable reminder leading into drink logging.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The simple tap gets crowded out

Look at the original: The artwork combines several device views and beverage amounts in different units.

Why I’m flagging it: Devices, silhouettes and differing amounts compete in the same frame.

Brief this change

Use one enlarged logging control and its real total update.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The history loses the original drink

Look at the original: The example reports a dated week and mixes different drink colours.

Why I’m flagging it: A weekly report does not connect to the preceding action.

Brief this change

Show the same logged example with consistent units and labelled sample values.

See how the proposed sequence fits together ↓
Figure 1. First three still screenshots from the US iPhone listing, captured 1 October 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

Water Tracker by WaterMinder®

Drink More, Hydration Reminder

Proposed alternative

WaterMinder: Water Tracker

Drink logs & gentle reminders

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

Keep the recognised brand and tracking category while describing recorded drinks and reminders rather than implying a health measurement.

The tradeoff: The proposal removes the drink-more wording and explicit hydration-reminder phrase. Check qualified search relevance and comprehension separately before adoption; keep metadata stable during the screenshot experiment.

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 WaterMinder or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Set reminders that fit

    Illustrative layout · verify the real flow

    Put this in the frame: A current reminder example with accurate schedule and device context.

    Why it earns the space: Retain the immediately understandable job.

  2. 02Show useful evidence

    Proposed headline

    Log the drink you had

    Illustrative layout · verify the real flow

    Put this in the frame: One verified cup amount and drink type with the resulting recorded total against a chosen goal.

    Why it earns the space: Explain the input and output in consistent units.

  3. 03Move the decision forward

    Proposed headline

    Review your logged week

    Illustrative layout · verify the real flow

    Put this in the frame: A current chart with a defined period, clear legend and accurate goal context.

    Why it earns the space: Make history useful without promising a physical or medical outcome.

The test: Does a single drink-to-goal example improve understanding of WaterMinder’s tracking? 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

Water tracker Waterllama ↗

Hydration drink reminder - app

Waterllama combines water tracking and drink reminders.

The lesson: A playful fill metaphor is not unique; WaterMinder should make the exact logging action and meaning clear.

Observed competitor metadata

Plant Nanny Cute Water Tracker ↗

Drinking & Hydration Reminder

Plant Nanny names a cute water tracker and hydration reminders.

The lesson: WaterMinder can distinguish practical device logging without implying that either visual metaphor measures the body.

Observed competitor metadata

Daily Water - Drink Reminder ↗

Drinking Balance & Tracking

Daily Water names drinking reminders, balance and tracking.

The lesson: The basic job is shared. Show the current quick-log workflow and history interpretation rather than unsupported health superiority.

Competitor comparison. US listing names and subtitles captured 1 October 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.

water reminder / drink reminder

Visitor’s job: Remember a user-chosen routine through notifications.

Evidence: The subtitle and first creative make reminders explicit.

Decision: Show configurable reminders and avoid universal drinking schedules or guarantees about notification delivery.

water tracker / drink log

Visitor’s job: Record an amount in familiar units and review it later.

Evidence: The second frame shows preset amounts and the third shows history.

Decision: Demonstrate one accurate entry, correction and resulting total; qualify any app-defined weighting.

Apple Watch water tracker

Visitor’s job: Record a drink from the wrist and view the result.

Evidence: The first two stills show Watch notifications and quick-add controls.

Decision: Verify app and complication refresh separately, including permissions and plan access.

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 2021–2026 accounts were selected for corrected drink-counting expectations, Watch entry and complication refresh. Conflicting personal experiences are retained without calculating prevalence. Other review claims about beverage physiology, weight loss and specific daily quantities are not used as medical evidence.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 30 August 2021–12 June 2026. No sentiment percentage is calculated.

30 August 2021 · 5/5 stars

“initially confused me”

An August 2021 reviewer initially misunderstood non-water entries in Apple Health, then described learning about drink-specific contributions; they also praised VoiceOver.

What I’d investigate: Preserve the correction while treating the explanation as a user account. Verify the present calculation and accessibility rather than adopting its physiological accuracy.

Listing review source · Review ID 7750069939

12 June 2026 · 5/5 stars

“Apple Watch”

A June 2026 returning user praised easy Watch entry and sync after resuming tracking.

What I’d investigate: Use the logging convenience as a research lead. Their personal medical circumstances do not establish clinical benefit.

Listing review source · Review ID 14173304772

25 February 2024 · 3/5 stars

“will not update”

A February 2024 reviewer distinguished an app that synced from a Watch complication that did not refresh without opening the app.

What I’d investigate: Keep the distinction and date. Recheck current behaviour without claiming either a present universal failure or that a later positive review resolves it.

Listing review source · Review ID 10979061039

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 notification needs a response

Two reminders demonstrate prompting without the next action.

Deliverable: Show one readable reminder leading into supported drink logging.

Creative brief and current-product check
02

The simple tap gets crowded out

Devices, silhouettes and differing amounts compete in the same frame.

Deliverable: Use one enlarged logging control and its real supported total update.

Creative brief and current-product check
03

The history loses the original drink

A weekly report does not connect to the preceding action.

Deliverable: Show the same logged example with consistent units and labelled sample values.

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

One test worth running

Does a single drink-to-goal example improve understanding of WaterMinder’s tracking?

Audience
US English iPhone visitors seeking drink logging or reminders, with Watch owners and non-owners analysed separately.
Control
The captured sequence after misleading measurement language is corrected consistently across variants.
Treatment
Replace only frame two with one actual drink entry and resulting logged total against a user-selected goal. Keep reminder and history frames, metadata and offer fixed.
Method
Verify units, drink contribution, correction flow and device behaviour first. Run randomized comprehension research and eligible App Store product page optimization.
Primary measure
Correct understanding of recorded intake versus the chosen goal; platform-reported download conversion in the storefront test.
Guardrails
No increase in belief that the graphic measures the body, supplies an individual medical prescription or requires everyone to drink more. Verify trial and paid access before displaying advanced features.
Decision rule
Define a useful comprehension effect and sample requirement from baseline research. Reject a variant that increases medical misunderstanding even if downloads improve; retain control if inconclusive.
What could muddy the result
Device ownership, unit preference, notification settings, trial eligibility, seasonal weather and existing tracking habits can affect response.

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/10

    Recognisable. Not convincing.

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

  5. 5/10WaterMinder is here

    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. Show one readable reminder leading into supported drink logging.
  2. Use one enlarged logging control and its real supported total update.
  3. Show the same logged example with consistent units and labelled sample values.

What would change my mind?

  • Current goal and drink-contribution calculation with approved non-medical wording.
  • Device, permission, unit and subscription access for promoted features.
  • Baseline tracking comprehension and first-log activation across device groups.
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 WaterMinder. 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.