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
title: Community-developed Navigators and Libraries
4
-
sidebar_label: Community Navigators and Libraries
2
+
id: navigation-solutions-and-community-libraries
3
+
title: Navigation Solutions and Community Libraries
4
+
sidebar_label: Navigation Solutions and Community Libraries
5
5
---
6
6
7
7
> Libraries listed in this guide may not have been updated to work with the latest version of React Navigation. Please refer to the library's documentation to see which version of React Navigation it supports.
8
8
9
-
# Navigators
9
+
# Solutions built on top of React Navigation
10
10
11
-
## Fluid Transitions
11
+
## Solito
12
12
13
-
Fluid Transitions is a library that provides Shared Element Transitions during navigation between screens using react-navigation.
13
+
A tiny wrapper around React Navigation and Next.js that lets you share navigation code across platforms. Also, it provides a set of patterns and examples for building cross-platform apps with React Native + Next.js.
14
14
15
-
A Shared Element Transition is the visualization of an element in one screen being transformed into a corresponding element in another screen during the navigation transition.
15
+
#### Links
16
16
17
-
The library implements a custom navigator called `FluidNavigator` that makes all this and more possible.
react-navigation-collapsible is a library and a `Higher Order Component` that adjusts your screen options and makes your screen header collapsible.
31
+
## Navio
28
32
29
-
Since react-navigation's header is designed as `Animated` component, you can animate the header by passing `Animated.Value` from your `ScrollView` or `FlatList` to the header.
33
+
A navigation library built on top of React Navigation. It's main goal is to improve DX by building the app layout in one place and using the power of TypeScript to provide route names autocompletion.
Copy file name to clipboardExpand all lines: versioned_docs/version-6.x/pitch.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,5 +19,5 @@ It's useful when considering whether or not to use a project to understand the t
19
19
20
20
- Improvements may require breaking changes. We are working to make ["easy things easy and hard things possible"](https://www.quora.com/What-is-the-origin-of-the-phrase-make-the-easy-things-easy-and-the-hard-things-possible) and this may require us to change the API at times.
21
21
- Some navigators don't directly use the native navigation APIs on iOS and Android; rather, they use the lowest level pieces and then re-creates some subset of the APIs on top. This is a conscious choice in order to make it possible for users to customize any part of the navigation experience (because it's implemented in JavaScript) and to be able to debug issues that they encounter without needing to learn Objective C / Swift / Java / Kotlin.
22
-
- If you need the exact platform behavior, you can choose to use the navigators that use native platform primitives (e.g. [Native Stack Navigator](native-stack-navigator.md)), or use another library that wraps the platform APIs. Read more about these in [Alternatives](alternatives.md) and be sure to understand the tradeoffs that they make before digging in!
22
+
- If you need the exact platform behavior, you can choose to use the navigators that use native platform primitives (e.g. [Native Stack Navigator](native-stack-navigator.md)), or use a different navigation library which provides fully native navigation APIs (e.g. [React Native Navigation](https://github.com/wix/react-native-navigation)).
23
23
- There are other limitations which you may want to consider, see [Limitations](limitations.md) for more details.
title: Community-developed Navigators and Libraries
4
-
sidebar_label: Community Navigators and Libraries
2
+
id: navigation-solutions-and-community-libraries
3
+
title: Navigation Solutions and Community Libraries
4
+
sidebar_label: Navigation Solutions and Community Libraries
5
5
---
6
6
7
7
> Libraries listed in this guide may not have been updated to work with the latest version of React Navigation. Please refer to the library's documentation to see which version of React Navigation it supports.
8
8
9
-
# Navigators
9
+
# Solutions built on top of React Navigation
10
10
11
-
## Fluid Transitions
11
+
## Solito
12
12
13
-
Fluid Transitions is a library that provides Shared Element Transitions during navigation between screens using react-navigation.
13
+
A tiny wrapper around React Navigation and Next.js that lets you share navigation code across platforms. Also, it provides a set of patterns and examples for building cross-platform apps with React Native + Next.js.
14
14
15
-
A Shared Element Transition is the visualization of an element in one screen being transformed into a corresponding element in another screen during the navigation transition.
15
+
#### Links
16
16
17
-
The library implements a custom navigator called `FluidNavigator` that makes all this and more possible.
react-navigation-collapsible is a library and a `Higher Order Component` that adjusts your screen options and makes your screen header collapsible.
31
+
## Navio
28
32
29
-
Since react-navigation's header is designed as `Animated` component, you can animate the header by passing `Animated.Value` from your `ScrollView` or `FlatList` to the header.
33
+
A navigation library built on top of React Navigation. It's main goal is to improve DX by building the app layout in one place and using the power of TypeScript to provide route names autocompletion.
Copy file name to clipboardExpand all lines: versioned_docs/version-7.x/pitch.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,5 +19,5 @@ It's useful when considering whether or not to use a project to understand the t
19
19
20
20
- Improvements may require breaking changes. We are working to make ["easy things easy and hard things possible"](https://www.quora.com/What-is-the-origin-of-the-phrase-make-the-easy-things-easy-and-the-hard-things-possible) and this may require us to change the API at times.
21
21
- Some navigators don't directly use the native navigation APIs on iOS and Android; rather, they use the lowest level pieces and then re-creates some subset of the APIs on top. This is a conscious choice in order to make it possible for users to customize any part of the navigation experience (because it's implemented in JavaScript) and to be able to debug issues that they encounter without needing to learn Objective C / Swift / Java / Kotlin.
22
-
- If you need the exact platform behavior, you can choose to use the navigators that use native platform primitives (e.g. [Native Stack Navigator](native-stack-navigator.md)), or use another library that wraps the platform APIs. Read more about these in [Alternatives](alternatives.md) and be sure to understand the tradeoffs that they make before digging in!
22
+
- If you need the exact platform behavior, you can choose to use the navigators that use native platform primitives (e.g. [Native Stack Navigator](native-stack-navigator.md)), or use a different navigation library which provides fully native navigation APIs (e.g. [React Native Navigation](https://github.com/wix/react-native-navigation)).
23
23
- There are other limitations which you may want to consider, see [Limitations](limitations.md) for more details.
0 commit comments