Case study 04 / 04 · Travel & Experiences Platform

← All work

ZRI Adventures

The ZRI Adventures home page: navigation above a quad-bike adventure photograph, the headline “Untamed Sri Lanka” and tour links.

Exploration, made bookable.

A travel and experiences platform for browsing, planning and booking guided trips.

Role
Engineer: frontend and booking flow
Year
2024

01Overview

Overview

Built with

  • Next.js
  • TypeScript
  • PostgreSQL
  • Payments

Filed under

  • Client work
  • Travel
  • Booking

02The challenge

The challenge

Visitors need to compare dates, group sizes and itinerary options before booking a trip. The flow needs to make those choices clear.

03The thinking

How it was approached.

  1. 01

    Compressed the enquiry-to-booking path and let visitors explore itineraries without committing up front.

  2. 02

    Kept trip imagery prominent while managing image sizes and loading.

04The engineering

The system, taken apart.

The booking flow is the architecture. Every step between arriving and committing is one a visitor can abandon, so exploration is free and unauthenticated and the flow only asks for details once there is something to pay for.

  1. 01

    Visitor

    • Trip browsing
    • Itinerary variants
    • No commitment up front
  2. 02

    App

    • Next.js app
    • Compressed enquiry path
  3. 03

    Booking

    • Dates + group size
    • Payments
  4. 04

    Data

    • PostgreSQL
    • Trip content

05The experience

What people actually see.

Captured from the live product. Nothing here is a mock-up.

06What shipped

What shipped

  • Browsing, planning and booking unified in one flow.

Next case study

Snapvyn

Moments, becoming shared.

Continue
The Snapvyn home page: the headline “The photos you didn't know were taken.” beside an event album on a phone, Polaroid guest captures and a QR code.

Analytics

May I use Google Analytics to see which pages and interactions people use? It loads only if you accept. Form contents are never included. You can change this in the footer.