Skip to content

State management

What state management solutions do you use in your React Native apps?

State management ratios over time

Jotai
Legend State
MobX
MobX State Tree
React built-ins
Recoil
Redux
Redux Toolkit
XState
Zustand

Mode:

View:

0%
20%
40%
60%
80%
100%
2022
2023
2024
0%
20%
40%
60%
80%
100%

State management experience & sentiment

Group by:

Sort by:

1

91.5%
5.5%
2,434
2

71%
25.9%
2,440
3

61.1%
31.4%
7.3%
2,421
4

46.7%
38.3%
14.5%
2,413
5

17.3%
61.9%
20.4%
2,429
Experience
  • Used it: Respondents who have used an item.
  • Heard of it: Respondents who have heard about an item, but haven't used it.
  • Never heard of it: Respondents who have never heard about an item.
Sentiment
  • Positive: Respondents who are interested in learning more about a technology; or are willing to use it again.
  • Neutral: Responents who did not indicate any sentiment about a technology.
  • Negative: Respondents who are not interested in learning more about a technology; or have used it and had a negative experience.

Other solutions

Other state management solutions
Freeform
What other solutions not mentioned above have you used in your React Native apps?
0%
8%
16%
25%
33%
41%
1

tanstack_query

52
2

valtio

14
3

apollo_client

12
4

stan_js

8
5

Other Answers

47
0%
8%
16%
25%
33%
41%
% of question respondents

State management pain points

State management pain points
Freeform
What pain points have you encountered with state management in your React Native projects? If applicable, point out the specific solution and its problems.
0%
10%
20%
30%
40%
50%
1

Synchronization issues

2

Excessive re-renders

3

4

Excessive complexity

5

Excessive boilerplate

6

Performance

7

Context

8

Debugging

9

Architecture

10

Global state management

0%
10%
20%
30%
40%
50%
% of question respondents
Zustand continues its rise as the go-to modern state management library, offering a refreshingly simple developer experience. Besides the React built-ins, no other libraries leaves developers with such a positive experience after using it. Which also shows that using the Context API is still extremely popular, and actually an acceptable solution for the needs of most small apps. For server state, TanStack Query remains unmatched—essential for any React Native app interacting with APIs. The biggest challenge for state management remains synchronisation. AsyncStorage isn’t up to the challenges of today compared to solutions like MMKV, and especially. With the growing shift toward local-first approaches, developers are craving seamless app-to-backend sync mechanisms."
Simon Grimm
Galaxies.dev founder
We asked members of the React Native community to share their opinions about the results

On-device storage

What on-device storage solutions do you use in your React Native apps?
0%
17%
34%
50%
67%
84%
1

83.82%
1,938
2

44.16%
1,021
3

22.49%
520
4

17.73%
410
5

9.73%
225
6

7.57%
175
7

7.4%
171
8

expo-secure-store

0.99%
9

op-sqlite

0.52%
10

Other Answers

2.36%
55
0%
17%
34%
50%
67%
84%
% of question respondents

Local-first app architecture

Are you familiar with local-first app architecture pattern?
Group by:
1

25.7%
56.6%
17.3%
2,353

Local-first app architecture

Local-first app architecture

View:

0%
20%
40%
60%
80%
100%
2023
2024
0%
20%
40%
60%
80%
100%