NavigationBackport VS swift-composable-architecture

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

TCA for short. Very scalable, quite promising, quite popular. A decent alternative for MVVM enhanced by the Clean Architecture. You can learn more about it in a Point-Free tutorial and on GitHub.

🙏 Built with SwiftUI and The Composable Architecture (TCA): This isn’t a feature, but I just want to express my gratitude to the creators and maintainers of these two frameworks, which have played a huge part in making me fall in love with iOS development.

Razliciti alternativni frameworci i arhitekture - Recimo, na pamet mi padaju Composable Architecture (https://github.com/pointfreeco/swift-composable-architecture) i RIBs arhitektura (https://github.com/uber/RIBs). Ok, ove arhitekture resavaju neke probleme. Ali da li problemi koje te arhitekture resavaju solidan developer ne moze sam da resi bez vendor locka za kreatore tih arhitektura. Jesu one open-source, ali meni je rizik da se vezujem za bilo sta sto sutra moze da prestane da se odrzava.

I came across this post discussing MVM, MVVM, MVP, and composable architecture.

At a minimum, Composable Architecture, and now Dependencies from Point-Free.

I’ve built a couple of apps with this framework: https://github.com/pointfreeco/swift-composable-architecture

While there are apps that use a Redux-style architecture, the arch is still in its infancy in the community. There are a number of implementations each with their own take on Redux. TCA is probably the one with the most name recognition and documentation.

Learn it if the project at hand requires it. A lot of older, more mature apps will still use UIKit, so it’s likely if you plan to work an iOS developer job that you will need it. But it’s getting to the point where a lot of the forward thinking shops are already starting to integrate SwiftUI. (Me being one of them) which, btw, a lot of people will say SwiftUI isn’t quite there yet, and I mostly disagree. SwiftUI is good for a great many use cases. Yes, there are still pain points, but you can write most of the apps you’d need to write in SwiftUI. And there are great architectural frameworks out there that actually give SwiftUI an opinionated way to structure apps that is testable and maintainable. Check out pointfreeco’s The Composable Architecture (https://github.com/pointfreeco/swift-composable-architecture)