Zero signal is the default, not the edge case.
The app opens instantly with no network, works from a local store, and syncs only what changed — quietly, in the background, while the rep keeps moving.
An order taken is an order kept.
Every edit is saved locally, queued in a durable outbox, and replayed with retry until it lands. When two people touch the same record, conflicts resolve field by field — not last-writer-wins roulette.
Change the form at 10am. It's in the field by 10:05.
Layouts designed in the web studio render as native mobile UI. Changes reach devices without an app-store release — no version skew across your fleet.
The hardware, put to work.
Your brand on the home screen.
Multiple branded apps per company — colors, logo, splash — with per-app data policies and staged over-the-air updates. One binary underneath.
The outbox that never gives up.
server price kept, your note kept
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Mobile App |
|---|---|
| Local-first reads | Native |
| Delta and background sync | Native |
| Durable offline outbox | Offline |
| Rule-based conflict resolution | Native |
| Admin-governed selective sync | Configurable |
| Designer screens rendered as native UI | Native |
| Over-the-air layout updates | Native |
| Barcode and camera capture | Native |
| Push notifications with deep links | Native |
| Biometric lock | Native |
| Lock-screen session card | Native |
| Role-based apps from one binary | Native |
Everything in the Mobile App.
The questions evaluators ask.
Does the app work with no signal at all?
Yes — completely. Screens read from data already on the device, so the app opens instantly and stays fast with no connectivity whatsoever. Everything the user does — orders, check-ins, photos, forms — queues locally and syncs when the network returns. Offline is not a degraded mode with a banner; it is the design assumption. The rep in the warehouse basement and the technician in the lift get the same app as everyone else.
What happens to work captured offline if the app is closed or the phone restarts?
It survives. Every offline action lands in a durable outbox on the device the moment it is captured — closing the app, restarting the phone or running the battery flat does not touch it. When coverage returns, the outbox sends itself in the background. If the same record changed somewhere else in the meantime, the conflict resolves by rule rather than by silently overwriting someone's work.
Do screen changes need an app-store release?
No. Screens are built in the platform designer and delivered to devices over the air — a new field, a reshaped form or a whole new visit type reaches every phone without an app-store submission. That also ends version skew in the field: there is no long tail of reps on last quarter's layout, because layouts are not compiled into the binary in the first place.
Can we ship the app under our own brand?
Yes — the experience is yours by design. Screens, navigation and theme come from your platform configuration, and each role — sales, service, warehouse — gets its own app experience from a single binary your IT team manages once. Branded deployment under your own name is arranged as part of rollout, and because layouts arrive over the air, a branded app does not fork your maintenance.
Which devices are supported?
Android and iOS, both as native apps — screens designed once render as true native UI on each platform, so the experience stays fast and familiar. Biometric lock uses the device's own fingerprint or face unlock, push notifications deep-link into the exact record, and the camera doubles as the keyboard for barcodes, receipts and shelf photos. Admin-governed selective sync keeps each phone carrying only the data its role needs.
"We ran a full day through a no-signal belt and didn’t lose a single order. Within a month our reps stopped carrying paper as backup."