CORE TECH — OFFLINE-FIRST ARCHITECTURE

Offline-First Data Collection.
Sync when you're ready.

Field work happens where antennas don't reach. Remote pipelines, dense forests, underground vaults, rural roads — data capture can't depend on having signal. Mapalyze saves everything to an encrypted local database first and syncs automatically when connectivity returns.

Device local DB847 records
Pending sync12 queued
NetworkNo signal — offline
LOCAL-FIRST ARCHITECTURE DEVICE ACTIVE
Your Device
PRIMARY STORE
Local Database
ALWAYS AVAILABLE
Cloud Server
WHEN CONNECTED
Device holds the source of truth
12
QUEUED
THE PROBLEM

The problem with "offline mode"
in field data apps.

Most field platforms treat offline as a checkbox to tick, not an architectural decision. The result is predictable — and expensive.

01

Looks offline. Fails in practice.

The app lets you start a form without a connection. Fine. But it freezes when saving a record with 6 photos and a polygon. Offline capability was added after launch, not designed from the ground up. Your team finds out the hard way — mid-inspection, 35 kilometres from the nearest signal.

02

Data loss on reconnect.

An intermittent connection is worse than none. When signal comes and goes, some platforms attempt partial syncs that fail mid-transfer. Records get corrupted, photos disappear, or duplicate entries flood your database. Your team spends the afternoon untangling data that should have synced cleanly the first time.

03

Needs internet just to open.

Some platforms require internet just to open the app, load a project, or download form definitions. If your team arrives at a remote site and opens the app for the first time that morning, they're stuck. No connection, no work — even if the tool claims to have offline support.

HOW MAPALYZE HANDLES OFFLINE

Offline data collection isn't a feature.
It's the foundation.

LOCAL-FIRST ARCHITECTURE

Your device is the
source of truth.

Every write goes to an encrypted local SQLite database (SQLCipher, 256-bit AES) before anything touches the server. Every local write creates a paired sync operation in the same atomic transaction — your outbox is always in lockstep with your data. The encryption key is stored in the platform secure enclave (iOS Keychain / Android Keystore). Your device holds the authoritative copy while offline.

Encrypted at rest with SQLCipher — 256-bit AES, key in secure enclave
WAL mode enables concurrent reads while writes proceed
No reduced mode, no feature degradation — offline is the full experience
DEVICE STATUS OFFLINE
LOCAL DATABASE
847 records
ENCRYPTED ON DEVICE · SOURCE OF TRUTH
PHOTOS
2.3GB
FULL RESOLUTION
GPS POINTS
4,821
LAT/LNG/ALT/ACCURACY
App fully operational — no signal required
AUTOMATIC BACKGROUND SYNC

When signal returns, your
field data syncs automatically.

The moment the device detects connectivity, sync starts automatically after a 5-second debounce. The engine runs in the background on both iOS and Android using lease-based mutual exclusion — no two sync cycles can run concurrently. Adaptive batching sends 200 to 1,000 operations per batch based on queue depth. Pull page sizes adapt to Wi-Fi vs cellular. If connectivity drops mid-sync, the engine picks up exactly where it left off.

No separate manual upload step for normal sync — pending work resumes automatically once connectivity returns
Lease-based mutual exclusion prevents concurrent sync conflicts
Adaptive batching — 200 to 1,000 ops per batch based on queue depth
SYNC QUEUE SYNCING
Pole Inspection #4821
4 photos · 1 GPS point · 847ms
SYNCED
Pole Inspection #4820
2 photos · 1 GPS point · 621ms
SYNCED
Environmental Sample #218
6 photos · 3 GPS points
68%
·
Site Survey #042
12 photos · polygon · queued
QUEUED
·
Pipe Inspection #1103
3 photos · 2 GPS points · queued
QUEUED
CONFLICT RESOLUTION

Two offline edits. One record.
Auto-resolved.

If two team members edit the same record while offline, Mapalyze automatically merges non-conflicting changes from both sides. If both people edited different fields, both changes are kept. If both edited the same field, the system records the conflict, applies the configured resolution path, and keeps that decision visible in Sync History before the merged result syncs back to the other devices.

Field-level merge preserves non-conflicting changes from both editors
Same-field conflicts follow the configured server-first path and remain visible in Sync History
Full merge history logged for audit compliance
CONFLICT RESOLVED AUTO-RESOLVED
Field-by-field resolution — Record #4819
FIELD
J. MARTINEZ · 09:18
S. REYNOLDS · 09:44
MERGED RESULT
Condition
Fair
Critical
Critical
Notes
Corrosion at joint B
Valve checked — OK
Valve checked — OK
Photos
6
4
4
MERGED RESULT
Contested fields kept the server version · unrelated local edits were preserved
AUTO-RESOLVED · NO USER ACTION NEEDED
RELIABILITY & SECURITY

Your team always knows
what's synced.

Every operation gets exponential backoff retry (15s, 1m, 5m, 15m, 1h). Permanent server rejections are dead-lettered — never retried forever. Content-hash deduplication prevents redundant pushes, and server-side operation ID dedup ensures idempotency. Malformed data is quarantined, not silently dropped. GPS captures full precision: latitude, longitude, altitude, accuracy, speed, and heading — all queued locally even without signal.

Exponential backoff: 15s → 1m → 5m → 15m → 1h per operation
Content-hash dedup client-side, operation-ID dedup server-side
GPS captures lat/lng/altitude/accuracy/speed/heading offline
SYNC STATUS LIVE
SYNCED TODAY
835
RECORDS · CONFIRMED
PENDING
12
RECORDS · IN QUEUE
RETRIES
0
BACKOFF QUEUE EMPTY
DEAD-LETTER
0
NO PERMANENT FAILURES
PHOTO UPLOAD — BACKGROUND
inspection_047_photo_06.jpg
sample_218_photo_02.jpg
3.2MB
sample_218_photo_03.jpg
4.1MB
VS GOCANVAS

Mapalyze keeps synced forms, maps, and project data on-device so teams can keep working when signal drops. Newly published forms and project changes arrive on the next sync.

BUILT FOR REAL CONDITIONS

Where connectivity
is a luxury.

The offline architecture was designed for the environments where capturing data without connectivity is a necessity, not an exception.

Remote Utility Corridors

Utility inspection teams work along transmission lines, pipeline easements, and rural distribution networks that are kilometres from the nearest antenna. Inspect 47 poles, document damage, and capture GPS-tagged photos through a full shift — no signal required.

UTILITIES · PIPELINES · RURAL NETWORKS
🕳

Underground Infrastructure

Subways, tunnels, basements, and underground vaults have no cell signal. Full stop. Inspection teams need to document conditions, capture measurements, and photograph assets without any connectivity. Mapalyze captures everything locally and syncs when the team surfaces.

TUNNELS · VAULTS · SUBTERRANEAN
🌲

Dense Forest Cover

Environmental survey teams conducting biodiversity assessments, habitat mapping, and forest censuses work under tree canopies that block or degrade cell signal. GPS still works under the canopy, and Mapalyze captures all spatial and attribute data locally for end-of-day sync.

ENVIRONMENTAL · ECOLOGY · FORESTRY
📡

Intermittent Coverage Zones

Teams operating in regions with limited cell infrastructure need a tool that doesn't assume constant connectivity. Mapalyze keeps the same capture workflow on full LTE, intermittent 2G, or no signal at all, as long as the required forms, maps, and project data were synced beforehand.

RURAL · DEVELOPING REGIONS · LOW BANDWIDTH
GET STARTED

Your data shouldn't depend
on your signal.

14-day free trial. No credit card. Works on iOS, Android and web. Your team can be capturing GPS-tagged data in under an hour — with or without connectivity.

Open the Web App