swiftui-router VS SwiftCurrent

It’s kind of hard in native SwiftUI, but this might help: https://github.com/frzi/SwiftUIRouter

The magic is definitely weird. The base views with Body == Never are what get me, they feel impossible to replicate. There's like a few projects around navigation in SwiftUI like SwiftUI Router (Federica Zanetello had this cool blog post on using NavigationLink) but yeah navigation is very magical too. I honestly wish Apple would open up the SwiftUI framework a little, there are efforts to recreate Combine in an open source way, but SwiftUI seems tougher. This early on in SwiftUI it's super frustrating to wait between WWDCs for updates and fixes.

Going to see if I can get data-driven workflows into https://github.com/wwt/SwiftCurrent so that you can define an order of things dynamically from a server. Already having some successes with SwiftUI, so I'm hopeful it'll land (or at least beta) by the end of the month.

If you want to look under the hood to see how we set up all our CI/CD code, you can look here: https://github.com/wwt/SwiftCurrent/tree/main/.github

I'm not sure if you're still looking into this, but this library might help: https://github.com/wwt/SwiftCurrent specifically that it helps you manage workflows through your app. It sounds like you're in UIKit, which there's support for managing at the view controller level. You might want to take a look to see if it gives you any ideas.

Repo: https://github.com/wwt/SwiftCurrent

Working on https://github.com/wwt/SwiftCurrent with a focus on getting SwiftUI support out of beta. I also need to do better in the readme to more convincingly portrait the library's value for managing complicated workflows in your swift apps.