Field app
The dashboard rides along, signal or no signal.
Field work happens where the signal drops and the gloves stay on. An app that needs four bars to show a job is a clipboard you cannot read.
One phone, the same records
- Step 1Today, firstThe phone opens on the same Today command view the office sees, sized for a thumb.
- Step 2Photos that queueCaptures upload through a queue that survives leaving the screen, then land on the job.
- Step 3Documents on this deviceAn opened document stays on the phone in an encrypted store, readable with zero signal.
- Step 4Flory rides alongAsk what needs attention today; every proposed action still waits for your confirmation.
How the work moves
Built for the day the signal drops.
Offline is the design center rather than an error state, so what the screen shows is always labeled with what it actually is.
- Step 1
Every surface worth a phone screen
Today, jobs, permits, photos, documents, schedule, customers, crew, leads, proposals, claims, compliance, storm, inbox, search, settings, equipment, catalog, money, commissions, and performance are all on the phone, each with its own papercraft object.
- Step 2
The snapshot restores first
The field snapshot comes back with zero signal, so the last synced record is readable before the network is.
- Step 3
Honest per-section states
A section that has not synced says so, and one that is stale says how stale. The app never fabricates a zero where it simply does not know.
- Step 4
The same ledger face
Money, dates, and counts sit in the same mono ledger face the office uses, so a number reads the same on a roof as at a desk.
Next step
Put the record where the work is.
The same organization, the same jobs, the same ledger, in a pocket that keeps working offline.
Rolling out through TestFlight now.