The challenge
Trailhead runs guided expeditions in places with no reliable connectivity, and their app assumed a network on every screen. Travelers arrived at trailheads unable to load the itinerary they had downloaded at the hotel, meeting points were unreachable when it mattered, and the operations team absorbed the cost. The support line was staffed for calls that were almost always from someone standing somewhere with no bars trying to open a screen that required a request. The app's store rating reflected it.
What we did
Made airplane mode the acceptance test
We set one rule the build had to satisfy: after a trip is confirmed, switching the device to airplane mode changes nothing the traveler can see. That reframed the work from adding an offline mode to removing network dependencies, which is a different and more thorough exercise.
Cached the whole trip at confirmation
Itinerary, meeting points with local-language addresses, guide contact details, permits, gear lists and a pre-loaded map area around every waypoint, all saved to the device the moment a booking is confirmed, not on first open. The download happens while the traveler still has hotel wifi, which is the only reliable window.
Moved critical moments to wallet passes
Meeting times and locations were pushed as wallet passes, not notifications. A pass surfaces on the lock screen at the right time and place without an app launch, a connection or notification permission. Those are three things that fail in exactly the conditions these trips involve.
Built a time-zone fixture suite
Expeditions cross zones and occasionally date lines, and the previous app displayed departure times that were wrong by a day in specific combinations. We built a fixture set of the nastiest real itineraries from their booking history and ran it on every build, which turned a recurring support issue into a test that fails loudly in CI.
The result
Support calls during trip days fell 54% within two quarters, and the operations team reallocated a full-time role away from the phone line. Repeat bookings rose 34%. We can't prove the rebuild caused that, but the feedback is consistent, and travelers who never lost access to their itinerary describe the operator differently. The app holds a 4.7-star rating against 3.1 before the rebuild, and cold start with no connection is under a second.
What result did Trailhead Collective get? +34% in repeat bookings over 7 months, completed in 2026.
“The old app worked perfectly in our office, which is the one place nobody uses it. Watching them test on airplane mode from the first week told us they'd understood the actual problem faster than anyone we'd briefed before.”
Figures reflect real engagement outcomes at the time they were measured. This is a demonstration build — the client name and identifying details above are illustrative.