Helm VS NavigationBackport

At the moment I am considering FlowStacks (https://github.com/johnpatrickmorgan/FlowStacks) that seems to do the trick, but I was wondering if there are any other options one would recommend. I also know of Helm (https://github.com/valentinradu/Helm) but it feels overly verbose and tedious to set up for me.

Have a look at Helm. It's a bit harder to set up (it relies on a graph to describe the relationships between dynamic views, a bit like storyboards, but it does support deeplinking (it's actually possible to fully restore the navigation state, overlapping views included)

still you can use it via this library by default it suppourt iOS 14+ https://github.com/johnpatrickmorgan/NavigationBackport

My team is working on updating our SwiftUI app’s navigation to use this package: https://github.com/johnpatrickmorgan/NavigationBackport

Pretty much the same as you, just that I bit the bullet and didn't give up until I managed to get something decent on the navigation part using native SwiftUI tools. NavigationBackport + SwiftUINavigator has been surprisingly tolerable as long as you don't have a need for too many modal views or complex deeplink flows.

If you want to do it the SwiftUI way, you can try using the NavigationStack backport which gives you support all the way back to iOS 14. I am using it right now and it's ok with the addendum that you need to do some gymnastics to bubble up a navigation destination from one of the sub-sub-sub children of the view owning the navigation stack.

There’s a back port of the nav view at https://github.com/johnpatrickmorgan/NavigationBackport