A cluster of 2026 buying guides for field inspection software keep drawing the same hard line: there is "offline," and there is fake offline. The difference only shows up once, in the field, at the worst possible moment.
The failure mode nobody notices until it's too late
Fake offline looks fine in a demo. The form fills in, the fields save, the app feels responsive. The problem shows up at submit time: the record needs a live connection to actually reach the server, so it queues silently, or worse, fails without telling the inspector. They walk off the site assuming the inspection is logged. It isn't, until someone notices the gap during an audit.
What actually has to work with the radio off
True offline means every step of the workflow - not just the form - keeps working with no signal: creating a new inspection, capturing photos and GPS, searching and referencing the applicable standard, bookmarking a clause for later, and syncing automatically the moment the connection comes back. Probe361 is built this way on purpose: a service worker caches the app shell, and the standards text itself (AWS, API, ASME clauses) lives in IndexedDB on the device, so full-text search and clause lookup work with the phone in airplane mode, not just a static "last viewed page."
Persian-language access is its own offline problem
Most inspectors' actual alternative isn't another app - it's the official standards portals themselves (IEC, BSI, ISO), which are English-only web portals with no offline mode at all. For a Persian-speaking welding inspector on a site with no signal, that's a bigger daily obstacle than most vendor comparisons even mention when they talk about "offline support."
None of this is a knock on cached-form tools - they solve a real problem for a lot of field work. But for standards lookup specifically, where the actual content (not just a form) has to be searchable and correct with zero connectivity, the distinction between caching a page and shipping the data itself is the whole ballgame.
