This project aims to expose native navigation container components to React Native. It is not designed to be used as a standalone library but rather as a dependency of a full-featured navigation library.
Screens are already integrated with the React Native's most popular navigation library react-navigation and Expo. Read usage guide depending on if you are using Expo or not.
Since version 2.0.0 react-native-screens requires RN v0.60+.
Usage with react-navigation
Screens support is built into react-navigation starting from version 2.14.0 for all the different navigator types (stack, tab, drawer, etc). We plan on adding it to other navigators shortly.
To configure react-navigation to use screens instead of plain RN Views for rendering screen views, follow the steps below:
- Add this library as a dependency to your project:
# bare React Native project
yarn add react-native-screens
# if you use Expo managed workflow
expo install react-native-screens- Enable screens support before any of your navigation screens renders. Add the following code to your main application file (e.g. App.js):
import { enableScreens } from 'react-native-screens';
enableScreens();Note that the above code needs to execute before the first render of a navigation screen. You can check the Example's app App.js file as a reference.
-
Make sure that the version of react-navigation you are using is 2.14.0 or higher
-
You are all set 🎉 – when screens are enabled in your application code react-navigation will automatically use them instead of relying on plain React Native Views.
To take advantage of the native stack navigator primitive for React Navigation that leverages UINavigationController on iOS and Fragment on Android, please refer to the README in react-native-screens/native-stack. Note that this depends on React Navigation v5.
Interop with react-native-navigation
React-native-navigation library already uses native containers for rendering navigation scenes so wrapping these scenes with <ScreenContainer> or <Screen> component does not provide any benefits. Yet if you would like to build a component that uses screens primitives under the hood (for example a view pager component) it is safe to use <ScreenContainer> and <Screen> components for that as these work out of the box when rendered on react-native-navigation scenes.
This library should work out of the box with all existing react-native libraries. If you experience problems with interoperability please report an issue.
If you are building a navigation library you may want to use react-native-screens to have control over which parts of the React component tree are attached to the native view hierarchy. To do that react-native-screens provides you with two components documented below:
This component is a container for one or more Screen components.
It does not accept other component types as direct children.
The role of the container is to control which of its children's screens should be attached to the view hierarchy.
It does that by monitoring the active property of each of its children.
It is possible to have as many active children as you'd like but for the component to be the most efficient, we should keep the number of active screens to a minimum.
In the case of a stack navigator or tabs navigator, we only want to have one active screen (the topmost view on a stack or the selected tab).
While transitioning between views we may want to activate a second screen for the duration of the transition, and then go back to just one active screen.
This component is a container for views we want to display on a navigation screen.
It is designed to only be rendered as a direct child of ScreenContainer.
In addition to plain React Native View props this component only accepts a single additional property called active.
When active is set to 0, the parent container will detach its views from the native view hierarchy.
Otherwise, the views will be attached as long as the parent container is attached too.
<ScreenContainer>
<Screen>{tab1}</Screen>
<Screen active={1}>{tab2}</Screen>
<Screen>{tab3}</Screen>
</ScreenContainer>Screen stack component expects one or more Screen components as direct children and renders them in a platform-native stack container (for iOS it is UINavigationController and for Android inside Fragment container). For Screen components placed as children of ScreenStack the active property is ignored and instead the screen that corresponds to the last child is rendered as active. All types of updates done to the list of children are acceptable when the top element is exchanged the container will use platform default (unless customized) animation to transition between screens.
StackScreen extends the capabilities of the Screen component to allow additional customizations and to make it possible to handle events such as using hardware back or back gesture to dismiss the top screen. Below is the list of additional properties that can be used for Screen component:
A callback that gets called when the current screen is dismissed by hardware back (on Android) or dismiss gesture (swipe back or down). The callback takes no arguments.
Allows for the customization of how the given screen should appear/disappear when pushed or popped at the top of the stack. The following values are currently supported:
"default"– uses a platform default animation"fade"– fades screen in or out"flip"– flips the screen, requiresstackPresentation: "modal"(iOS only)"none"– the screen appears/disappears without an animation
Defines how the method that should be used to present the given screen. It is a separate property from stackAnimation as the presentation mode can carry additional semantic. The allowed values are:
push– the new screen will be pushed onto a stack which on iOS means that the default animation will be slide from the side, the animation on Android may vary depending on the OS version and theme.modal– Explained below.transparentModal– Explained below.containedModal– Explained below.containedTransparentModal– Explained below.fullScreenModal– Explained below.formSheet– Explained below.
For iOS:
modalwill useUIModalPresentationAutomaticon iOS 13 and later, and will useUIModalPresentationFullScreenon iOS 12 and earlier.fullScreenModalwill useUIModalPresentationFullScreenformSheetwill useUIModalPresentationFormSheettransparentModalwill useUIModalPresentationOverFullScreencontainedModalwill useUIModalPresentationCurrentContextcontainedTransparentModalwill useUIModalPresentationOverCurrentContext
For Android:
modal, containedModal, fullScreenModal, formSheet will use Screen.StackPresentation.MODAL.
transparentModal, containedTransparentModal will use Screen.StackPresentation.TRANSPARENT_MODAL.
The config component is expected to be rendered as a direct child of <Screen>. It provides an ability to configure native navigation header that gets rendered as a part of the native screen stack. The component acts as a "virtual" element that is not directly rendered under Screen. You can use its properties to customize platform native header for the parent screen and also render react-native components that you'd like to be displayed inside the header (e.g. in the title are or on the side).
Along with this component's properties that can be used to customize header behavior, one can also use one of the below component containers to render custom react-native content in different areas of the native header:
ScreenStackHeaderCenterView– the children will render in the center of the native navigation bar.ScreenStackHeaderRightView– the children will render on the right-hand side of the navigation bar (or on the left-hand side in case LTR locales are set on the user's device).ScreenStackHeaderLeftView– the children will render on the left-hand side of the navigation bar (or on the right-hand side in case LTR locales are set on the user's device).
Below is a list of properties that can be set with ScreenStackHeaderConfig component:
hidden
When set to true the header will be hidden while the parent Screen is on the top of the stack. The default value is false.
Controls the color of items rendered on the header. This includes a back icon, back text (iOS only) and title text. If you want the title to have a different color use titleColor property.
A string representing screen title that will get rendered in the middle section of the header. On iOS, the title is centered on the header while on Android it is aligned to the left and placed next to the back button (if one is present).
Customize the font family to be used for the title.
Customize the size of the font to be used for the title.
Allows for setting text color of the title.
Controls the color of the navigation header.
Boolean that allows for disabling drop shadow under navigation header. The default value is true.
If set to true the back button will not be rendered as a part of the navigation header.
If set to true the back button will also be rendered while using headerLeft function.
When set to false the back swipe gesture will be disabled when the parent Screen is on top of the stack. The default value is true.
When set to true, it makes native navigation bar on iOS semi-transparent with blur effect. It is a common way of presenting a navigation bar introduced in iOS 11. The default value is false.
Allows for controlling the string to be rendered next to the back button. By default, iOS uses the title of the previous screen.
Allows for customizing font family to be used for the back button title on iOS.
Allows for customizing font size to be used for the back button title on iOS.
When set to true it makes the title display using the large title effect.
Customize the font family to be used for the large title.
Customize the size of the font to be used for the large title.
If you are adding a new native component to be used from the React Native app, you may want it to respond to navigation lifecycle events.
A good example is a map component that shows the current user location. When the component is on the top-most screen, it should register for location updates and display the user's location on the map. But if we navigate away from a screen that has a map, e.g. by pushing a new screen on top of it or if it is in one of the tabs, and the user just switched to the previous app, we may want to stop listening to location updates.
To achieve that, we need to know at the native component level when our native view goes out of sight. With react-native-screens you can do that in the following way:
In order for your native view on iOS to be notified when its parent navigation container goes into background override didMoveToWindow method:
- (void)didMoveToWindow
{
[super didMoveToWindow];
BOOL isVisible = self.superview && self.window;
if (isVisible) {
// navigation container this view belongs to became visible
} else {
// we are in a background
}
}You can check our example app for a fully functional demo see RNSSampleLifecycleAwareView.m for more details.
On Android, you can use LifecycleObserver interface which is a part of Android compat library to make your view handle lifecycle events. Check LifecycleAwareView.java from our example app for more details on that.
In addition to that, you will need to register for receiving these updates. This can be done using LifecycleHelper.register.
Remember to call LifecycleHelper.unregister before the view is dropped.
Please refer to SampleLifecycleAwareViewManager.java from our example app to see what are the best ways of using the above methods.
React native screens library is licensed under The MIT License.
This project is supported by amazing people from Expo.io and Software Mansion
