Nexma Mobile
Nexma in the field
Nexma Mobile brings the platform into the field. The same project DataStore your office team designs against travels with the crew on iOS and Android — offline-first, voice-and-vision native, with Jax along for the work. Designs flow out to the technician, status and evidence flow back, and the desktop Globe updates in real time. One source of truth, two ends of the same project.
Core concepts
The mobile app is not a separate product with its own data. It is a field client onto the same world model, scoped to the work assigned to the crew.
- One DataStore, two surfaces. The phone reads and writes the same project files as the desktop. A design published in the office appears on the device; a photo captured in a trench appears on the Globe.
- Offline-first by construction. The app assumes connectivity will drop. Work orders, drawings, and pending writes are durable on the device and reconcile when the network returns.
- Voice and vision native. Crews capture with the camera and the microphone, not a keyboard. Jax interprets what is said and seen and writes it back as typed entities.
- Scoped to the crew. A technician sees only the projects, work orders, and layers their role allows. The same permission engine governs phone and desktop.
A field write is not a free-text note. A captured photo or spoken report becomes a typed entity in the world model, attached to the work order, ready to trigger the next step.
Who it is for
The app targets the people who do the work on the ground, each with a tailored flow.
| User | What they do on the device |
|---|---|
| Crew leader | Run the daily route, accept and complete work orders, dispatch the crew |
| Inspector | Step through inspection checklists, capture evidence, file structured reports |
| Surveyor | Capture positions and assets in the field, ground-truth the design against reality |
| Field technician | Execute task steps, scan materials, capture photos and signatures |
On-device Jax
Jax runs on the device, tied to the active work order. Crews talk to it hands-free — on a ladder, in a trench, behind the wheel — and it answers against the project world model rather than the open internet.
- Voice-driven chat. Speak the request; Jax transcribes, reasons against the active Ontology, and acts through the same eight primitives it uses everywhere.
- On-device inference for fast turns. Common interpretation and capture flows run locally so the app stays responsive when the signal does not. Heavier reasoning escalates to the cloud when connectivity allows.
- Work-order context. Jax already knows the open assignment, its location, and its attached drawings, so the crew states only what is non-default.
Offline sync
A local store keeps the field session durable across network drops. Reads serve from the device; writes queue and reconcile.
1Offline: read work orders from local store
2 capture photos, voice notes, positions → queued writes
3Online: queued writes sync to the DataStore in the background
4 desktop Globe + tables react as each write landsConflict handling is described in detail on Field operations.
Platforms and languages
The app ships for both major mobile platforms with full localization.
| Item | Status |
|---|---|
| Android | Generally available |
| iOS | Beta with select partners; general availability planned |
| Languages | EN, HE, AR in the box, with full right-to-left support |
| Voice and TTS | Use the device locale |
Authentication
Sign-in is single sign-on through your organization's identity provider — the same identity that governs the desktop. Session tokens are short-lived and refresh on each network round-trip, and the app stores no long-lived credentials on the device, so a lost phone is not a lost key. See Permissions and roles.
Where to go next
- Field operations — daily routes, work orders, capture, and conflict handling end to end.
- Jax — the agent that travels with the crew.
- Permissions and roles — what each field role can do.
- DataStore — the world model the device reads and writes.