Cross-platform is the default
For a service-status app that is mostly lists, timelines, forms and push notifications, a single cross-platform codebase ships faster and costs less to maintain. Two apps stay in feature parity without two teams.
Go native when hardware is involved
Bluetooth OBD-II dongles, CarPlay and Android Auto surfaces, background location for pickup and delivery, or continuous telematics ingestion all argue for native. The platform APIs move quickly, and the bridge layers lag.
Hybrid is legitimate
Several products we run keep a cross-platform shell and drop into native modules for the two or three hardware-bound screens. It is not a compromise; it is the cheapest way to buy native behaviour exactly where users can feel it.