React Native Best Practices

Chapter 1 of 8 · 5 practices · 5 min · 4-question quiz

Project setup and upgrades

How to start a React Native project so it stays on the supported path: a framework, the New Architecture, Hermes V1 and the strict TypeScript API, plus a habit of small upgrades.

Start: Start new apps with a framework such as Expo

5 practices in this chapter

  1. 1Start new apps with a framework such as ExpoThe React Native docs recommend building new apps with a framework, and name Expo as the example. A framework gives you navigation, access to native APIs, native dependency handling and a build…
  2. 2Treat the New Architecture as the only architectureSince React Native 0.82 the New Architecture is the only runtime option, and every release since has removed more legacy code. In 0.84 iOS builds exclude legacy architecture code by default, and in…
  3. 3Run on Hermes V1 and leave it onHermes has been the default JavaScript engine since React Native 0.70, and Hermes V1 became the default on both iOS and Android in 0.84. The release post describes improvements to both the compiler…
  4. 4Import only from the react-native root with the strict TypeScript APIIn React Native 0.87 the Strict TypeScript API is the default. Types are generated from React Native's source instead of being written by hand, and they cover only what react-native exports from…
  5. 5Upgrade one minor version at a time with the Upgrade HelperReact Native ships a new minor release every couple of months, and only the latest few are supported. When 0.87 came out in August 2026, 0.84.x moved to unsupported. Falling three or four versions…

Check yourself on this chapter

4 questions, right here once you are signed in. Your progress is saved as you read.

Sign up for the quiz