You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: versioned_docs/version-7.x/native-stack-navigator.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,10 @@ Native Stack Navigator provides a way for your app to transition between screens
16
16
17
17
This navigator uses the native APIs `UINavigationController` on iOS and `Fragment` on Android so that navigation built with `createNativeStackNavigator` will behave exactly the same and have the same performance characteristics as apps built natively on top of those APIs. It also offers basic Web support using [`react-native-web`](https://github.com/necolas/react-native-web).
18
18
19
-
A few things to keep in mind:
20
-
* While `@react-navigation/native-stack` offers native performance and exposes native features such as large title on iOS etc., it may not be as customizable as [`@react-navigation/stack`](stack-navigator.md) depending on your needs.
21
-
* While `@react-navigation/stack` renders only views that are visible, `@react-navigation/native-stack` will require all views to be kept in memory regardless of visibility. In particular, this is important if your stack model allows the user to place a new screen on top of the stack infinitely. This may lead to out-of-memory issues.
19
+
A few things to keep in mind:
20
+
21
+
- While `@react-navigation/native-stack` offers native performance and exposes native features such as large title on iOS etc., it may not be as customizable as [`@react-navigation/stack`](stack-navigator.md) depending on your needs.
22
+
- While `@react-navigation/stack` renders only views that are visible, `@react-navigation/native-stack` will require all views to be kept in memory regardless of visibility. In particular, this is important if your stack model allows the user to place a new screen on top of the stack infinitely. This may lead to out-of-memory issues.
22
23
23
24
So if you need more customization than what's possible in this navigator, or if memory becomes a concern, consider using `@react-navigation/stack` instead - which is a more customizable JavaScript based implementation.
0 commit comments