- Market
- Saudi Arabia
- Written for
- Head of Digital, Head of CX
- Decision
- Build or rebuild an airport passenger app that travellers keep installed because it works on the day of the flight
The graveyard
Why passengers delete an airport app before the return flight
Most airport apps are not disliked; they are abandoned. Each failure below is common, each is avoidable, and each traces to a decision made in a meeting room rather than in a departure hall.
- 01
The login wall before any value
A traveller with a boarding pass in one hand and a suitcase in the other is asked to create an account before seeing a single flight time. Registration built to feed a marketing database costs the app the only moment it had to prove itself.
- 02
The status screen an hour behind the hall
One stale gate — the app saying B12 while the hall says B31 — and trust is gone for good. A passenger forgives an app that says “being updated”; nobody forgives one that was confidently wrong at the worst moment of the trip.
- 03
The brochure wearing an app icon
Restaurant listings, duty-free promotions and a photo gallery of the terminal duplicate the website without doing a single job the day of travel requires. An app with nothing live in it gives the phone’s storage cleaner an easy decision.
- 04
The notification that cried wolf
Promotional pushes teach passengers to ignore notifications, and then the one that mattered — the gate change — arrives pre-ignored. Notification permission is spent once; an airport app should spend it only on the flight.
The scope
Flight status, the walk and the car: what an airport app must do faultlessly
The passenger’s needs are unglamorous and absolute. First, the flight: is it on time, which terminal, which gate, has boarding started — answered without an account, faster than a search engine, and updated at the pace of the operations floor. Second, the way: from the kerb or the car park to the gate, with an honest walking time, and from the aircraft to the belt and the exit on the way back. Third, the car: where to park, what it costs, where the car was left, and paying without a queue at a machine. An app that does these three faultlessly has earned its icon; everything else is optional.
For a Gulf airport, one more requirement is not optional: the app is designed in Arabic first and translated into English, not the reverse. That decision is structural, not cosmetic — right-to-left layouts drawn as the primary case rather than mirrored afterwards, Arabic flight-city names from an authoritative source rather than transliterated by the app, and dates and numerals rendered the way the passenger actually reads them. An interface that treats Arabic as the second language tells the majority of its users they were an afterthought.
The hard part
How a gate change travels from the AODB to a passenger’s lock screen
The interface is the visible tenth of the work. The rest is this path, and every minute lost along it is a minute the app is lying to somebody standing at the wrong gate.
01
The operational record changes
A controller moves the flight to a new gate in the AODB — the same entry that drives the hall displays and the resource plan.
- AODB
02
The app platform hears it
An event interface — not a nightly export — carries the change to the app backend within the tolerance the operator sets, with the change timestamped at the source.
- Event feed
- FIDS
03
The right passengers are chosen
Only travellers who marked this flight are woken. Everyone else hears nothing, which is what keeps the one notification that matters believed.
- App backend
04
The lock screen tells the truth
The notification names the flight, the old gate, the new gate and the walking time from where the terminal map thinks the passenger area is — one glance, no app open required.
- Push
- Terminal map
When the feed goes quiet
If the operational feed stalls, the app says so — showing the last confirmed time with its age, never presenting stale data as current. Honest uncertainty keeps trust; a confident guess spends it.
The app is the last metre of a pipeline that starts on the operations floor; a beautiful last metre cannot rescue a broken pipeline.
Measurement
A million downloads can hide an app nobody uses twice
Download counts flatter every airport app, because travellers install under duress — a QR code at check-in, a Wi-Fi captive portal — and delete on the way home. The measures that describe reality are task completions: how many passengers checked a flight status and got a live answer, how many followed a route to a gate and arrived, how many paid for parking without touching a machine, and how many of those came back for a second trip. Those numbers are harder to collect and far harder to inflate, which is exactly why they are the ones worth putting in front of a steering committee.
Our role
What we engineer behind the app screen and what your teams keep deciding
- 01
The integration before the interface
We build the event feeds from the AODB, FIDS and parking systems first, because an app scoped from the screens inward discovers too late that the data it promised does not arrive fast enough to keep.
- 02
Arabic-first product design
The interface, the notifications and the terminal names are designed in Arabic and translated to English, tested with Arabic-speaking travellers, with right-to-left as the primary layout rather than a mirrored afterthought.
- 03
Honest instrumentation
We instrument the app around task completion — status checked, route finished, parking paid — and report those numbers as they are, so the investment case rests on journeys completed rather than icons installed.
What the app promises passengers, and which services join the roadmap after the core three, are your calls; we build the feeds, the interface and the measurement that make those promises keepable on a bad operational day, not just a calm one.
Common questions
What buyers ask
Does an airport need its own app when every airline already has one?+
The airline app and the airport app answer different questions. The airline knows the booking, the seat and the fare; the airport knows the building — which gate the walk actually leads to, how long security is running, where the car is parked, which belt the bag lands on. A passenger connecting between two airlines has two apps that each know half the journey and neither knows the terminal. The honest scope for an airport app is exactly the part no airline can cover: the building, the kerb-to-gate journey and the parking. Duplicating booking features the airline already does better is scope the airport app should refuse.
Should an airport app require passengers to create an account?+
Not before it has delivered value, and for most passengers not at all. Flight status, the terminal map and walking times should work the second the app opens, anonymously. An account earns its place only where it genuinely serves the traveller — remembering the parked car across sessions, storing a payment method, holding accessibility preferences — and it should be offered at that moment, as an exchange the passenger understands, not demanded at the door. Every screen placed between a stressed traveller and a flight time is paid for in deletions, and the marketing database an early login wall builds is a list of people who resent being on it.
What should an airport measure to know its app is earning its place?+
Completed tasks and returning travellers, not installs. The questions worth asking monthly: of the passengers who opened the app on a travel day, how many got a live flight answer without friction; how many started a route to a gate and finished it; how many paid for parking in the app rather than at a machine; and how many travellers used it again on their next trip. A falling delete rate after travel days is the single most honest signal, because it means the app survived the one test that matters. Download totals belong in none of these conversations — they measure the strength of the sign-up prompt, not the worth of the product.
In this cluster
Next step
Walk one journey with us
A working session that walks one passenger’s day-of-travel journey and defines the three jobs the app must do faultlessly before anything else is scoped.
Walk one journey with us
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly

