01The Question Everyone Asks Wrong
Leadership usually frames the decision as native versus PWA — as if those are the only two rooms in the building. In 2026 the real choice is which surface the product needs: a store-listed app with deep device access, an installable web app that ships from one URL, or a cross-platform native shell such as React Native.
Teams that skip that distinction spend the first six months rediscovering constraints: push behaviour on iOS, offline sync, biometric login, store review cycles, and who owns the release. The stack is not a preference. It is a consequence of those constraints.
PWA
One URL, installable on the home screen, shared across devices. Fast to ship — with platform limits you must design around.
Native
Installed from the store, full OS access, and the home-screen presence users already expect from enterprise tools.
React Native
Native UI on iOS and Android from one codebase. Closer to device APIs than a PWA, faster than two fully native teams.
Platform myths — fact-checked for enterprise
PWAs cannot send push notifications on iOS.
iOS 16.4+ supports Web Push for PWAs added to the home screen. Enterprise MDM environments may still restrict this, so verify your deployment context.
React Native is a compromise between native quality and web speed.
Modern React Native with JSI (JavaScript Interface) delivers near-native performance for 95% of enterprise use cases. The "compromise" narrative is 2019-era.
PWAs are always faster to build and deploy.
PWAs avoid app store friction but require service worker complexity, caching strategy design, and offline sync architecture. For complex apps, build time is comparable.
Offline-first apps always need native.
PWAs with well-designed service workers handle read-heavy offline scenarios well. Complex write-then-sync operations (field service, inventory) still favour React Native + WatermelonDB.
