A modern programming language that makes developers happier.

kotlinlang

Hey all, small announcement :mega: : with the *Jetpack Compose 1.8. beta01 release*, you may notice that a significant number of APIs that were previously experimental, have been graduated to stable.

:heart_hands:  We care a lot about providing a high quality and cohesive API surface for Compose, while also adhering to strict binary compatibility across releases, to ensure upgrades are relatively straightforward. We’ve heard from the community that APIs that have been experimental for longer are harming the Compose experience, which is why we are *decreasing our usage of experimental APIs moving forward*.

In 1.8, we will stabilize all experimental APIs in the Foundation and UI modules that have been unchanged for more than one full release cycle, and we plan to do the same for more modules in the future.

As part of this effort, we have also identified APIs added in recent releases that are not what we believe we should commit to long term. This has led to the decision to *deprecate the experimental `ContextualFlowRow` and `ContextualFlowColumn`*, added in 1.7. It is possible for developers to implement their particular use cases, while we work on a plan for future components that can cover these functionalities better.

The related APIs `FlowRow` and `FlowColumn` will become stable, however *without the new `overflow` parameter* added in the last release.

Please reach out to us if you have any questions or concerns, thanks! :gratitude-thank-you:

Have you considered putting `ContextualFlow` components into the Accompanist repo? I'm not actually sure when the API is a good fit for Accompanist and when it should be in Compose directly

We try to be very strict with accompanist and not just shove anything we’re unsure of there :confused:, and especially since we want to support this specific use case in a better way, we opted for this move

<@U030M71HBT4> what will the alternative to `FlowXOverflow.Visible` be? I want my content to overflow but I dont want it to be clipped.

This is great news.   On a related note, if a lot of experimental stuff is going away, does anyone know of a good way to identify the annotations in your code that you no longer need?

Also, is there a list of the APIs going stable in 1.8 that were experimental in 1.7 (or earlier)?

<@U5MF219BP> Places with unnecessary annotations will show a warning
I think you could run a full-project analysis in the IDE to get all of them at once

We're on a huge project with a lot of warnings.  It's a huge thing to sift through, but hopefully there's something useful we can grep for.