Travel · US iPhone listing

ASO Audit: Flighty

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

5/10Fine. A dangerous place to stop.

Flighty looks expensive in all the right ways. Its opening still spends prime space on awards and a floating plane before explaining the useful travel decision. A premium treatment does not get an automatic premium audit score.

ASO Audit: Flighty illustration: An airplane rises above diverging routes and stormy travel paths.
Gabriel Machuret in an ASO Guru T-shirt: squinting at unreadable details.

Gab’s verdict · 5/10Gabriel Machuret

Editorial illustrationFirst-class art direction. Economy-class 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 · 29/30 characters

Flighty – Live Flight Tracker

Observed subtitle · 28/30 characters

World's Fastest Delay Alerts

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

Why this gets 5/10

The flight detail and lock-screen status are concrete reasons to care. This is not just pretty airport wallpaper. Bring the changed flight information into focus so the benefit is as clear as the art direction. Show one flight update, the relevant change and the readable alert a traveller uses. Keep the styling. Make the practical advantage as obvious as the polish, and substantiate comparative alert claims separately.

  1. Reason to care

    1/2

    The travel and live-status context communicates a relevant passenger benefit, though premium language is less precise than a specific alert example.

  2. Product evidence

    1/2

    Flight detail and Live Activities are real but not a connected alert story.

  3. Readable at a glance

    1/2

    Dark partial devices and small timings weaken immediate readability.

  4. A useful sequence

    1/2

    Awards and press interrupt the flight-to-useful-alert progression.

  5. A reason to choose

    1/2

    Outside-app status is specific; fastest-alert wording needs separate evidence.

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

First-class is positioning, not proof

Look at the original: The frame introduces the flight-tracker category and publisher-displayed 2023 recognition.

Why I’m flagging it: Atmosphere and awards displace the first useful flight action.

Brief this change

Lead with one actual travel decision by a complete, readable interface.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The quote gets the loudest voice

Look at the original: The second still combines a flight overview with a visible tight-connection example.

Why I’m flagging it: Press praise competes with small flight and connection details.

Brief this change

Enlarge one relevant connection or status change; keep attributed recognition secondary.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The useful feature needs context

Look at the original: The frame shows status outside the main app with several sample timing labels.

Why I’m flagging it: Outside-app timings appear without a clear before-and-after event.

Brief this change

Show a update reaching the lock screen with accurate access and timing context.

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

Flighty – Live Flight Tracker

World's Fastest Delay Alerts

Proposed alternative

Flighty: Live Flight Tracker

Flight status & delay alerts

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

Retain 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.

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

  1. 01Make the benefit clear

    Proposed headline

    Follow your next flight

    Illustrative layout · verify the real flow

    Put this in the frame: The first half of a complete, verified opening composition with accurate recognition context.

    Why it earns the space: Keep the distinctive brand introduction.

  2. 02Show useful evidence

    Proposed headline

    See the trip in context

    Illustrative layout · verify the real flow

    Put this in the frame: The matching flight-list half with a real itinerary and clear estimate labels.

    Why it earns the space: Preserve the visual relationship and demonstrate a personal trip.

  3. 03Move the decision forward

    Proposed headline

    Understand the latest update

    Illustrative layout · verify the real flow

    Put this in the frame: One authentic Live Activity or gate update with its timing meaning, device and access context.

    Why it earns the space: Make the next useful action understandable without promising perfect information.

The test: Does a simpler, correctly qualified third frame improve understanding of Flighty’s status updates? 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

FlightAware Flight Tracker ↗

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

Flightradar24 | Flight Tracker ↗

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

TripIt: Travel Planner ↗

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.

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 tracker / live flight status

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.

flight delay alerts / incoming plane

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.

flight connection / gate updates

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.

What the selected reviews tell us

What three reviewers can teach us

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 10780103148

3 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 10544277346

26 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 14349645882

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

First-class is positioning, not proof

Atmosphere and awards displace the first useful flight action.

Deliverable: Lead with one actual travel decision supported by a complete, readable interface.

Creative brief and current-product check
02

The quote gets the loudest voice

Press praise competes with small flight and connection details.

Deliverable: Enlarge one relevant connection or status change; keep attributed recognition secondary.

Creative brief and current-product check
03

The useful feature needs context

Outside-app timings appear without a clear before-and-after event.

Deliverable: Show a supported update reaching the lock screen with accurate access and timing context.

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

One test worth running

Does a simpler, correctly qualified third frame improve understanding of Flighty’s status updates?

Audience
Eligible US English iPhone default-page visitors; include occasional and frequent travellers in comprehension research.
Control
The connected first two frames and captured third frame after verifying claims, device support and access wording in both variants.
Treatment
Replace only the third frame with one supported live-status example, explaining the update and Pro context. Preserve the opening pair, metadata, icon and offer.
Method
Verify the flight-state labels using safe sample data, check claim support, then run randomized comprehension research and eligible App Store product page optimization.
Primary measure
Platform-reported download conversion for eligible visitors; assess correct interpretation of the update as a separate research outcome.
Guardrails
No assumption of guaranteed faster alerts, fixed gates, certain connections or universal live-data completeness. Visitors should recognise estimates and paid access.
Decision rule
Predefine useful effect, sample requirement and analysis date from real baseline traffic. Keep control if inconclusive or if a conversion gain introduces incorrect travel expectations.
What could muddy the result
Disruption events, holiday travel, airline data availability, device mix and Pro promotions may affect response.

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/10Flighty 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 one actual travel decision supported by a complete, readable interface.
  2. Enlarge one relevant connection or status change; keep attributed recognition secondary.
  3. Show a supported update reaching the lock screen with accurate access and timing context.

What would change my mind?

  • Evidence supporting comparative alert claims and coverage limits.
  • Current feature access, status labels and permission flows.
  • Baseline traffic, conversion and status comprehension across traveller types.
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 Flighty. 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.