Alright, this one's been a long time coming. Starting today, the FieldPulse mobile app goes fully offline on both iOS and Android — and I mean actually offline, not the "kinda works if you squint" version some of you may have wrestled with in the past.

What "Fully Offline" Actually Means

Your technicians can now:

  • View assigned work orders (cached locally on app launch)
  • Complete jobs, capture photos, fill checklists, and collect signatures — all without a signal
  • Queue everything for automatic sync once connectivity returns

The app handles conflict resolution if someone else edited the same work order while you were offline. Yeah, this one tripped me up too when I first looked at it — the merge logic prioritizes field-collected data over dispatch edits in most cases, unless the dispatch edit happened after your offline timestamp. Edge case worth knowing about.

Technical Bits (Because I Know Some of You Want Them)

We moved from a "fetch on demand" model to a SQLite-backed local store with background sync workers. Roughly speaking:

// Your offline queue lives here until the worker runs
POST /api/v2/workorders/{id}/offline-update
→ queued locally → sync worker → server reconciliation

The sync worker runs every 60 seconds when connected, or immediately on reconnection. Large photo batches get chunked. Checklist submissions with 50+ items have been tested up to ~15MB without issues.

One gotcha: if your org uses custom role permissions, those get cached at login. New permission changes won't reach an offline device until the next full session. Something to file under "known limitation" for now.

Getting Started

Update to mobile app version 3.4.0 or later. The offline toggle is under Settings → Sync & Storage → Enable Offline Mode. There's a brief one-time download of your active work orders and reference data.

If you've got questions about the sync behavior or want to poke at the API changes, I'm around. For general how-to stuff, this troubleshooting doc covers the basics.

Parents Comment
  • Teresa — good catch. Multiple active sessions are supported, but the sync queue is device-specific. So if your tech completes a job offline on their phone, then switches to a tablet before the phone syncs, that completion won't show up on the tablet until the phone gets back online and pushes.

    We debated centralizing the queue but it gets messy with field devices. Current approach keeps conflict surface area smaller. If your workflow depends on frequent device swapping, let me know — there's a feature request open for cross-device sync state that I can bump.

Children
No Data