Travel · US iPhone listing
My take: Solid. Put the pitchfork down.
Wanderlog makes a persuasive case for gathering a trip in one place. Maps, lists, notes and reservations all appear in the opening sequence. The third still is where I would go deeper: email forwarding and Gmail connection lead to a flight card, but the traveller is left to infer the review step and access conditions. A concrete reservation check would make that promise easier to trust than another general claim about simpler planning.
Actual listing creative · App Store source ↗
One storefront, one language and a dated capture. This is an independent editorial audit, not a client case study.
Open the source listing ↗. Public text cannot reveal the private keyword field, search volumes, rankings or conversion rates. The recommendations below are proposals to validate.
What I saw. A Miami trip combines map pins, reservations, attachments and a places list.
My read. This shows why an itinerary tool can be useful beyond navigating to one address.
What I’d do. Keep the combined planning view and verify the scope of any depicted export action.
What I saw. The second still shows notes mentioning MRT and restaurant entries including Toa Payoh, while the first is labelled Miami and the third Oahu.
My read. The screens demonstrate breadth, but a newcomer cannot follow the same stop or booking across all three.
What I’d do. For a future sequence redesign, use one coherent trip; isolate the import test first.
What I saw. The third still highlights forwarding email and syncing with Gmail beside a flight reservation.
My read. A viewer could assume the methods have identical access and reliability. The description explicitly places Gmail linking and Google Maps export in Pro.
What I’d do. Verify each method, its entitlement and the actual way to inspect or correct an imported reservation.
The original creative is preserved. Numbered notes sit beside each frame so observations and recommendations stay separate.
The pictured export action does not establish that export is included for every user.
Test idea: Retain the consolidation story with accurate current access context.
Original image source ↗
The screen makes a flexible travel document concrete but introduces a different destination example.
Test idea: Use consistent sample places when testing a complete journey, and distinguish saved notes from verified live travel information.
Original image source ↗
It does not show the original confirmation, permission step or correction path, and an on-schedule badge is not evidence of guaranteed live alerts.
Test idea: Test a real import-to-review example with verified access conditions and accurately represented edit controls.
Original image source ↗Observed competitor metadata
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
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
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.
Intent candidates grounded in the listing—not fabricated search-volume or difficulty scores.
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.
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.
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.
Proposed copy for discussion. These are not current listing fields or tested winners.
Observed listing
Itinerary & Road Trip Guide
Proposed alternative
Itinerary, maps & group trips
Name 26/30 · Subtitle 29/30 charactersKeep 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.
Show: A consistent example with map, stops and reservations.
Establish the workspace and destination.
Show: Verified ordering and sharing controls for that same trip.
Show planning as an editable task rather than a finished travel guarantee.
Show: A supported import method, resulting record and actual correction or confirmation action.
Make the automation boundary and traveller’s responsibility visible.
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 1120626899829 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 1369052956820 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 12441379503A 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.
The creative skips permission, validation and correction.
Deliverable: A verified reservation-import third-frame concept with accurate access context.
Product and creative workThe description distinguishes Pro Gmail linking and Google Maps export.
Deliverable: A dated feature-access sheet for every pictured integration.
Product verificationDifferent destinations demonstrate breadth without a continuous story.
Deliverable: A separate one-trip storyboard with realistic stops and booking data.
Creative planningDoes a reservation-review third frame improve import expectations and qualified acquisition?
Check Apple’s current product page optimization guidance and custom product page guidance before configuring a test. Write your experiment brief.
Solid. The creative contains real planning surfaces and enough detail to distinguish an itinerary workspace from a plain map. However, Miami, Singapore-style notes and an Oahu trip appear across separate examples, so the sequence does not tell one continuous journey. The import frame also pairs two methods without explaining their different requirements. I would test that specific gap before rebuilding the whole listing.
The basics need a serious rethink.
Too many obvious things have been left unfinished.
There is a useful product here. The listing needs to show it.
The essentials are there, but there is little to get excited about.
Good ideas, with a few important gaps still to close.
A strong foundation. Look for specific improvements, not a complete restart.
Clear positioning, thoughtful choices and very few loose ends.
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.
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.
Bring your listing and the evidence behind it. We can turn a public critique into a prioritized plan for your actual audience.
See what an ASO audit includes →
