Case study · Expedition Cruising

A faster, mobile-first booking experience for expedition guests

How National Digital gave Coral Expeditions a faster, more flexible online booking experience for guests planning an expedition cruise.

  • Next.js
  • TypeScript
  • GraphQL
  • AWS
  • Playwright

3

Ships booking through the experience

12+

Departure points served

Every step

Booking journey covered end to end

At a glance

Industry
Expedition Cruising
Engagement type
Booking experience rebuild
First release
2025
Team
National Digital engineering team

The challenge

Coral Expeditions wanted an online booking experience that matched the quality of its voyages - quick to load, clear on mobile, and able to change as itineraries and campaigns change, rather than being held back by everything sitting behind it.

What we built

A rebuilt Next.js booking site served by a clean, National Digital-built API layer, so the guest experience can be designed, measured and improved on its own release cycle.

  • Next.js booking front end rebuilt mobile-first for speed
  • Typed, documented APIs serving the guest-facing site
  • Caching to keep peak-season browsing fast
  • Automated end-to-end tests across the full booking journey

The outcome

Coral Expeditions now has a booking experience it can shape on its own timetable. The guest-facing site is a product in its own right - fast, mobile-first, and covered end to end by automated tests - so improving how a voyage is presented, priced or selected is a front-end decision rather than a whole-of-platform one.

Where it went next

The same foundation gives Coral Expeditions room to keep extending the guest experience - richer itinerary and cabin content, and more of the planning journey handled online.

This case study describes real work delivered by National Digital for Coral Expeditions.

Key Takeaways

What a faster booking experience actually takes

  • A booking journey is a product, and it earns its own release cycle.Critical

    Giving the guest-facing site its own service layer means the booking journey can be redesigned, measured and improved on its own timetable, instead of every change being scheduled around everything else the business runs.

  • When the purchase is considered, page speed is part of the offer.Critical

    An expedition cruise is researched over weeks and compared across many visits. A site that loads quickly and presents itineraries clearly keeps people in the planning journey, which is where the decision actually gets made.

  • Design the booking flow for a phone first, then let it grow up.Important

    Most travel planning starts on a phone and finishes somewhere else. Building the flow mobile-first means the narrow case is the designed case rather than the compromised one, and the desktop experience gets the room it has anyway.

  • Clean API contracts let the experience and the systems behind it move separately.Important

    The front end talks to documented, typed contracts rather than reaching into whatever sits behind them. Either side can change on its own schedule as long as the contract holds, which is what keeps a guest-facing rebuild from becoming a whole-of-business project.

  • End-to-end coverage is what protects a multi-step transaction.Helpful

    Automated tests exercise the real booking journey rather than isolated units, because typed contracts prove the pieces agree with each other but not that the flow still makes sense to the person completing it.

Coral Expeditions' booking experience is a fast, mobile-first product with its own release cycle, served by clean API contracts and covered end to end by automated tests. The guest journey can now be improved continuously without that becoming a whole-of-business project.

Questions decision-makers ask about this build

What changed for guests booking a voyage?

The booking experience got faster and clearer, particularly on a phone. Itineraries, cabins and pricing are presented through a rebuilt Next.js front end designed mobile-first, and the whole journey - from browsing a voyage to confirming a booking - is covered by automated tests so it stays that way as the site keeps changing.

Why rebuild the booking experience rather than restyle it?

Because a restyle leaves the constraint in place. The thing slowing the guest journey down was not how it looked, it was that the site could not change on its own timetable. Giving the front end its own service layer and clean API contracts is what makes continuous improvement a front-end decision instead of a scheduling negotiation.

How do you keep a booking site fast during a campaign?

Expedition cruise demand is peaky: campaigns, season launches and departure dates concentrate traffic into short windows. The APIs serving the site scale per service rather than sitting on provisioned capacity between those peaks, and caching absorbs repeat reads so a busy week is served quickly rather than becoming load on everything behind it.

How is a multi-step booking flow tested?

End to end. The booking flow is covered by Playwright tests that exercise the real journey rather than isolated units, which matters when the whole value of the experience is a multi-step transaction that must not break. Typed contracts catch drift between services; the end-to-end suite catches a flow that has stopped making sense to a human being.

Can the experience keep changing after launch?

That is the point of the design. Presentation, pricing clarity, cabin selection and itinerary detail all live in the front end, behind documented contracts. Coral Expeditions can improve any of them and release on its own cadence, with the automated suite standing behind each change rather than a manual regression pass.

What does this approach suit beyond cruise bookings?

Any business whose customer experience is a considered, multi-step purchase served from systems that run the rest of the business - travel, events, hospitality, education, healthcare scheduling. The move is the same: give the customer-facing product its own clean contracts and its own release cycle, so it can improve at the pace the market expects.

More client work

What's next

Rebuilding a booking experience?

Coral Expeditions' guest journey runs as a product in its own right, on clean contracts it can keep improving. If you're weighing the same move, see how we approach custom booking and scheduling systems and connecting the systems behind them, part of our wider custom software development work.

Want a platform like this for your business?

Tell us what you're building. We'll come back within one business day with what we'd do first and what it would take.

or enquiries@nationaldigital.com.au1300 800 855