react-native-web-expo-is-wrong-architecture-for-pwa
Using React Native + Expo compiled via react-native-web + Metro bundler for a PWA creates worst-of-both-worlds: 50+ Expo dependencies, 434KB lockfile, slower bundle than a native web stack, and none of the PWA primitives (service worker push, install prompt, manifest) are first-class. A PWA must be built on Next.js, Remix, or SvelteKit — not RN-web shim layer.
Related
- react-native-web-as-pwa-is-structural-anti-pattern
- react-native-web-expo-anti-pattern-for-pwas
- react-native-web-is-wrong-pwa-stack
- react-native-web-is-not-a-viable-pwa-stack
- react-native-web-pwa-antipattern-bundle-bloat
- react-native-web-expo-as-pwa-is-worst-of-both-worlds
- react-native-web-metro-wrong-stack-for-pwas
- react-native-web-is-wrong-architecture-for-pwa
- react-native-web-pwa-is-wrong-architecture
- react-native-web-pwa-antipattern-bundle-cost
- react-native-web-is-anti-pattern-for-pwa