Travel · US iPhone listing

ASO Audit: Hopper

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

5/10Fine. A dangerous place to stop.

Hopper's best-way opener could belong to practically any travel app. The useful difference is the calendar and forecast. Those should lead, with the uncertainty as readable as the possible saving.

ASO Audit: Hopper illustration: Travel dates and destinations unfold from a suitcase.
Gabriel Machuret in an ASO Guru T-shirt: questioning the vague promise.

Gab’s verdict · 5/10Gabriel Machuret

Editorial illustrationBest way to book travel is not an explanation.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 · 30/30 characters

Hopper: Flights, Hotels & Cars

Observed subtitle · 26/30 characters

Spend Less, Travel Better.

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

Why this gets 5/10

The calendar and forecast are practical tools for a travel decision. Keep them. The broad best-way claim is less persuasive than showing how someone uses that information without assuming a guaranteed saving. Replace the generic opener with a specific date decision, enlarge the calendar and explain what watching a trip does. Keep forecast uncertainty visible. Potential savings should not become a confident outcome through larger typography.

  1. Reason to care

    1/2

    The travel context and date-choice tools make the booking purpose identifiable, although the superlative does not explain a specific advantage.

  2. Product evidence

    1/2

    Calendar and forecast appear without a completed decision.

  3. Readable at a glance

    1/2

    Small type and miniature phones weaken useful detail.

  4. A useful sequence

    1/2

    Booking, dates and forecasts connect only loosely.

  5. A reason to choose

    1/2

    Prediction is specific, but uncertainty needs stronger visual treatment.

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 superlative wastes the opener

Look at the original: The frame combines booking categories with promotional discount artwork and a destination example.

Why I’m flagging it: Categories and offers support a claim rather than a distinctive benefit.

Brief this change

Lead with a travel-date decision and a readable example.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The useful comparison is tiny

Look at the original: Dates are grouped into four colour bands with example dollar values.

Why I’m flagging it: The colour legend and prices are small inside a full phone.

Brief this change

Enlarge the relevant date comparison with clearly labelled sample amounts.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Could needs equal billing

Look at the original: The visible interface uses likely and could, including an illustrative possible saving per ticket.

Why I’m flagging it: Forecast uncertainty is less prominent than the possible saving.

Brief this change

Show the watch action and keep conditional forecast wording legible.

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

Hopper: Flights, Hotels & Cars

Spend Less, Travel Better.

Proposed alternative

Hopper: Flights, Hotels & Cars

Compare dates. Watch prices.

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

Keep the current category-rich name and replace the broad Spend Less, Travel Better promise with two visible actions. The wording describes a decision process without guaranteeing the lowest fare.

The tradeoff: It reduces the aspirational benefit and may feel flight-heavy to hotel or car shoppers. Verify exactly which products support the watch action before a metadata release.

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

  1. 01Make the benefit clear

    Proposed headline

    Compare dates for your trip

    Illustrative layout · verify the real flow

    Put this in the frame: A verified route and date calendar with an accurately labelled sample fare basis.

    Why it earns the space: Make the first useful comparison visible.

  2. 02Show useful evidence

    Proposed headline

    Understand the price forecast

    Illustrative layout · verify the real flow

    Put this in the frame: A current estimate with its uncertainty and conditions, using illustrative values.

    Why it earns the space: Explain the forecast before asking a traveller to delay buying.

  3. 03Move the decision forward

    Proposed headline

    Watch the trip you choose

    Illustrative layout · verify the real flow

    Put this in the frame: The actual watch flow and an accurate example notification.

    Why it earns the space: Turn a prediction into a clear action without promising a cheaper future ticket.

The test: Does explicit forecast uncertainty improve understanding while preserving qualified download conversion? 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

Skyscanner Flights & Travel ↗

Cheap Flight Tickets & Booking

Skyscanner foregrounds flights and travel with cheap tickets and booking.

The lesson: Low-price intent is shared. Explain Hopper’s actual date and watch workflow instead of inferring a pricing advantage from category language.

Observed competitor metadata

KAYAK: Flights, Hotels & Cars ↗

Plan vacations & book trips

KAYAK names flights, hotels and cars with planning and booking.

The lesson: The same category breadth appears in Hopper’s name. Specific decision support is a more useful creative distinction than another list of booking types.

Observed competitor metadata

Expedia: Hotels, Flights, Cars ↗

Trip planner & travel deals

Expedia names hotels, flights and cars with a trip-planner proposition.

The lesson: Planning is adjacent intent, but a forecast has a different job from a complete itinerary. Show when and how the user should act.

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.

flight price tracker / price alerts

Visitor’s job: Follow a route while deciding when to book.

Evidence: The third screenshot shows a watch action and a price forecast.

Decision: Verify alert scope and eligibility, then research this task as a specific proposition without implying guaranteed savings.

cheap flight dates / flexible travel dates

Visitor’s job: Compare possible departure dates and costs.

Evidence: The second screenshot uses a calendar and a price legend.

Decision: Clarify the fare and route basis before testing comparison-led language; no keyword-volume estimate is available.

hotels flights cars / travel booking

Visitor’s job: Find and book different parts of a trip.

Evidence: All three categories appear in the observed name and opening interface.

Decision: Retain broad booking relevance while testing the narrower forecast message independently.

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 accounts from 2022–2024 were selected for booking details, forecast interpretation and itinerary constraints. They include praise and criticism but do not provide a representative sample or forecast-accuracy rate. Historical filters, prices and the reviewer’s theory of colour coding require independent verification.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 20 February 2022–22 April 2024. No sentiment percentage is calculated.

10 February 2023 · 5/5 stars

“reading the details”

A February 2023 reviewer praised hotel and rental usefulness but described selecting a different room type than intended.

What I’d investigate: Use this as a booking-detail comprehension lead. Personal price comparisons and suggested booking times are not general savings evidence.

Listing review source · Review ID 9601950524

22 April 2024 · 4/5 stars

“not accurate”

An April 2024 reviewer valued time savings while describing a forecast disappointment and uncertainty about calendar colours.

What I’d investigate: Verify the current legend and forecast scope. The reviewer explicitly speculates about the algorithm; that explanation is not adopted as fact.

Listing review source · Review ID 11189319346

20 February 2022 · 4/5 stars

“total flight duration”

A February 2022 reviewer wanted more control over flight duration when interpreting forecasts.

What I’d investigate: Investigate current filters and the forecast’s covered itinerary set instead of claiming that the historical limitation persists.

Listing review source · Review ID 8374954267

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 superlative wastes the opener

Categories and offers support a claim rather than a distinctive benefit.

Deliverable: Lead with a supported travel-date decision and a readable example.

Creative brief and current-product check
02

The useful comparison is tiny

The colour legend and prices are small inside a full phone.

Deliverable: Enlarge the relevant date comparison with clearly labelled sample amounts.

Creative brief and current-product check
03

Could needs equal billing

Forecast uncertainty is less prominent than the possible saving.

Deliverable: Show the supported watch action and keep conditional forecast wording legible.

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

One test worth running

Does explicit forecast uncertainty improve understanding while preserving qualified download conversion?

Audience
Eligible US English iPhone default-page visitors; separately recruit flexible-date travellers and fixed-itinerary travellers for research.
Control
The existing third-frame support copy only if a claims review confirms it is accurate; correct any unsupported claim across variants first and establish a fresh baseline.
Treatment
Change only the third-frame supporting line to verified estimate-and-watch wording. Keep the conditional UI, sequence, images and metadata fixed.
Method
Validate the current forecast scope and run comprehension research, followed by eligible App Store product page optimization. Do not label this a forecast-accuracy experiment.
Primary measure
Platform-reported download conversion for eligible randomized traffic.
Guardrails
Participants should distinguish a forecast from a confirmed quote or guaranteed saving and understand whether it covers their intended itinerary. Booking savings require separate evidence.
Decision rule
Set a useful effect, sample requirement and analysis timing before launch from real baseline data. Keep control if inconclusive; reject wording that improves conversion through mistaken certainty.
What could muddy the result
Fare volatility, disruptions, promotional discounts, seasonality and changing itinerary mix can 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/10Hopper 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. Lead with a supported travel-date decision and a readable example.
  2. Enlarge the relevant date comparison with clearly labelled sample amounts.
  3. Show the supported watch action and keep conditional forecast wording legible.

What would change my mind?

  • Current forecasting methodology, qualification and supported products.
  • Calendar legend, fare basis and itinerary-filter behaviour.
  • Real conversion baseline and fresh uncertainty-comprehension 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 Hopper. 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.