Travel · US iPhone listing

ASO Audit: Wanderlog

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

6/10Useful. Still leaving too much unsaid.

Wanderlog has useful planning machinery and demonstrates it with a geographical identity crisis. Miami, notes from somewhere else, then Oahu. The visitor has to assemble the itinerary and the sales argument at the same time.

ASO Audit: Wanderlog illustration: An open suitcase holds maps, itinerary cards and travel memories.
Gabriel Machuret in an ASO Guru T-shirt: questioning a disconnected screenshot story.

Gab’s verdict · 6/10Gabriel Machuret

Editorial illustrationOne travel planner. Three trips. No continuous story.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 · 26/30 characters

Wanderlog - Travel Planner

Observed subtitle · 27/30 characters

Itinerary & Road Trip Guide

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

Why this gets 6/10

The reservation, map and note detail shows useful planning substance. The app is doing more than the screenshots explain. Keep the tools; connect the examples so the visitor does less mental assembly. Dense interfaces, long captions and disconnected examples obscure the useful reservation-to-plan workflow. Use one trip across all three frames and enlarge the handoff that matters. This needs a clearer creative brief, not another generic promise to simplify travel.

  1. Reason to care

    1/2

    Simplified itinerary planning is understandable but broad.

  2. Product evidence

    2/2

    Maps, notes and imported reservations show substantive product utility.

  3. Readable at a glance

    1/2

    Dense screens and multi-line captions dilute the key action.

  4. A useful sequence

    1/2

    Maps, notes and reservations add different planning uses. Changing trips makes the connection less clear, but does not erase the information each frame adds.

  5. A reason to choose

    1/2

    Combined planning and import tools offer a specific, partly demonstrated advantage.

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 overview is doing every job

Look at the original: The overview brings locations and travel records into one surface.

Why I’m flagging it: Map, reservations and attachments compete in a single small panel.

Brief this change

Enlarge one itinerary overview with a clear first planning benefit.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The trip changes underneath us

Look at the original: Notes and custom lists sit alongside restaurant information within the overview.

Why I’m flagging it: The notes do not continue the opening Miami example.

Brief this change

Use the same destination and demonstrate adding one place or note to its plan.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

Import needs a visible handoff

Look at the original: The still links two import methods to a populated reservation display.

Why I’m flagging it: Two import methods appear beside an already populated reservation.

Brief this change

Show one import method and its result within that same trip.

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

Wanderlog - Travel Planner

Itinerary & Road Trip Guide

Proposed alternative

Wanderlog - Travel Planner

Itinerary, maps & group trips

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

Keep the current recognisable title and use the subtitle to connect the itinerary and map surfaces with shared planning. The description explicitly supports group collaboration.

The tradeoff: Road-trip and guide wording leave the subtitle. The change prioritises a broader collaborative itinerary job, so query data should establish whether that tradeoff is worthwhile before any 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 Wanderlog or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Keep one trip in view

    Illustrative layout · verify the real flow

    Put this in the frame: A consistent example with map, stops and reservations.

    Why it earns the space: Establish the workspace and destination.

  2. 02Show useful evidence

    Proposed headline

    Build the day together

    Illustrative layout · verify the real flow

    Put this in the frame: Verified ordering and sharing controls for that same trip.

    Why it earns the space: Show planning as an editable task rather than a finished travel guarantee.

  3. 03Move the decision forward

    Proposed headline

    Review the reservation you import

    Illustrative layout · verify the real flow

    Put this in the frame: A import method, resulting record and actual correction or confirmation action.

    Why it earns the space: Make the automation boundary and traveller’s responsibility visible.

The test: Does a reservation-review third frame improve import expectations and qualified acquisition? 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

TripIt: Travel Planner ↗

Trip Itinerary & Alerts

TripIt names travel planning, itineraries and alerts directly.

The lesson: Wanderlog should make its editable trip workspace clear instead of assuming an imported reservation proves alert coverage.

Observed competitor metadata

Roadtrippers - Trip Planner ↗

Planner, Map, & Travel Guides

Roadtrippers centres trip planning, maps and travel guides.

The lesson: Road-trip intent overlaps; show what organising stops means in Wanderlog without inferring identical geographic coverage or route optimisation.

Observed competitor metadata

Google Maps ↗

Places, navigation & traffic

Google Maps foregrounds places, navigation and traffic.

The lesson: Wanderlog can explain the additional itinerary and reservation job while accurately describing any export relationship and access conditions.

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.

travel planner / trip itinerary

Visitor’s job: Collect dates, places and bookings into a usable plan.

Evidence: The title, first overview and third reservation screen directly support this job.

Decision: Keep this broad core and use one complete trip example.

road trip planner / route planning

Visitor’s job: Organise multiple stops and understand their order.

Evidence: The subtitle names road trips and the description describes stops, distances and optimisation.

Decision: Verify current optimiser scope; estimated times and suggested orders are not guaranteed feasible travel schedules.

group trip / shared itinerary

Visitor’s job: Let travel companions view or edit one plan.

Evidence: The first example names a trip with friends, the third has sharing controls and the description distinguishes view and edit permissions.

Decision: Verify permission and account behaviour before promising frictionless collaboration; do not confuse a shared itinerary with a confirmed booking.

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–2026 accounts were chosen for import fallback, large-trip organisation and day-level sorting. They represent different access levels and tasks. Reported stop counts are not performance benchmarks, personal ADHD references are not clinical evidence, and old compatibility complaints are not treated as current supported-format lists.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 27 April 2024–29 January 2026. No sentiment percentage is calculated.

27 April 2024 · 5/5 stars

“manually input my info”

An April 2024 traveller liked the planning and sharing workflow but said hotel email forwarding sometimes required manual entry.

What I’d investigate: Retain the positive overall experience and the specific import issue. Test current formats rather than assuming all email imports fail.

Listing review source · Review ID 11206268998

29 January 2026 · 3/5 stars

“a lot of stops”

A January 2026 free-version user valued the planner but reported slow behaviour on large trips and difficulty organising many saved trips.

What I’d investigate: The reviewer’s suggested stop threshold is not a verified capacity limit. Use varied realistic trip sizes in product research without publishing a universal cutoff.

Listing review source · Review ID 13690529568

20 March 2025 · 4/5 stars

“just the ones in that day”

A March 2025 Pro user found sorting useful for a New York trip but wanted cross-day planning and used a workaround to regroup stops.

What I’d investigate: Preserve the day-level context and overall positive assessment. Verify current optimiser scope rather than promising it solves a whole multi-day itinerary automatically.

Listing review source · Review ID 12441379503

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 overview is doing every job

Map, reservations and attachments compete in a single small panel.

Deliverable: Enlarge one itinerary overview with a clear first planning benefit.

Creative brief and current-product check
02

The trip changes underneath us

The notes do not continue the opening Miami example.

Deliverable: Use the same destination and demonstrate adding one place or note to its plan.

Creative brief and current-product check
03

Import needs a visible handoff

Two import methods appear beside an already populated reservation.

Deliverable: Show one supported import method and its result within that same trip.

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

One test worth running

Does a reservation-review third frame improve import expectations and qualified acquisition?

Audience
Eligible US English iPhone default-page visitors planning trips with confirmed flight or hotel reservations; include both solo and group planners in research.
Control
The captured overview, travel-document and import sequence after verifying access and retained claims.
Treatment
Replace only the third frame with one verified import method and its actual review or correction step. Keep the first two frames, metadata and subscription offer fixed.
Method
Test the chosen confirmation format with consented or synthetic booking data. Run comprehension research and eligible randomized App Store product page optimization once the displayed steps are verified.
Primary measure
Platform-reported download conversion for eligible randomized visitors.
Guardrails
People should understand which import method is shown, its access requirements and the need to check details. Do not imply universal parsing, live disruption alerts, a confirmed reservation or safe routing from a screenshot.
Decision rule
Predefine useful effect, sample requirement and analysis point using real baseline traffic. Retain control if inconclusive or if gains come from mistaken free-access or import-reliability expectations.
What could muddy the result
Travel season, destination mix, Gmail-permission changes, subscription promotions and importer updates 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/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/10Wanderlog is here

    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. Enlarge one itinerary overview with a clear first planning benefit.
  2. Use the same destination and demonstrate adding one place or note to its plan.
  3. Show one supported import method and its result within that same trip.

What would change my mind?

  • Current import formats, edit controls and integration entitlements.
  • Optimiser scope, offline scope and large-trip performance on supported devices.
  • Baseline acquisition and reservation-import comprehension.
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 Wanderlog. 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.