Skip to content
UXE Award

Travel and hospitality UX: designing for people in transit

Booking is the easy part. What editors look for in travel and hospitality products: the day-of experience, disruption handling, offline behaviour, and prices that don't change while you decide.

The UXE editors5 min read

Travel products are tested twice: once at a desk, in a calm moment, comparing options — and once in an airport at 6am when something has gone wrong. Most are designed for the first and abandon the user in the second. Entries that score well in travel and hospitality are the ones built for the second.

1. Search and compare without lying

Travel search is where dark patterns are most concentrated, and we know exactly where to look. Prices that rise when a result is reopened, fees that appear at the final step, "only two left at this price" that is always true, and pre-ticked insurance are all scored — under ethics, not just usability.

Search results, two ways
Compared onScoresCosts
Price shownTotal including taxes and mandatory fees, from the first screenBase fare, with fees revealed at step four
AvailabilityReal counts, or nothingPermanent scarcity messaging
ExtrasOpt-in, clearly pricedPre-selected, hard to remove
SortingDefault explained, changeable"Recommended" with no definition
Price changesHeld while the user decides, or explained plainlySilently different on the next click

2. The day of travel is the product

Booking happens once. The day of travel happens with luggage, a queue, a child, a phone at 12%. This is where a travel product earns or loses its reputation, and it's the part most entries forget to show.

  • The boarding pass, ticket or room key reachable in one tap from launch, with no sign-in and no network.
  • Screen brightness handled — a barcode that can't be scanned in sunlight is a design failure with a queue behind it.
  • Times shown in the traveller's timezone and the local one, labelled, with no ambiguity about which is which.
  • The critical number — gate, platform, room, reference — large enough to read at arm's length.

3. Disruption: the state everyone designs last

A cancelled flight, an overbooked hotel, a delayed train. This is the moment the product either helps or becomes another obstacle. Editors ask directly: what does the interface do when the plan breaks?

Four moves when things go wrong
  1. 01

    Tell them first

    Before the departure board does, and before the email.

  2. 02

    Say what it means

    Not "status changed" — "your connection is no longer possible".

  3. 03

    Offer the options

    Rebook, refund, compensate — in the app, not on a phone line.

  4. 04

    Confirm in writing

    A record they can show at a desk, offline.

4. Offline, always

Travel is the field where offline is least optional. Roaming is expensive, airport wifi is a captive portal, trains go through tunnels, and the moment you most need your ticket is the moment you're least likely to have a connection.

The benchmark: everything the traveller needs on the day is cached and usable with the phone in airplane mode. If an editor can't open their ticket offline, that finding goes in the verdict regardless of how good the booking flow was.

5. Groups, families and the real shape of travel

Most travel products are designed for one adult travelling alone, and most travel isn't that. Two adults and a child with different tickets. A group where one person books and four people need the details. Someone travelling with a wheelchair, or with a dog, or with a connecting ticket bought elsewhere.

Handling shared itineraries — sending the details to someone who isn't the booker, without requiring them to create an account — is a distinguishing feature in entries that score above 8.

6. Accessibility, mobility and assistance

Travel is one of the few fields where the accessibility of the interface and the accessibility of the service are the same question. Booking assistance, declaring a mobility need, finding step-free routes, carrying a medical device — if these exist only as a phone number, the digital product has excluded the people who most need to plan ahead.

What to send

A booking we can make or a sandbox that behaves like one, the day-of screens (ticket, room key, gate information), the disruption state, and the app in airplane mode. Plus your assistance-booking flow if you have one.

Travel entries usually go to Service Experience with a Travel subcategory, or Mobile Experience if the app is the centre of it. Enter a project — it's free, and the disruption state alone is worth having someone else's eyes on.

Loyalty programmes, and the points nobody can value

Loyalty schemes are where travel products are least honest and most complicated. A points balance that cannot be translated into anything concrete is a number, not a benefit — and editors will try to work out what theirs is worth.

  • Show what the balance buys, in real options, not in points.
  • State expiry clearly and in advance, not in the terms.
  • Make tier rules understandable in one screen, including how close the person is.
  • If availability is restricted, say so where the points are displayed rather than at the point of redemption.

Group bookings and the second traveller

Most products assume the person who booked is the person travelling. Designing for the second traveller — forwarding the details, adding them to the app, letting them check in themselves without an account — is unusual enough to move a score, and it is exactly the scenario every family hits.

Accessibility on the move

Travel is where accessibility meets physical reality. Step-free routing, assistance booking, seat requirements, service animals, medical equipment: if these exist only on a phone line, the digital product has excluded the people who most need to plan in advance. Products that put them in the main flow — bookable, changeable, visible in the itinerary — score conspicuously higher.

Questions we get asked

  • How do editors judge a booking product without booking?

    A sandbox is best. Otherwise we judge to the payment step, which limits what can be scored on the day-of experience — the part that usually matters most.

  • What's the most common failure in travel entries?

    The ticket that needs a connection. If an editor can't open their boarding pass in airplane mode, it goes in the verdict regardless of how good the booking flow was.

  • Are prices and fees judged as a design issue?

    Yes. Total price shown late, pre-selected extras and invented scarcity are scored under ethics as well as usability.

  • Should we enter the app or the website?

    Whichever carries the day-of experience. If the answer is genuinely both, Service Experience is the category that assesses them together.

Assessed work in mobility & travel

Chosen by score from the work the editors have assessed, not by hand.

  • travel
  • hospitality
  • industry

Written by

The UXE editors

The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.