Discussion time! For those going pure compose... Are you using Compose navigation arch component or...

# compose

[Colton Idle]

Discussion time!

For those going pure compose... Are you using Compose navigation arch component or something else? And why not just use the arch component?

[julioromano]

I’m using the arch component. I see no reason for using anything else besides needing a cross-platform solution (i.e. one without android SDK dependencies).

[Shakil Karim]

I use this code from @Adam Powell it's working Great for me, Nav compose i feel is less flexible and Opinionated which is not a bad thing, but i prefer to stay away from Nav Compose, Viewmodel https://kotlinlang.slack.com/archives/CJLTWPH7S/p1620399346144500?thread_ts=1620397844.142900&cid=CJLTWPH7S

[eygraber]

I'm skipping the navigation arch component. I tend to not use any arch components because of bad initial experiences with it + an API design that doesn't work for me.

One of the main reasons the API design doesn't work for me is that it trends towards leaning more into Android, while after 11+ years of professional Android development, I've learned that abstracting Android out of your codebase as much as possible is the key to a stable, scalable app.

Also I'd like to keep cross platform on the table without having separate navigation implementations 😅

[Daniel Burnhan]

My team has been trying to figure this out for a production app. The current navigation arch doesn't work well for our app. It basically requires us to implement something similar on IOS since we are using KMM all the way up to the ViewModel level. We have made it work by using multiple navhosts to break up the modules of the application. IMHO the navigation works better in swiftUI