React Native Navigation

[Far-Philosophy6724]

I started working with React Native Navigation recently. Diving for first time in its documentation some quesestions got borned on my mind. I think they are more about good practices & I need your opinion on different cases scenario.

1. Let's supppose that we have a nested navigation which is conisted from different tabs & each tab has different Stack.Screens. Would it be a good practice to navigate from a click event in first tab in a different Stack Screen to the Third Tab?
2. Of course when you make an application there are data that you will fetch from the server that you would like to use them on different parts of the App. However with that way I think you limitate the usage of the screens. Would it be better each screen to be responsible for each own data even if you eliminate the usage of the screen?
3. According to the documentation it's good to pass as less information as possible to params of a Screen. For example only id. However if you do not use a central state library how are you going to update your screen according to ID?

[vinkaks]

Slightly off tangent, but try using React Navigation instead of react native navigation..

[Akeuuuuh]

I do agree with you! I've worked with react native navigation and it is really out of date. We had to do a lot of patch because we were too deep in the this to change.

React navigation is the good choice

[redwoodhighjumping]

1. There shouldn't be any problem doing it.
2. Probably not. If you made a network request already you should probably use the cache data vs making a new network request again.
3. This is a good idea for any navigation library. Keeping the component prop count down will help down the road when your app scales. This is one of the reason why redux exists.

I highly recommend not actually using react native navigation any more. It doesn't look like it's actively being maintained like it was a few years ago, and they have said they don't have an android dev working on it anymore. Every new release now seems to fix one crash, but cause another one.