Field app

Written for a phone held in one hand

The field app is not the console made smaller. It is made for gloves, a dirty screen, one free hand and a battery that has to last the day.

15 days • 10 users • no card required

Filling in

One action per screen

Targets are large, the order of questions follows the order of the work, and the app keeps your place if the phone locks.

Drafts are not lost: Closing the app halfway through a form erases nothing. The submission is written locally as you go.
Evidence is captured on the spot: Annotated photo, sketch, voice note, signature, position, barcode and NFC tag: what justifies the job is captured where it happens.
Upload state is always visible: What has gone, what is waiting, what needs correcting. Nobody has to call the office to find out whether the report arrived.

The day

Assignments arrive on the phone with their deadline. Three tabs — overdue, today, to do — and a map to get there.

Rounds handed to someone: Created by hand, imported, or generated by a workflow. Each carries its deadline and its prefilled form.
A notification when it matters: Round assigned, approval awaited, overdue. With an email fallback when no device answers.
A map, not a list of addresses: The day's assignments show on a map, and the route opens in the device's navigation app.

What to know

Two points of honesty, because they are otherwise discovered at rollout.

iOS and Android, not Windows: The desk uses the web console, which can also fill a form. A Windows application is not planned.
French and English: Other languages will come with demand. A vendor who announces nine languages without holding them lets you find out at go-live.
NFC needs a real phone: Tag reading is built and tested, but checking it on a real device in site conditions is still to do. We will say so when it is done.

That is the one-minute test that separates a field app from a mobile app. Fifteen days, ten users, no card.