| id | getting-started |
|---|---|
| title | Getting started |
| sidebar_label | Getting started |
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';
The Fundamentals section covers the most important aspects of React Navigation. It should be enough to build a typical mobile application and give you the background to dive deeper into the more advanced topics.
Prior knowledge
If you're already familiar with JavaScript, React and React Native, you'll be able to get moving with React Navigation quickly! If not, we recommend gaining some basic knowledge first, then coming back here when you're done.
Minimum requirements
react-native>= 0.72.0expo>= 52 (if you use Expo Go)typescript>= 5.0.0 (if you use TypeScript)
You can use the React Navigation template to quickly set up a new project:
npx create-expo-app@latest --template react-navigation/templateThis creates a new Expo project with React Navigation already installed and configured. See the project's README.md for more information, then move on to Setting up React Navigation.
The @react-navigation/native package contains the core functionality of React Navigation.
In your project directory, run:
npm install @react-navigation/nativeNext, install the dependencies used by most navigators: react-native-screens and react-native-safe-area-context.
In your project directory, run:
npx expo install react-native-screens react-native-safe-area-contextThis will install versions of these libraries that are compatible with your Expo SDK version.
In your project directory, run:
npm install react-native-screens react-native-safe-area-contextIf you're on a Mac and developing for iOS, install the pods via Cocoapods to complete the linking:
npx pod-install iosreact-native-screens requires one additional configuration to properly work on Android.
Edit MainActivity.kt or MainActivity.java under android/app/src/main/java/<your package name>/ and add the highlighted code:
// highlight-start
import android.os.Bundle
import com.swmansion.rnscreens.fragment.restoration.RNScreensFragmentFactory
// highlight-end
// ...
class MainActivity: ReactActivity() {
// ...
// highlight-start
override fun onCreate(savedInstanceState: Bundle?) {
supportFragmentManager.fragmentFactory = RNScreensFragmentFactory()
super.onCreate(savedInstanceState)
}
// highlight-end
// ...
}// highlight-start
import android.os.Bundle;
import com.swmansion.rnscreens.fragment.restoration.RNScreensFragmentFactory;
// highlight-end
// ...
public class MainActivity extends ReactActivity {
// ...
// highlight-start
@Override
protected void onCreate(Bundle savedInstanceState) {
getSupportFragmentManager().setFragmentFactory(new RNScreensFragmentFactory());
super.onCreate(savedInstanceState);
}
// highlight-end
// ...
}This avoids crashes related to View state not being persisted across Activity restarts.
React Navigation doesn't yet support Android's predictive back gesture, so you need to disable it for the system back gesture to work properly.
In AndroidManifest.xml, set android:enableOnBackInvokedCallback to false in the <application> tag (or <activity> tag to opt-out at activity level):
<application
// highlight-next-line
android:enableOnBackInvokedCallback="false"
>
<!-- ... -->
</application>When using React Navigation, you configure navigators in your app. Navigators handle transitions between screens and provide UI such as headers, tab bars, etc.
There are 2 ways to configure navigators:
-
Static configuration Recommended
Object-based configuration with automatic TypeScript types and deep linking. Supports static screen lists with dynamic navigator options.
-
Component-based configuration with significantly more boilerplate. Supports dynamic screen lists and navigator options.