use react-navigation!

[chandu0101]

https://microsoft.github.io/reactxp/docs/components/navigator.html

my guess is that when you guys built this there is no react-navigation, is it possible to adopt https://reactnavigation.org/ instead of creating one more navigation lib/API, we already have plenty now ;)

[kaiyes]

Please . Sticking to React Navigation will be a god send.

[saint4eva]

It may not be ideal as React Navigation only has support for Android and iOS - there is no support for UWP...

[dryganets]

Regarding the navigation framework, it was a hard decision for us.
Initially, we used React Native's Navigator but the animations were not smooth enough.

In order to fix this we considered two libraries:
React Native's NavigationExperimental and https://reactnavigation.org/.

We ended up switching to NavigationExperimental because it required a minimum amount of change to the framework and it met our performance goals.

If you want to use a different navigation library, it's possible to extend
https://github.com/Microsoft/reactxp/blob/master/src/native-common/NavigatorCommon.ts

similar to how we wrote delegates for Navigator and NavigationExperimental:
https://github.com/Microsoft/reactxp/blob/master/src/native-common/NavigatorStandardDelegate.tsx

https://github.com/Microsoft/reactxp/blob/master/src/native-common/NavigatorExperimentalDelegate.tsx

Unfortunately, ExperimentalDelegate does not currently work with the official version of React Native. In order to support our app's requirements, we made some enhancements to NavigationExperimental which haven't yet been contributed back to Facebook's React Native repo. The primary enhancements are a fade navigation animation (similar to Navigator's) and the ability to provide custom navigation animations.

Also, ExperimentalNavigator got deprecated and pulled out from the ReactNative repository, so likely we will move our implementation to the separate reactxp plugin.

Our goal was to create a cross-platform framework. Currently, Facebook's NavigationExperimental seems like a reasonable choice as it results in smooth animations in our app and we are able to share navigation code between all platforms Skype is working on.

[fotiDim]

@dryganets whatever your reasons back then the way to go now is react navigation. If it doesn't support UWP you can consider contributing that part maybe.

[dryganets]

@fotiDim we have nothing to argue about 🤣

I took a closer look at the https://github.com/react-community/react-navigation.
It's the framework we likely will use once we move to react-native 0.42. I can't give any timeframe now as it could change with our project priorities.

In fact, https://reactnavigation.org/ just an ExperimentalNavigation pulled out of the facebook repository into the community one.

I was likely looking into the different library before. It was fully native and that was a limitation for us as we need full control over the navigation stack to have a compatibility with the web/desktop version.

The ReactNative community is fluid and fast growing. Projects often change authors and names :)

We are not trying to limit anyone. Navigation framework choice it's probably the hardest decision in case you are building a cross-platform app as many future architectural decisions would depend on it.

[smkhalsa]

@dryganets any update on when we can expect the update to react-navigation?

[quantuminformation]

I started a RN app using react-navigation, but I think I will wait a bit before continuing as I would like to build with XP. Exciting stuff!

[dryganets]

@smkhalsa, we don't have exact plans for this enhancement yet, sorry.

[afilp]

@dryganets Can we use react-native-router-flux with reactXP?

[quantuminformation]

Any updates guys?

[quantuminformation]

I had to google UWP, not something that most js devs would worry about..