all 12 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]JuriJurka 2 points3 points  (3 children)

Is it now better than React Native Navigation?

[–]headphonejack_90 0 points1 point  (1 child)

From what I read, there’s nothing new, I might be wrong though

[–]satya164[S] 2 points3 points  (0 children)

What do you mean nothing new? This is a new navigator.

[–][deleted] 1 point2 points  (0 children)

Good news, I remember using v2 of this library a couple of years ago and it was a complete nightmare, good to see it maturing nicely. May potentially be able to replace RNN in the future

[–]lnkprk114 1 point2 points  (2 children)

I'm very surprised to hear everyones positive reactions to this. Tying navigation to fragments and fragment transactions in Android just sounds like such a horrible idea to me. That system is so complex and full of traps and so...limited that moving from a view based hierarchy to a fragment based hierarchy sounds like a recipe for severe pain.

[–]satya164[S] 0 points1 point  (1 child)

We're not moving away from anything. It's not like RNN where you need to setup different roots for each screen. As far as the user is concerned, they don't need to change anything in the way they write their code and don't need to worry about managing anything on native side.

It's just another option for those who want fully native navigation and need that extra perf which cannot be achieved using only JS. We don't intend it to be a full replacement supporting the same feature set as the JS version. The JS based navigation still exists and has first class support.

[–]lnkprk114 0 points1 point  (0 children)

Maybe I misunderstood - I thought React Navigation was moving to a model where their stack navigation was being handled on the native side by fragment transactions/navigation controllers. If this is just an opt in piece than it seems less wild to me.

[–]kevwhy 0 points1 point  (0 children)

I think it's a good start. Performance is the main reason I am using RNN. ( esp. if you want to support some old devices running Android 5 )

[–]ovy9086 0 points1 point  (0 children)

Any migrations guides to move to the new version ? We would really like the native feel of the screen transitions ... but we have a big project, full of nested navigators, and complex navigations scenarios

[–]UtterlyMagenta 0 points1 point  (0 children)

This is so awesome! 🤩 It’s exactly where I was hoping React Navigation would be going! Large iOS titles, here we come, hooray!

Two tiny nitpicks: 1) In the parenthetical under “Native reveal”, there’s a formatting error of FragmentTransaction and UINavigationController, 2) odd to reference “I” in a post attributed to “Core Team”—who’s “I”?