Case study ·

2024

Atlas Rail

A seat booking flow for night and day trains across Europe, with a seat map that loads before the price does.

Role

Booking flow

Client

Atlas Rail

Stack

React Native · TypeScript · GraphQL

Result

Search to booked seat in 48 s

Atlas Rail seat booking: coach seat map with the chosen seat, trip from Amsterdam to Berlin and a ticket card

01 — The problem

Six screens to pick a seat.

Choosing a seat took six screens, and the seat map appeared only after payment details, so people paid for seats they did not want.

Desktop · 1440 px

Atlas Rail search results from Amsterdam to Berlin with a seven-day fare strip, filters and a selected train

01 —

Pick a train in seconds

Seven days of fares at once

Seven days of fares at once

02 — What I built

Seat map, filters and price together.

A single screen where the seat map, filters and trip summary sit together. The map is cached per train, so it opens instantly while the price loads in the background. The ticket works offline on the phone.

Phone · 390 px

Three Atlas Rail phone screens timed at 0, 19 and 48 seconds: search, the suggested usual seat 42A, booked

02 —

48 seconds to a seat

Search, seat, booked

Search, seat, booked

Component · 5 states

The Atlas Rail seat in five states, its anatomy with sizes and contrast, and the coach 7 seat map

03 —

One seat, five states

Seat states, sizes and the coach map

Seat states, sizes and the coach map

03 — What changed

A booked seat in 48 seconds.

Median time from search to a booked seat fell to 48 seconds, and seat change requests dropped by a third.

48 s

median from search to a booked seat

−33%

seat change requests

Create a free website with Framer, the website builder loved by startups, designers and agencies.