Respond to native routing versus reactive navigation

I'm going to choose whether to use React Navigation or use React Router Native , I thought that React Navigation is better, but then I found some reviews like this to respond to a navigation problem , ps: React Router Native has a similar API for React Router , which seems very simple, I'm still lost! I need an advice

+4
source share
1 answer

In my experience, React Navigation works like a charm. It uses its own layouts if you do not want to create your own, and you can customize them through the details at your discretion. It also allows you to navigate inside functions without the need for redux actions, which, in my opinion, are needed in React Router.
The main problem with React Navigation is its documentation, which is pretty dull. It has no complicated examples, only simple things, so you need to hide a bit to do something if your application starts to become complex, with many sockets.
Despite this, the only difficult task that I really had with React Navigation was when I had a stack navigator (2nd) inside the drawer navigator that was nested in the main stack navigator (1st), which then didn't let me change the main title from the 2nd Stack Navigator. This could be circumvented by placing the 2nd stack navigator directly inside the main one.

+1
source

Source: https://habr.com/ru/post/1687202/


All Articles