native-data-fetching

Use the fetch API with explicit response status checks: call fetch, verify response.ok, and throw typed errors for non-2xx statuses. Wrap requests in a helper that distinguishes HTTP errors from network failures for consistent handling.

React Query (TanStack Query) suits complex apps needing mutations, cache invalidation, and offline persistence, while SWR fits simpler fetching needs. React Query also integrates with NetInfo via onlineManager to pause queries when offline.

Store tokens with expo-secure-store, not AsyncStorage, since SecureStore encrypts sensitive values. Combine it with an authFetch wrapper that attaches the Bearer token and a refresh flow that deduplicates concurrent refresh requests.

Expo Router supports route-level data loaders on web with SDK 55+ by exporting an async loader function and reading it with useLoaderData. Loaders are web-only; native platforms should use React Query or fetch instead.

Define EXPO_PUBLIC_ prefixed variables in .env.development and .env.production files, then read them via process.env. These values are inlined at build time, so restart the dev server after changes and never put secrets in prefixed variables.

React Query only pauses queries if onlineManager is synced with network status. Register a NetInfo event listener with onlineManager.setEventListener so queries pause offline and resume when connectivity returns.