Why offline-first is not a feature — it is the default

Most "offline support" in construction software is a lie of omission. The marketing page promises it. The feature matrix has a checkmark next to it. Then you open the app on a site with no signal, tap submit on a daily log, and watch a spinning wheel until the session times out and everything you typed disappears.

The only honest definition of offline-first

An app is offline-first if every write action writes to a local database on the device first, the UI confirms immediately, and the server-sync happens afterwards in the background. The user does not wait. The user does not retry. The user does not even know whether the device is online. That is the bar.

Why this is architectural, not cosmetic

You cannot bolt offline-first onto a traditional request/response app. It requires a local write-ahead log, a queue with conflict resolution, and a synchronisation layer that treats the network as an optimisation, not a dependency. Any app that was not built this way from day one will ask you to "please check your connection" — which is not a feature, it is a bug the marketing team calls a feature.

What works offline in Krewcore

Every field-facing action. Submit a daily log. Capture and attach photos. Raise an issue. Clock in or out. Raise a change order. Complete a punch list item. Perform a safety inspection. View job details, documents, drawings, and the BIM model (from the last time they were opened). On reconnect, everything syncs in the background. The sync indicator on the home screen tells you how many operations are pending and when the last successful sync happened. You always know where you stand.

Conflict resolution, briefly

When two devices edit the same record offline and both reconnect, the server version wins and the user is notified. For append-only records — daily logs, photos, inspections, issues — conflicts are structurally impossible, because each new submission is a new record, not an edit to an existing one. That is not an accident; it is a deliberate modelling choice that eliminates a whole class of sync bugs.

The bottom line

If you work on sites with unreliable connectivity — and every construction site qualifies — offline-first is the single non-negotiable feature in any tool you consider. Everything else can be added later. Trust is destroyed the first time a foreman loses a daily log at 6pm on a Friday. It does not come back.