Travel · US iPhone listing
My take: Whoever did this knows their stuff.
Flighty has a confident opening: a flight map, dated award artwork and a connected phone composition. The third still then shows live status on the lock screen and Dynamic Island. I would preserve that first pair and improve the practical explanation that follows it. A traveller needs to understand what the status means, what is a prediction and which features require Pro—not just admire the interface.
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. The first still has a partial phone at its right edge; the second continues the dark map treatment with the tilted flight-list phone.
My read. Moving one frame independently could break the visual sequence and weaken the intended reveal.
What I’d do. Preserve both as a control pair and test the third slot first.
What I saw. The second still shows flight legs, a connection-duration label and a tight-connection indicator beneath attributed press artwork.
My read. The product interface suggests practical help, but one static example cannot establish a reliable connection recommendation or current endorsement scope.
What I’d do. Verify the displayed itinerary and distinguish observed flight status from estimates; retain attribution if the quote remains.
What I saw. The third still demonstrates Live Activities and Dynamic Island with sample route, gate and timing information.
My read. The surfaces are recognisable, but the image alone does not establish device support, refresh behaviour or Pro access.
What I’d do. Use an actual supported example and label its access requirements consistently with the current product.
The original creative is preserved. Numbered notes sit beside each frame so observations and recommendations stay separate.
The artwork builds trust but is not evidence of current comparative alert speed or coverage.
Test idea: Preserve the connected layout and independently verify recognition before reusing it in new creative.
Original image source ↗
It demonstrates information density but not the accuracy or completeness of every flight record.
Test idea: Keep the opening composition intact and verify every route, timing and prediction label used in a revised example.
Original image source ↗
Visitors can recognise convenience, but may miss the distinction between a forecast, a gate update and a scheduled time.
Test idea: Test a simpler third frame centred on one verified update with clear access and prediction context.
Original image source ↗Observed competitor metadata
Airplane & flight tracker
FlightAware names flight and airplane tracking directly.
The lesson: Flighty can emphasise the traveller’s immediate decision without claiming that other trackers lack operational information.
Observed competitor metadata
Live plane & flight tracker
Flightradar24 uses live plane and flight tracking in its metadata.
The lesson: Differentiate an individual itinerary workflow from broad aircraft discovery, while avoiding unsupported coverage comparisons.
Observed competitor metadata
Trip Itinerary & Alerts
TripIt names travel planning, itineraries and alerts.
The lesson: Clarify the job Flighty performs around a flight leg rather than imply it replaces every part of trip planning.
Intent candidates grounded in the listing—not fabricated search-volume or difficulty scores.
Visitor’s job: Follow a specific flight and understand its current state.
Evidence: The title and flight-list creative directly establish tracking.
Decision: Retain the clear category and use accurate distinctions between scheduled, estimated and actual information.
Visitor’s job: Learn about a disruption and the aircraft serving a trip.
Evidence: The subtitle and description foreground delay alerts and inbound-aircraft information.
Decision: Require evidence for comparative speed claims; do not turn a reviewer’s early alert into a universal timing guarantee.
Visitor’s job: Understand a connection and find relevant gate information.
Evidence: The second still includes a tight-connection indicator and the description names a connection assistant.
Decision: Verify current access, supported data and prediction labels. Do not promise a connection will be made or that gate information cannot change.
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
World's Fastest Delay Alerts
Proposed alternative
Flight status & delay alerts
Name 28/30 · Subtitle 28/30 charactersRetain the recognisable category and describe the useful alert job without an unverified global speed superlative.
The tradeoff: The proposed subtitle is less provocative than the current speed claim. Test relevance and qualified interest independently, and keep the creative test’s metadata fixed.
Show: The first half of a complete, verified opening composition with accurate recognition context.
Keep the distinctive brand introduction.
Show: The matching flight-list half with a real supported itinerary and clear estimate labels.
Preserve the visual relationship and demonstrate a personal trip.
Show: One authentic Live Activity or gate update with its timing meaning, supported device and access context.
Make the next useful action understandable without promising perfect information.
Three 2023–2026 accounts were chosen for sync attribution, corrected flight-search expectations and permission clarity. Both explicit reviewer corrections are preserved. Other travellers’ early-alert stories are not used to prove comparative speed, and allegations about developer motives are excluded.
Sample: 3 selected accounts from 8 displayed reviews. Dates: 3 November 2023–26 July 2026. No sentiment percentage is calculated.
3 January 2024 · 5/5 stars
“My airline app was the issue”
A January 2024 flight-attendant account included calendar-sync complaints, then explicitly corrected the cause to the airline app. It also praised inbound-aircraft information.
What I’d investigate: Preserve the correction. This is not evidence that Flighty currently fails to sync, and the old Apple Watch request is not a current feature gap.
Listing review source · Review ID 107801031483 November 2023 · 5/5 stars
“search by city pair”
A November 2023 reviewer struggled with repeated flight numbers, then reported that searching the city pair found the correct leg after developer guidance.
What I’d investigate: Use this as a discoverability lead while keeping the workaround and positive update. Verify today’s search behaviour before describing a defect.
Listing review source · Review ID 1054427734626 July 2026 · 3/5 stars
“full access to my calendar”
A July 2026 reviewer praised updates but questioned calendar permissions and found friend-sharing behaviour unclear.
What I’d investigate: Investigate the current permission and sharing flows directly. The reviewer’s privacy interpretation is not a verified account of data use or disclosure.
Listing review source · Review ID 14349645882A 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 third still contains several timing examples with little access context.
Deliverable: One current Live Activity concept with accurate status and Pro labels.
Product and creative workFastest is a comparative claim that screenshots cannot prove.
Deliverable: A documented claim review or factual alert-focused alternative.
Evidence reviewSelected accounts raise search, calendar and sharing questions.
Deliverable: A current walkthrough covering flight selection, permissions and recipient visibility.
Product researchDoes a simpler, correctly qualified third frame improve understanding of Flighty’s status updates?
Check Apple’s current product page optimization guidance and custom product page guidance before configuring a test. Write your experiment brief.
Whoever did this knows their stuff. The visual identity is coherent, the category is obvious and the third frame shows a useful surface outside the app. The opportunity is precision: sample times, predictions and paid access need the same care as the design. The subtitle’s fastest-alert claim requires comparative evidence; a strong personal travel story cannot establish that it is universally true.
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 Flighty. 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 →
