In this single field test, the tester stopped within five meters of the excursion meeting point.
In this walk, the SDK called the route at 11.52 minutes. The actual time was 12 minutes 13 seconds.
Airplane mode start to finish. No Wi-Fi, no cellular, no roaming. Phone might as well have been a brick.
No dropouts, no "searching for signal," no gaps in the trace. The blue dot held the entire walk.
A timer tells passengers when. ShipSafe shows whether they can still make it back.
Countdown timers tell passengers when all-aboard is. That's a real upgrade for the industry. But knowing when you have to be back is only half the problem. The other half — the part ShipSafe focuses on — is whether the passenger still has enough walking time to return.
That's the gap ShipSafe is built to address. Budapest is the latest field test showing that logic working in a real city walk.
The setup
I'd never been to Budapest before. That mattered. Most navigation field tests are run by someone who already knows the streets, who already knows that this alley is a shortcut and that one is fenced off. I wanted to walk in cold, the way a cruise passenger does — off the ship, no plan, no muscle memory, no idea which way north is.
Phone goes into airplane mode at the gangway. Destination: St. Stephen's Basilica, which on this itinerary is the meeting point for a guided walking excursion. Out-and-back loop. Tight return-to-ship window on purpose, because comfortable margins are not where this product gets stress-tested.
The whole walk runs on GPS only. GPS works without internet — same as on a hiking trail — and the SDK does the rest with port data that's already on the device.
What the SDK actually did during the walk
Time-to-ship awareness, no internet required. From the second I stepped off the gangway, the app was tracking my walking speed, the distance back to the pier, and the time I had left before all-aboard. It does this on the device. There is no "we'll catch up when you reconnect" delay. The countdown was honest the whole time, and when I slowed down to read a sign, it noticed and adjusted.
Walking-path routing, not driving routing. Anyone who has tried to use a generic mapping app on foot in a European city knows the problem: it tries to put you on a road built for cars. ShipSafe routed me through pedestrian streets, around the car-only stretches, and across the squares that a driving route would refuse to acknowledge. Because the SDK knows it's planning for a person on foot, not a vehicle, it stays on streets a person can actually walk.
Live re-routing when I went the wrong way. I made one wrong turn near Vörösmarty tér — genuinely wrong, not a manufactured one — and the route updated within a few seconds. No spinner. No "no connection" error. Same thing happened later when a faster path opened up after I crossed onto a smaller street: the ETA dropped, the new line drew, and the alert thresholds reset against the new arrival time.
Essentials nearby, surfaced offline. Halfway back I needed an ATM. The Navigator tier surfaces nearby essentials — ATMs, pharmacies, restrooms, convenience stores — pulled from on-device port data. No search bar. No "loading." Tap a category, see what's close, walk to it. This is the kind of thing that sounds small until you're standing on a sidewalk in a country whose language you don't read.
And then the moment that matters most: the return-to-ship escalation alert fired at the correct buffer threshold on the way back. Not too early, where passengers learn to ignore it. Not too late, where it doesn't help. At the threshold the model picked, given my pace and the distance still ahead.
For this walk, the SDK called the route at 11.52 minutes. Actual: 12 minutes 13 seconds. The tester arrived inside a five-meter circle of the meeting point in a city neither the tester nor the device had used before.
This walk validated GoTime, too
Ocho Rios, the previous field test, exercised the back-to-ship layer — the layer that helps passengers understand whether they still have enough time to return. Budapest exercised that and the GoTime excursion-awareness layer in the same walk.
St. Stephen's wasn't just a generic destination. It was a real shore-excursion meeting point, with a real meet-by time, on a real itinerary. The SDK tracked the walking ETA to that meeting point alongside the walking ETA back to the ship. Two clocks running in parallel, both on-device, both right.
That is the difference GoTime makes for the passenger experience. The cruise app already knows where the meeting point is. With ShipSafe, the app also knows whether the passenger is actually going to make it there on foot — early enough to do something about it if the answer is no.
Two continents, same result
Six weeks ago we ran the same kind of test in Ocho Rios, Jamaica: 17 minutes of walking in airplane mode, then a head-to-head against Google Maps. Caribbean port. Different street network. Different climate, frankly. Same pattern: useful ETA context, no connectivity used, full loop back to the pier.
Budapest is Central Europe. Old streets. Tram lines. A river running through the middle of the route. Nothing about the two cities is the same except that the SDK doesn't need them to be. It works the way it works because the routing happens on the phone, against port data that's already there.
Two ports. Two continents. Both fully offline. That is the evidence base we wanted before walking into Seatrade conversations with cruise lines.
What this means if you're a cruise line
The same SDK runs across three tiers. Core handles offline walking ETAs, pace-adjusted timing, compass bearing, and departure alerts — the basics of return-to-ship guidance. Navigator adds route-aware walking guidance, nearby essentials, self-healing GPS, and re-routing. Navigator Plus adds multi-route alternatives and the GoTime excursion-awareness layer that Budapest exercised — offline walking guidance to meeting points alongside the back-to-ship layer.
Passengers don't download anything separate. There's no settings screen. Boarding times, ship names, and port data are fed into the host app automatically. The SDK activates when guests go ashore and watches the clock so they don't have to.
If you want to see what this looks like running live on a phone — including the Budapest test data — I'm happy to walk you through it.
Email me: info@shipsafesdk.com
ShipSafe SDK gives cruise-line apps offline walking ETAs and escalating alerts to reduce late-return and missed-excursion risk.
Learn about Return-to-Ship Safety →