README.md

react-native-screens

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 depenedncy of a full-featured navigation library.

Usage with react-navigation

Screens support is built into stack navigator starting from version [2.14.0][https://github.com/react-navigation/react-navigation/releases/tag/2.14.0) of react-navigation. We plan on adding it to other navigators in near future.

To enable stack navigator to use screens instead of plain RN Views for rendering stack cards follow the steps below:

1. Add this library as a depedency to your project:

yarn add react-native-screens

1. Link native modules this library ships with into your app:

react-native link react-native-screens

If you are not familiar with the concept of linking libraries read on here.

1. Enable screens support before any of your navigation screen renders. Add the following code to your main application file (e.g. App.js):

import { useScreens } from 'react-native-screens';

useScreens();

Note that the above code need to execute before first render of a navigation screen. You can check Example's app App.js file as a reference.

1. Make sure that the version of react-navigation you are using is 2.14.0 or higher

2. 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.

Guide for navigation library authors

If you are building navigation library you may want to use react-native-screens to have a control 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:

<ScreenContainer/>

This component is a container for one or more Screen components. It does not accept other component types are direct children. The role of container is to control which of its children screens should be attached to the view hierarchy. It does that by monitoring active property of each of its children. It it possible to have as many active children as you'd like but in order for the component to be the most effictent we should keep the number of active screens to the minimum. In a case of stack navigator or tabs navigator we only want to have one active screen (the top most view on a stack or the selected tab). Then for the time of transitioning between views we may want to activate a second screen for the duration of transition, and then go back to just one active screen.

<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.

Example

<ScreenContainer>
  <Screen>{tab1}</Screen>
  <Screen active={1}>{tab2}</Screen>
  <Screen>{tab3}</Screen>
</ScreenContainer>

Guide for native component authors

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.

Good example is a map component that shows current user location. When component is on the top-most screen it should register for location updates and display users location on the map. But if we navigate away from a screen that has a map, e.g. by pushing new screen on top of it or if it is in one of a tabs and user just switched to the previous app, we may want to stop listening to location updates.

In order 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:

Navigation lifecycle on iOS

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.

Navigation lifecycle on Android

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.

License

Gesture handler library is licensed under The MIT License.

Credits

This project is supported by amazing people from Expo.io and Software Mansion