When is proper navigation support expected to come...

# compose

[aryk]

When is proper navigation support expected to come out?

[Adam Powell]

If you mean integration with the arch components nav library, not sure. We don't consider it blocking for alpha, beta or 1.0, partially because it's fairly straightforward to create a ComposableFragment and use that with the existing library. We're focusing on the fundamentals that make such integrations easy to write first

[Adam Powell]

If you check out the incoming changes, you'll see that the initial support for integrating with saved instance state from compose is landing, which is an important step for it

[Adam Powell]

From there, it's mostly a matter of the feature set that matters to you. If you want a stack and back button navigation, that's fairly straightforward to put together today. I think at least one community member here has published a compose-centric navigation library so far

[Adam Powell]

I'd like to see the arch components library integration also support the other fragment navigators alongside compose in the same navigation graph for robustness, but that will take some additional time given the size of the surface area to support, the Android studio integration, etc.

[molikto]

I've been using android.app.Activity as router. Because compose based navigation doesn't have nice animations now... Also I don't see it necessoary to pull in the buck of appcompat jars.