
Stepper & Progress Logic
The current step, what's done and what remains, without the full tree.
Booking System · Web + Mobile · 2025
A modular booking system for Qiddiya's two flagship parks, handling multiple ticket types, add-ons and group bookings across web and mobile.
Not fixed flows. A system that generates them.




The challenge
One booking system for Six Flags and Aquarabia, each with its own tickets, add-ons and rules.
The approach
I designed a modular system that assembles each journey from shared building blocks, instead of hard-coding flows.
Impact
Business Goals
User Goals
Design Challenge
How might we support many ticket types, add-ons and group scenarios without overwhelming people, and ship it on two platforms in five months?
01
Designed, validated and handed off in five months, against park launch dates.
02
Six Flags and Aquarabia were built at the same time, on one shared system.
03
Tickets, add-ons and rules kept changing, so the flows had to change with them.
04
Payment and security requirements fixed parts of the flow in place.
01
Categories, bundles and add-ons, without adding steps for the user.
02
Journeys adjust per park, from ride access to experience bookings.
03
New rules and offerings slot in without reworking the core.
04
Consistent on web and mobile, with interactions tuned to each.
I structured every journey as a set of building blocks, arranged by what the user picks and which park they're in. Each block works on its own and behaves the same everywhere, so the question stopped being "which flow?" and became "which blocks?"

Modular System Components
Reusable blocks, not screens, combined to fit each booking scenario.

01
Choose a ticket or package, and compare alternatives.

02
Assign up to 9 tickets across Adults, Children, Seniors, Companions and People of Determination.

03
A calendar showing availability and peak pricing, narrowing from month to week.

04
Extras assigned to individual tickets.

05
Date-specific experience packages, added alongside tickets.

06
A live breakdown of tickets, extras, pricing, promo codes and upgrades.

07
Contextual upgrades that update the cart without breaking the flow.

08
Placed late in the journey to cut early drop-off.

09
Saved cards, Apple Pay and financing, with a final summary before confirming.
Challenge 01
The journey had steps within steps. Showing them all would have overwhelmed people, so we kept the stepper focused on where you are and what's next, and kept the rest out of the way.
Challenge 02
Paths branch by ticket type, add-ons and park. Instead of forcing one rigid flow, the journey adapts to each selection, so the complexity stays beneath the surface.

The current step, what's done and what remains, without the full tree.

Consistent across desktop and mobile, touch and pointer, English and Arabic.

Every change to tickets, dates or extras updates the price instantly.

Template 01
Problem
Choosing ticket types, quantities and dates without getting lost.
Solution
A guided structure with clear ticket groups and live pricing.

Template 02
Problem
Understanding extras and assigning them to the right ticket.
Solution
A filtered list with clear availability and per-ticket assignment.

Template 03
Problem
Reviewing and editing everything before checkout.
Solution
One cart with grouped items, edits, promo codes and upgrades.

Template 04
Problem
Several required steps that could stall people early.
Solution
Progressive steps, login held back, and a summary that stays in view.

Template 05
Problem
Clear feedback when payment succeeds or fails.
Solution
Dedicated success and error states, with next steps and a way to recover.

Decision 01
We moved sign-in to after people commit to buying. Fewer drop off early, and accounts are only created when there's real intent.

Decision 02
A 15-minute hold protects inventory during high demand and gives people a clear window to finish.

Decision 03
Composable journeys instead of fixed flows, so new parks and offerings don't need a redesign.

Decision 04
Extras attach to individual tickets, not the whole cart, so groups can customize per person without confusion.
01
Treat complexity as a structural problem. The answer was a better system, not busier screens.
02
Design for change. The rules shifted throughout, and the modular approach absorbed that instead of fighting it.
03
Speed and quality don't have to trade off when the system is right. Five months, two parks, no compromise on clarity.
Next Case Study
Six Flags Qiddiya City
The flagship digital platform for a record-breaking theme park, built to introduce it to the world before it opened.
View Case Study