The survey, conducted by Software Mansion from December 22 to January 20, drew more than 1,800 responses. The hosts caution that promotion through This Week in React and Software Mansion may have skewed the sample. They also note that 36% of respondents had contributed to a React Native library, a share they considered unusually high and not representative of all developers.
State of React Native
Speakers
Callstack host and React Native developers Oscar and Michał discuss the 2022 State of React Native survey with Callstack colleagues on the Coffee Talk podcast.
The hosts discuss gaps between their expectations and reported tool use: MobX appeared under “other” state management, while Axios was used by 89% of respondents despite Fetch being capable of handling requests. They point to web-to-mobile influences including tRPC, Expo Router, React Router, and Tailwind. React Navigation remained the leading navigation choice, and React Native Paper version 5 supported Material Design versions 2 and 3.
The survey showed strong interest in the new architecture and 20% reported usage, though the hosts stress that the respondents were likely more active than the broader developer population. Hermes had 60% usage. About one in five respondents used React Native in brownfield apps, and Flipper led the reported performance profiling tools.
Jest had more than 90% usage, and the hosts highlighted Maestro as an easy-to-use testing tool they expected to grow. Oscar noted that half of respondents used TypeScript exclusively, while 8.5% used JavaScript exclusively. Around 80% were happy or very happy with React Native overall, and 82% were happy with its direction; upgrades, especially for non-Expo libraries, were the leading pain point.
Oscar and Michał welcomed the survey as a first effort to fill a data gap and said they looked forward to future editions. They describe the results as a snapshot of the survey’s particular community and year, with broader participation needed for a more representative picture and year-to-year comparisons.
Takeaways
- Treat ecosystem survey results as a snapshot of respondents, not a census of all React Native developers.
- When evaluating library trends, check who answered and how many people responded to each question.
- Consider Fetch before adding Axios if your project does not need features such as interceptors.
- Track upgrade friction, particularly for non-Expo libraries, when planning React Native maintenance work.
Mentioned in this talk
Search inside this talk
What was claimed 14
- built
“our friends over at Software Mansion conducted one”
YouTube Unverified1 source· Talk
- featureThis Week in React: Helped popularize the survey
“popularized by Sebastian from This Week in React”
YouTube Unverified1 source· Talk
- metricReact Native Radio: Ranked number one in the resources category
“React Native Radio, which is number one”
YouTube Unverified1 source· Talk
- uses
“it uses MobX”
YouTube Unverified1 source· Talk
- integrates withExpo Router integrates with
Next.js
“inspired by Next.js navigation and folder-based routing”
YouTube Unverified1 source· Talk
- metricReact Native Paper: Version 5 is stable
“version 5 is in stable now”
YouTube Unverified1 source· Talk
- featureReact Native Paper: Supports Material Design versions 2 and 3
“support both Material Design version 2 and version 3”
YouTube Unverified1 source· Talk
- metricFabric: 20% usage among survey respondents
“there’s actually 20% usage”
YouTube Unverified1 source· Talk





