Hi, Is compose multiplatform navigation coming with the next stable 1.6.10 release? Is there any tim...

# compose

[mohamed rejeb]

Hi,
Is compose multiplatform navigation coming with the next stable 1.6.10 release? Is there any timeline for it?

[Ivan Matkov]

yes, but it's won't be "stable". First alpha will be available later today (🤞)

[Stylianos Gakis]

Will it try to ship along with the type-safe APIs in this stage, or is that coming later?

Also how about deep link support, is that coming with it, or perhaps soon?

[Stylianos Gakis]

And as a side question, I see that the SeekableTransitionState usage here is commented out for now https://github.com/JetBrains/compose-multiplatform-core/blob/5a698ba86e2cc1af653e8[…]se/src/commonMain/kotlin/androidx/navigation/compose/NavHost.kt, is that because CMP is using the old API where SeekableTransitionState was taking in two parameters but the google compose API no longer has that shape? I was trying to get something like that to work myself too in PreCompose and figured it’s just crashing because of this API mismatch between the two.

[Ivan Matkov]

I didn't merge type-safe APIs yet. Deep-link out of first version too

Will do it soon

[Stylianos Gakis]

Sounds reasonable, thank you 😊

[Ivan Matkov]

> he SeekableTransitionState usage here is commented out for now
As I remember it was because of lack of multiplatform (Predictive)BackHandler

[Stylianos Gakis]

Even without it, the internal animation can still be driven by a SeekableTransitionState theoretically right? Even if practically it would for now only ever be used to go to the start or the end of the animation until the multiplatform predictive back handler is added

[mohamed rejeb]

Great, I will give it a try!