A modern programming language that makes developers happier.

kotlinlang

Hi all - we have released <https://developer.android.com/jetpack/androidx/releases/wear-compose#1.5.0-alpha10|1.5.0-alpha10> with support for overscroll and prefetching in TransformingLazyColumn and updates to SwipeToReveal and Pager. Also, note that SwipeDismissableNavHost now uses PredictiveBack only in API 36 onwards.

In the Material3 library, we have released <https://developer.android.com/jetpack/androidx/releases/wear-compose#1.0.0-alpha33|1.0.0-alpha33>. The ArcLarge, ArcMedium and ArcSmall typographies are intended for use with curved text and are now explicitly CurvedTextStyle. Dialogs now use AppScaffold (when available) to show themselves, instead of launching compose.ui.window.Dialog, which gives a significant reduction in Jank. This release also includes improvements to APIs such as SwipeToReveal, LevelIndicator, button shapes classes, CircularProgressIndicator.

We will be upgrading to Kotlin 2.0 for the wear compose libraries in the next release cycle, which will be another alpha release, and will include a small number of new APIs. Subsequently, as soon as all API feedback has been resolved, we look forward to cutting our first 1.5 beta release (to include the material3 library).

Why is `PredictiveBack` within `SwipeDismissableNavHost` getting bumped to API 36? Are there any constraints that prevent it from working on 35?
I was looking internally at how `SwipeDismissableNavHost` works because I would like to implement horizontal navigation transitions when navigating through screens, and I saw that in the `PredictiveBack`, even though the transitions are not customizable, at least they are slide-in horizontal ones. So I was kind of sold on not implementing anything custom and wait for API 35 to get officially released to get the newer version.

<@U01NBR4L37T> from the playstore console, it recommends to the wearos app module that uses the compile 34 version (i dont know why), i think that while in alpha, we must be careful about using the sdk versions (most recent: 35 and above)

Yes, I get that, 35 is not out yet. However I thought that the `PredictiveBack` navigation was going to be in for 35, while because of this change it seems it will be postponed to 36.

Hi Marcel, no technical constraints, just not planned to be supported in API 35, I'm afraid.