Travel · US iPhone listing

ASO Audit: Google Maps

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

7/10Good. The product proof earns it.

Google Maps actually shows what the visitor can do, which earns credit. Its weakest headline is the broad ask-anything claim. The airport deadline example underneath is far more useful than that invitation to vagueness.

ASO Audit: Google Maps illustration: Roads connect city navigation, mountain travel and an airport.
Gabriel Machuret in an ASO Guru T-shirt: approving a useful product demonstration.

Gab’s verdict · 7/10Gabriel Machuret

Editorial illustrationUseful navigation proof. The new feature needs a real headline.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 · 11/30 characters

Google Maps

Observed subtitle · 28/30 characters

Places, navigation & traffic

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

Why this gets 7/10

The route and transport comparison help somebody make an actual decision. That earns a good score. Improve the small detail and broad conversational headline without pretending the useful proof is missing. Tighten the question-and-answer headline, enlarge relevant detail and use one continuous journey. The opportunity is sharper communication, not inventing faults because the brand is large. Sample estimates remain examples, not guaranteed arrivals.

  1. Reason to care

    2/2

    A next-turn benefit gives the opener an immediate job.

  2. Product evidence

    2/2

    Routes and a task-specific transport comparison provide substantial proof.

  3. Readable at a glance

    1/2

    Small route and response text needs selective enlargement.

  4. A useful sequence

    1/2

    Navigation, questioning and traffic connect but change scenarios.

  5. A reason to choose

    1/2

    Multiple decision inputs are useful without proving universal accuracy.

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

Keep the immediate navigation benefit

Look at the original: The active navigation interface supplies an immediate next step.

Why I’m flagging it: The useful next-turn view contains small competing map details.

Brief this change

Enlarge the key instruction and retain enough authentic route context.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Anything is weaker than this example

Look at the original: A conversational request is tied to a destination, arrival deadline and transport comparison.

Why I’m flagging it: A broad headline undersells a specific deadline-and-transport question.

Brief this change

Lead with that task and make the comparison readable.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The journey changes again

Look at the original: Traffic context appears directly on the navigation map.

Why I’m flagging it: Traffic proof does not continue the airport example.

Brief this change

Use one verified sample route and show its incident or alternative decision.

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

Google Maps

Places, navigation & traffic

Proposed alternative

Google Maps

Plan trips. Find your route.

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

Retain the brand and connect planning with navigation using two concrete jobs shown in the sequence. The proposal avoids guaranteed timing and does not imply that a conversational answer is always correct.

The tradeoff: The current subtitle explicitly includes places, navigation and traffic. This alternative loses the place-discovery term and traffic wording, which may be valuable intentions; test that tradeoff before narrowing the default page.

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

  1. 01Make the benefit clear

    Proposed headline

    Choose where you need to go

    Illustrative layout · verify the real flow

    Put this in the frame: A verified destination and route-planning view with realistic example inputs.

    Why it earns the space: Start with the destination decision and maintain accurate mode and region context.

  2. 02Show useful evidence

    Proposed headline

    Ask about the trip you are planning

    Illustrative layout · verify the real flow

    Put this in the frame: The checked airport scenario with a specific headline and truthful feature access.

    Why it earns the space: Explain the new interaction through one useful question rather than an unlimited promise.

  3. 03Move the decision forward

    Proposed headline

    Review changing traffic conditions

    Illustrative layout · verify the real flow

    Put this in the frame: A current navigation example with clearly illustrative timing and route information.

    Why it earns the space: Show decision support without presenting estimates as guaranteed outcomes.

The test: Does a trip-planning headline on the second frame improve conversion compared with the current broad conversational headline? 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

Waze Navigation & Live Traffic ↗

Avoid traffic, police, hazards

Waze explicitly names navigation, live traffic and road-related alerts.

The lesson: Driving intentions overlap strongly. Compare the clarity of the route-planning story, not unsupported accuracy or speed superiority.

Observed competitor metadata

Apple Maps ↗

Navigate and explore the world

Apple Maps positions navigation and exploring the world.

The lesson: It also spans directions and discovery. Google Maps can explain a particular planning interaction rather than relying only on category breadth.

Observed competitor metadata

Citymapper: All Live Transit ↗

Live Bus, Subway, Train Times

Citymapper foregrounds live transit with bus, subway and train times.

The lesson: Transit users have different decisions from drivers. Do not generalise a driving-led test to every transport mode.

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.

maps / driving directions

Visitor’s job: Reach a destination with turn-by-turn guidance.

Evidence: The opening shows a driving route and next-turn instruction.

Decision: Research destination and mode needs without claiming a current ranking or universal route accuracy.

trip planning / airport directions

Visitor’s job: Compare how and when to leave for a destination.

Evidence: The second frame presents an airport deadline and multiple transport options.

Decision: Verify the conversational feature’s current coverage; avoid implying it answers every travel question in every region.

traffic updates / route alternatives

Visitor’s job: Understand changing road conditions before or during a journey.

Evidence: The third frame shows alternatives and a delay marker.

Decision: Treat speed and arrival times as estimates, and separate driver intent from transit and local discovery.

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

Only the three app-related accounts in the eight displayed reviews were selected. Five others primarily described experiences with local businesses or services and were excluded from app analysis. Two selected accounts date to 2019; none establishes current route accuracy or cross-platform feature parity.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 28 May 2019–10 February 2026. No sentiment percentage is calculated.

10 February 2026 · 5/5 stars

“Apple CarPlay”

A February 2026 reviewer requested changes to speed display and location sharing in a vehicle context.

What I’d investigate: Verify current availability and safe interaction design independently; do not recommend the reviewer’s workaround or treat requested features as established gaps.

Listing review source · Review ID 13734181960

28 May 2019 · 5/5 stars

“places I want to visit”

A May 2019 reviewer described saving places, planning stops and contributing information.

What I’d investigate: Use these as historical motivations, not a current capability inventory or evidence for the reviewer’s absolute reliability claim.

Listing review source · Review ID 4226009885

21 November 2019 · 5/5 stars

“text was a little bit smaller”

A November 2019 reviewer compared navigation interfaces and raised readability concerns.

What I’d investigate: Check present map readability with current devices. The old platform comparisons and accuracy opinions are not current product facts.

Listing review source · Review ID 5178142107

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

Keep the immediate navigation benefit

The useful next-turn view contains small competing map details.

Deliverable: Enlarge the key instruction and retain enough authentic route context.

Creative brief and current-product check
02

Anything is weaker than this example

A broad headline undersells a specific deadline-and-transport question.

Deliverable: Lead with that supported task and make the comparison readable.

Creative brief and current-product check
03

The journey changes again

Traffic proof does not continue the airport example.

Deliverable: Use one verified sample route and show its supported incident or alternative decision.

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

One test worth running

Does a trip-planning headline on the second frame improve conversion compared with the current broad conversational headline?

Audience
Eligible US English iPhone default-page visitors; interpret results alongside driving, transit and local-discovery acquisition mix.
Control
The current second-frame headline and airport-planning interface.
Treatment
Change only the headline to approved trip-planning wording; keep the question, map, other screenshots and metadata fixed.
Method
Verify current feature access and scenario accuracy, run stationary comprehension research, then use eligible App Store product page optimization for the text change.
Primary measure
Platform-reported download conversion within eligible randomized traffic.
Guardrails
Check separately that people do not expect infallible answers, guaranteed arrival times or universal geographic coverage; conduct no research interaction while participants drive.
Decision rule
Set the useful effect and sample plan from actual traffic. Retain control if inconclusive; conversion does not establish navigation accuracy, trip safety or completed journeys.
What could muddy the result
Travel demand, geography, feature rollout, traffic conditions and transport-mode campaigns can shift the audience and applicability of the result.

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/10Google Maps 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. Enlarge the key instruction and retain enough authentic route context.
  2. Lead with that supported task and make the comparison readable.
  3. Use one verified sample route and show its supported incident or alternative decision.

What would change my mind?

  • Current conversational feature coverage and supported mobile workflow.
  • Driving, transit and local-discovery visitor mix.
  • Conversion baseline and recent stationary comprehension and readability 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 Google Maps. 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.