Why ZQX starts mobile first for field operations

The people doing the physical work in container logistics, drivers, depot staff, and site crews, are the ones least served by software that assumes a desk and a mouse. ZQX Field is built for a phone in one hand and a container, chassis, or gate in front of the other.

The current build is a web-based progressive app rather than a native mobile app, deliberately. A PWA reaches a phone immediately, supports an offline capture queue for patchy yard connectivity, and lets the execution flows, assignment, start, arrive, depart, complete, proof capture, exceptions, prove themselves against real field use before committing to native platform work.

That ordering matters because native mobile is expensive to get wrong. Passwordless sign-in, multi-business switching, device trust, and offline sync all behave differently once they are wrapped in an app store release cycle. Proving the field workflow itself on the web first means the native app that follows is built against requirements that have already been tested, not guessed at.

Native ZQX Mobile remains on the roadmap as one consolidated app for every field role, not a separate app per function, once the PWA has done that proving work.