State for React Natives
State in a React Native app covers both local component state and data that must be shared, fetched or persisted, along with sign-in. Typical tools are useState and useReducer, Context, Zustand or Redux Toolkit, TanStack Query for server data, and secure storage for tokens. It decides how screens stay in sync with each other and with the backend.
Stage: Navigation and State · Part of the React Native roadmap · Last reviewed 19 November 2026
What to learn in State
- Choose between local state, context and a global store for a given case
- Fetch and cache API data with TanStack Query
- Persist small values with AsyncStorage and secrets with SecureStore
- Implement a login flow that stores a token and guards protected screens
- Handle loading, error and empty states for network requests
State interview questions
Where should you store an authentication token in a mobile app?
Use encrypted storage backed by the platform, such as Expo SecureStore or the Keychain and Keystore through a library. AsyncStorage is plain, unencrypted storage and suits non-sensitive preferences. Short-lived access tokens with refresh tokens limit the damage if a device is compromised.
Why separate server state from client state?
Server data has its own concerns: caching, staleness, refetching and deduplication. Tools like TanStack Query handle these. Client state, such as a selected tab or form draft, is simple and local. Mixing them in one global store leads to hand-written cache logic and stale screens.
Where State fits in the React Native roadmap
State belongs to the Navigation and State stage (intermediate level), which takes about 19 hours. App flow.
Other units in this stage
Back to the full React Native roadmap