react-native-web-pwa-is-wrong-architecture
Using React Native + Expo rendered via react-native-web + Metro as a PWA produces worst-of-both-worlds: 434KB lockfile, 50+ Expo deps, slower bundles, and no true PWA capabilities. A PWA should be built on a web-native stack (Next.js/Remix/SvelteKit). RN-web is only valid when sharing code with a real native app — if the target is purely browser, start web-native.
Related
- react-native-web-as-pwa-is-structural-anti-pattern
- react-native-web-is-not-a-viable-pwa-stack
- react-native-web-is-wrong-pwa-stack
- react-native-web-expo-is-wrong-architecture-for-pwa
- react-native-web-metro-wrong-stack-for-pwas
- react-native-web-pwa-antipattern-bundle-cost
- react-native-web-metro-is-antipattern-for-pwa
- react-native-web-is-anti-pattern-for-pwa
- react-native-web-as-pwa-substrate-is-antipattern
- react-native-web-for-pwa-structural-antipattern
- react-native-web-pwa-architectural-anti-pattern
- react-native-web-is-wrong-stack-for-pwa
- react-native-web-metro-is-anti-pattern-for-pwa
- react-native-web-antipattern-for-pwa
- react-native-web-expo-is-anti-pattern-for-pwa
- react-native-web-is-wrong-architecture-for-pwa
- react-native-web-expo-pwa-is-worst-of-both-worlds
- react-native-web-pwa-is-structural-antipattern