react-native-web-expo-is-antipattern-for-pwa

Using React Native + Expo rendered via react-native-web + Metro for a PWA produces worst-of-both-worlds output: 50+ Expo dependencies, a 434KB lockfile, slower bundle times, and no true web-native PWA capability (no real service worker push, no VAPID). Web-native stacks (Next.js, Remix, SvelteKit) are structurally superior for PWA targets. This architectural mistake is common when adapting RN codebases for web without a full rewrite.

Related

• react-native-web-is-not-a-viable-pwa-stack
• react-native-web-metro-wrong-stack-for-pwas
• react-native-web-as-pwa-is-structural-anti-pattern
• react-native-web-is-anti-pattern-for-pwa
• react-native-web-for-pwa-structural-antipattern
• service-worker-network-caching-insufficient-for-push
• service-worker-network-cache-is-not-push-notifications
• react-native-web-for-pwa-is-structural-anti-pattern