Book the trip. Carry it offline.
Arkanum Adventures runs group trips. I built their booking and payments platform, and a companion app travellers can read with no signal.
- Client
- Arkanum Adventures
- Built
- Booking and payments platform, staff portal and an offline trip companion app
- Owned by
- Arkanum Adventures
The booking site and the companion app.
One set of trips.
Two ways in.
Bookings ran through a rented platform that held the records. I built Arkanum its own, starting with one trip.
The website takes the booking and the money. The app carries the trips on the phone, where signal is often the first thing to go.
What got built
The trip page.
Each trip has its own page with the dates, the route and the price. Registration starts there.
The Umrah trip page on a phone. Register and pay a deposit.
Three steps: your details, who is going, then the deposit. The full payment schedule shows before anything is charged. Instalments then charge themselves.
Registration, step one of three. Every trip, with no signal.
The companion app carries every trip Arkanum runs, with its dates, route and price. It reads with no connection.
The trips tab in the companion app. One trip, in full.
A trip opens to its length, departure city and price. Travellers sign in with a code to see their booking and balance.
A trip in the companion app.
Their bookings.
Their Stripe.
Registration, deposits and instalments run on Arkanum’s own Stripe account. It has taken live payments since September 2026.
Staff see each trip in one portal: who is going, what is paid and what is due.
Needs a fact: what staff stopped doing by hand once bookings moved onto the platform.
Needs a fact: confirm the iPhone app has moved to Arkanum’s own Apple account, so “owned by Arkanum” covers every piece.