01The map is already on the device
Offline regions are first-class objects, not a cache. You choose an area and a zoom envelope, NavTrax pulls the tiles for every layer you have enabled, and the region is versioned so you can see exactly what is stale before you leave the trailhead.
Offline regionsPer-layer envelopesVersion pinning
02The AI runs on the phone
Wound triage, plant and wildlife identification, sky recognition and app-level questions all run through TensorFlow Lite models on the handset. A model router escalates to the knowledge base or the cloud only when a connection exists and the question needs it.
TFLite on-deviceModel routerRAG when online
03Writes are queued, not lost
Every mutation goes into a durable sync queue with an operation log. When any channel returns — cellular, Wi-Fi, mesh, satellite — the queue replays in causal order and resolves conflicts by field rather than by whole record.
Durable queueCausal replayField-level merge
04The group syncs through whoever gets a signal first
Group relay means one member reaching a ridge with two bars pulls and pushes for the whole party. Nobody has to be the one who climbed the hill.
Group relayStore & forwardMesh bridging
05Coverage loss is predicted, not discovered
The cell-signal predictor models terrain occlusion along your planned route and tells you where the bars end before you get there — so a satellite check-in is scheduled at the waypoint, not improvised at the summit.
Terrain occlusionRoute-awarePre-scheduled check-ins
06Emergency does not depend on the internet
SOS escalates through the channels that are actually up: group broadcast, mesh radio, then satellite, with a guarded confirmation step and a full audit trail of what was sent, when, and over what.
Multi-channel SOSGuarded confirmAudit trail