Technology · Field hardware
Choose for the
physical job.
A schedule can live happily in a browser. A rapid check-in involving a camera, a key tag, a location boundary, and time-sensitive alerts asks more from the device. The product should choose its runtime from those demands.
The decision
Most screens are not the deciding screens.
Forms, lists, dashboards, and reports can be excellent on the web. The split appears when a phone stops being a small monitor and becomes a sensor, radio, credential, and background worker.
Evaluate the few moments that cannot tolerate a browser losing context. Then use the lightest platform that handles those moments reliably.
Four capabilities
Where the choice becomes concrete
Camera and NFC are workflows, not checkboxes
Camera
Continuous capture
A plate workflow needs framing guidance, clear framing, reviewable results, and a fast handoff into the session, not merely a file picker.
NFC
Purposeful radio access
Reading and writing physical tags depends on platform APIs, device support, and lifecycle rules that differ from ordinary web input.
Location
Background behavior
If the operation needs a location signal while the app is not foregrounded, permission, battery, and OS scheduling become product constraints.
Push
Urgent delivery
A curb update must survive a locked screen and a suspended app. Native notification and activity surfaces are designed for that state.
→Do not count features. Trace the hardest field moment from sensor input to acknowledged result.
Use the web where reach matters most
Web surface
REACH- Opens from a link without installation
- Updates centrally
- Fits guest and manager tasks across devices
- Background and hardware behavior varies
Native field app
DEVICE- Deeper camera and radio control
- Durable local state and OS integrations
- Predictable locked-screen delivery
- Installation and release management
A mixed product is often the honest answer
The guest, manager, and valet do not share one device context, so forcing them into one runtime can optimize the wrong person.
Guest
Link first
A guest requesting a vehicle should not install software for a short interaction.
Manager
Large-screen web
Configuration, reporting, and review benefit from keyboard, space, and easy sharing.
Valet
Native field tool
Repeated sensor-heavy work earns a dedicated app when it reduces taps and survives poor conditions.
The procurement test
Test the capability with the screen locked and the signal weak.
A feature matrix created at a desk will make both options look equivalent. A field trial reveals camera latency, radio availability, background delivery, battery behavior, and the cost of returning to context.
The takeaway: choose the runtime that serves the physical job, then use the web everywhere installation would add more friction than capability.
