native-data-fetching

Use the fetch API with explicit error handling: check response.ok before parsing JSON and throw typed errors for HTTP failures. For Expo apps, prefer expo/fetch over axios, and wrap requests in a reusable API client configured with your base URL.

React Query (TanStack Query) suits complex apps needing mutations, cache invalidation, and offline persistence. SWR fits simpler needs with lighter configuration. Both handle caching, deduplication, and automatic request cancellation.

Store tokens with expo-secure-store, never AsyncStorage, since SecureStore encrypts sensitive values. Implement a refresh flow that deduplicates concurrent refresh attempts and attaches the token as a Bearer header in an authenticated fetch wrapper.

Define EXPO_PUBLIC_API_URL in .env.development and .env.production files; Expo inlines these at build time. Only EXPO_PUBLIC_ prefixed variables reach the client bundle, so keep secret keys in non-prefixed variables used only by server-side API routes.

Use @react-native-community/netinfo to track connectivity and sync it with React Query via onlineManager.setEventListener. Queries then pause while offline and resume automatically when the connection returns.

Yes, Expo Router supports data loaders with useLoaderData on web starting from SDK 55. For native platforms, use React Query or fetch inside your components instead, as detailed in the skill's references.