WhoBuilt

State of React Native

Feb 22, 2023· 37 min· 2.0K views·Watch on YouTube

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.

Who answered the survey

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.

Libraries and web influences

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.

React Native features and app practices

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.

Testing, languages, and developer sentiment

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.

A useful but limited snapshot

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

Show all 14 facts

Related talks