How Veldriq Field works

Flutter is a client. Laravel on your Veldriq deployment is the authority for jobs, licenses, and completion. This product never contains that server.

Screen path: technician shell Today / Jobs / Sync / Profile. Office CMS, License & Products, and Field Push credentials stay in Veldriq Web.

Veldriq Web (Laravel)
        ↕  HTTPS origin
Veldriq Field
   local Drift database
          ↕
   outbox / Sync

Preconditions

• A compiled binary with origin-only API_BASE_URL.
• Field APIs on that origin (/api/v1/mobile/*, /api/v1/field/sync/*).
• An eligible technician session (not a Profile API token).

How traffic flows

One origin (your Veldriq host). Tokens stay on the device (secure storage). Logos, CDNs, and maps never receive the token.

Sync model

1. Pull / bootstrap — download assigned jobs and related data into Drift.
2. Technician works (often offline).
3. Push — outbox operations go to the server (one operation at a time).
4. Pull — server state reconciles the local cache.

Open Sync → Sync now to run the same engine as bringing the app to the foreground. There is no websocket live board. FCM (optional) can wake a running/resumed app; it is not the sync engine.

Appointment grain

Work order
    ↓
one or more appointments
    ↓
technician receives the assigned appointment (Field job)

See Appointment = Field job.

What works / does not work

	Works	Does not work
Authority	Server accept / reject / pull	Treating a local tap as final Closeout
Sync while running	Foreground resume, Sync now	Periodic killed-app background synchronization
Tokens	Bearer on Field / mobile paths only	Bearer on logos, maps, or public files
Live board	Cached lists after pull	Websocket dispatch, GPS, ETA

Honest V1 limits

• Login is email and password — not Profile API tokens.
• Offline work queues while the app is running. A killed app does not sync in the background.
• No GPS / live van tracking.

If Sync stays pending: restore the radio, sign in again on 401, then Retry pending — do not tap Start work or Complete job again to “force” a second write.

Related: Offline-first · Sync Center.