The real test is offline reliability.
If your team works where signal drops, in basements, on remote sites, in transit, a native app with proper offline storage and sync is doing something a web app fundamentally can't do as reliably. That's the strongest case for going native.
Camera, location, and notifications are the other case.
If the job depends on the phone's actual hardware, photo capture tied to a specific task, location-aware assignments, push alerts that cut through, native access to those APIs is smoother and more dependable than a browser trying to approximate them.
If none of that applies, don't overbuild.
A team with reliable connectivity doing form-based data entry is often better served by a fast, well-built web app. Save the native investment for when the environment genuinely demands it.
Distribution and updates are part of the real cost.
A native app means an App Store process, device management, and an update cadence your team has to plan for. That ongoing responsibility should be priced into the decision from day one, not discovered after launch.
Bring your workflow, your constraints, and the outcome you want to achieve.