react-native-web-is-not-a-viable-pwa-stack
Using React Native + Expo rendered via react-native-web and Metro bundler as a PWA produces worst-of-both-worlds output: 50+ Expo deps, 434KB lockfile, slower bundle, no native web performance optimizations. PWAs should use Next.js, Remix, or SvelteKit. The RN-web approach is only justified when code sharing with a native mobile app is a primary requirement.
Related
- react-native-web-is-wrong-pwa-stack
- react-native-web-pwa-structural-antipattern
- react-native-web-expo-anti-pattern-for-pwas
- hypervisor-steal-time-misread-as-process-cpu
- skillui-live-site-to-claude-skill-extraction-pipeline
- react-native-web-as-pwa-is-structural-anti-pattern
- react-native-web-pwa-antipattern-bundle-bloat
- react-native-web-expo-is-wrong-architecture-for-pwa
- 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-metro-is-antipattern-for-pwa
- react-native-web-expo-is-antipattern-for-pwa
- react-native-web-as-pwa-is-structural-antipattern
- react-native-web-metro-is-anti-pattern-for-pwa
- react-native-web-pwa-is-structural-antipattern
react-native-web-for-pwa-is-structural-anti-pattern