react-native-architecture

Use Expo Router with file-based routing: define screens in the app directory, group them with folders like (tabs) and (auth), and configure a root Stack in _layout.tsx. Navigate programmatically with router.push, router.replace, and router.back.

Combine React Query with AsyncStorage persistence using PersistQueryClientProvider, set networkMode to offlineFirst, and sync online status via NetInfo. Use optimistic mutations with rollback on error for a responsive offline experience.

Expo offers lower setup complexity, built-in OTA updates, and EAS Build for managed native code, while bare React Native gives direct native access at the cost of manual linking and custom CI. Expo supports custom native code through config plugins.

Yes, use an AuthProvider that reads tokens from expo-secure-store and redirects based on route segments. When the user is unauthenticated and outside the (auth) group, call router.replace to send them to the login screen.

FlatList struggles with large datasets; switch to Shopify's FlashList with estimatedItemSize for better recycling. Also memoize list item components, use useCallback for renderItem, and avoid inline styles in render.

Configure build profiles in eas.json, then run eas build for each platform and eas submit to upload to the stores. Use eas update to push over-the-air JavaScript updates without a full store review.