Health & fitness · US iPhone listing

ASO Audit: AllTrails

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

7/10Good. The product proof earns it.

AllTrails spends its best screenshot on a number and some branded lines. The next two frames finally show why someone might care: difficulty, duration and elevation. Lead with the useful trail decision. The catalogue can stop doing the opening speech.

ASO Audit: AllTrails illustration: A paper trail map becomes a mountainous hiking landscape.
Gabriel Machuret in an ASO Guru T-shirt: approving the idea while flagging a detail.

Gab’s verdict · 7/10Gabriel Machuret

Editorial illustrationHalf a million trails. One empty opening frame.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 · 27/30 characters

AllTrails: Hike, Bike & Run

Observed subtitle · 30/30 characters

GPS Hiking & Biking Trail Maps

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

Why this gets 7/10

The trail details are useful: difficulty, duration and elevation help somebody make a real decision. Keep them prominent. The catalogue count can introduce the range without taking over the entire sales pitch. The count-led opener still wastes the chance to show a convincing hike, and the download button leaves readiness implicit. Build the opening around choosing one suitable route, inspecting its demands and checking preparation features. A large catalogue is supporting evidence, not the whole proposition.

  1. Reason to care

    1/2

    The trail catalogue communicates choice for people seeking a hike. It needs a concrete route example to turn that breadth into a stronger benefit.

  2. Product evidence

    2/2

    Trail difficulty, duration and elevation provide useful product evidence.

  3. Readable at a glance

    2/2

    Headlines and contrast are strong, with readable selective trail detail.

  4. A useful sequence

    1/2

    Discovery moves to evaluation, but the opening and download payoff remain disconnected.

  5. A reason to choose

    1/2

    The combination of route detail and preparation cues gives a tangible reason to investigate the product, although the count alone is not enough.

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 number gets the view

Look at the original: The opening uses a scale statement and brand artwork without a map or route interface.

Why I’m flagging it: The opening gives no trail or app experience to inspect.

Brief this change

Use a real trail hero with readable difficulty and duration; keep the sourced count secondary.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Discovery needs a sharper decision

Look at the original: The card displays a trail name, rating, difficulty, distance and estimated duration.

Why I’m flagging it: The card contains useful facts but the headline stays inspirational.

Brief this change

Enlarge the filters or trail attributes that help the chosen audience shortlist a route.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Download is not ready-to-go proof

Look at the original: The interface presents route characteristics and a download action under a before-going proposition.

Why I’m flagging it: The control is visible but no completion state or access context is explained.

Brief this change

Show the preparation or completed-download state with accurate entitlement context.

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

AllTrails: Hike, Bike & Run

GPS Hiking & Biking Trail Maps

Proposed alternative

AllTrails: Hike, Bike & Run

Find trails. Plan your route.

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

Keep the existing activity-rich name and shift the subtitle toward the discovery and planning actions shown in the creative. It avoids making an unqualified offline or navigation-reliability promise.

The tradeoff: The alternative removes explicit GPS, hiking, biking and trail-map wording from the subtitle, although activities remain in the name. Actual query relevance must justify that trade; descriptive planning copy is not automatically a stronger search choice.

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

  1. 01Make the benefit clear

    Proposed headline

    See the route before you choose

    Illustrative layout · verify the real flow

    Put this in the frame: A current representative trail detail with distance, elevation, route type and clearly labelled estimated time.

    Why it earns the space: Lead with a concrete decision instead of catalogue scale alone.

  2. 02Show useful evidence

    Proposed headline

    Check the latest available details

    Illustrative layout · verify the real flow

    Put this in the frame: The trail-information and recent-report view, with dates and source context retained.

    Why it earns the space: Help users distinguish published route information from current conditions without promising either is complete.

  3. 03Move the decision forward

    Proposed headline

    Prepare the map before you go

    Illustrative layout · verify the real flow

    Put this in the frame: The verified download-complete and reopening state with accurate feature and plan context.

    Why it earns the space: Explain preparation as a user action, not a guarantee of safety or uninterrupted navigation.

The test: Does a route-detail opening improve planning comprehension and qualified acquisition compared with catalogue scale? 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

komoot - hike, bike & run ↗

Your all-in-one route planner

komoot names hiking, biking and running with an all-in-one route-planner subtitle.

The lesson: The activities overlap directly. Show how someone judges a route rather than relying on the same broad activity list.

Observed competitor metadata

Gaia GPS: Mobile Trail Maps ↗

Hiking, Overlanding, Camping

Gaia GPS names mobile trail maps alongside hiking, overlanding and camping.

The lesson: The observed promise is more map-focused and includes adjacent uses. Explain AllTrails’ discovery-to-detail journey without assuming identical map layers or offline scope.

Observed competitor metadata

onX Backcountry: 3D Trail Maps ↗

Offline Hiking & Biking GPS

onX Backcountry names 3D trail maps with offline hiking and biking GPS.

The lesson: Offline intent is explicit in its current metadata. AllTrails should verify and explain its own access and preparation requirements instead of borrowing the claim without context.

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.

hiking trails / trails near me

Visitor’s job: Find a route in a location and decide whether to investigate it.

Evidence: The name and discovery screen identify hiking and include a Nearby filter.

Decision: Keep location-based discovery intent explicit without claiming every path or access point is covered.

trail maps / route details

Visitor’s job: Understand distance, elevation and route shape before going.

Evidence: The subtitle names trail maps and the third still displays those attributes.

Decision: Use route-planning language with accurate estimates; a listing rating is not a safety assessment.

offline hiking maps

Visitor’s job: Prepare needed map information before losing connectivity.

Evidence: The creative shows a Download action, but not a completed download or entitlement.

Decision: Verify current functionality and access before targeting this intent more strongly. Do not infer guaranteed operation or all-layer availability from the button.

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 2020–2026 accounts were selected for difficulty interpretation, offline preparation and finding a trailhead. They are a purposeful sample, not a reliability or safety estimate. The later developer-contact account is preserved. A Watch-focused account was not used to infer current iPhone behaviour, and old plan names do not establish today’s entitlements.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 24 June 2020–31 August 2026. No sentiment percentage is calculated.

24 June 2020 · 5/5 stars

“trail conditions”

A June 2020 reviewer valued other hikers’ reports and recording, while finding difficulty labels inconsistent with their own experience.

What I’d investigate: Research how people interpret difficulty and dated reports. Individual experience does not establish a universally correct difficulty scale or current offline feature set.

Listing review source · Review ID 6116364991

31 August 2026 · 4/5 stars

“download the map”

An August 2026 reviewer praised discovery but reported intermittent access to previously downloaded maps, requested offline heat maps and disputed weather information.

What I’d investigate: Investigate access states and feature scope with reproducible cases. These are unresolved reports, not confirmed current causes, universal weather errors or proof of unsafe operation.

Listing review source · Review ID 14494566835

18 September 2024 · 2/5 stars

“several months later”

A September 2024 account described trailhead confusion and difficulty reaching support, then said contact about speaking with a developer eventually arrived months later.

What I’d investigate: Retain the eventual contact. Check current trailhead and support flows without claiming the reported route error or support delay represents every user.

Listing review source · Review ID 11737756463

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 number gets the view

The opening gives no trail or app experience to inspect.

Deliverable: Use a real trail hero with readable difficulty and duration; keep the sourced count secondary.

Creative brief and current-product check
02

Discovery needs a sharper decision

The card contains useful facts but the headline stays inspirational.

Deliverable: Enlarge the filters or trail attributes that help the chosen audience shortlist a route.

Creative brief and current-product check
03

Download is not ready-to-go proof

The control is visible but no completion state or access context is explained.

Deliverable: Show the supported preparation or completed-download state with accurate entitlement context.

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

One test worth running

Does a route-detail opening improve planning comprehension and qualified acquisition compared with catalogue scale?

Audience
Eligible US English iPhone default-page visitors, with separate research among casual local walkers and people planning trips with limited connectivity.
Control
The captured first three stills with the catalogue-scale claim verified before reuse.
Treatment
Replace only the first frame with a new detail-led concept using a verified route and readable distance, elevation and estimated duration. Keep later frames, metadata and offers fixed.
Method
Validate example route data and label its scope, then run comprehension research and eligible randomized App Store product page optimization. This tests store communication, not navigation reliability or outdoor safety.
Primary measure
Platform-reported download conversion for eligible randomized traffic.
Guardrails
Participants should distinguish estimated time, difficulty, current conditions and offline access. Do not accept increased expectations of guaranteed coverage, safe passage or automatic downloads; measure preparation understanding separately.
Decision rule
Predefine useful effect, sample size and analysis timing from baseline traffic. Retain control if inconclusive or if the new opening produces more mistaken route-suitability or connectivity expectations.
What could muddy the result
Weather, season, local trail closures, featured destinations, subscription changes and the mix of casual versus remote-trip users may affect results.

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/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/10AllTrails is here

    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. Use a real trail hero with readable difficulty and duration; keep the sourced count secondary.
  2. Enlarge the filters or trail attributes that help the chosen audience shortlist a route.
  3. Show the supported preparation or completed-download state with accurate entitlement context.

What would change my mind?

  • Current route-data provenance, condition timestamps and estimate definitions.
  • Verified download, entitlement and offline feature behaviour.
  • Conversion baseline and planning-intent research by visitor segment.
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 AllTrails. 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.