While you will not notice anything changing in the APIs, this refactor paves the way for greatly improving Modifier performance. The October ‘22 release includes a major refactor of how Modifiers work under the hood. We will publish a new version of the BOM every time a Compose artifact has a new stable release, so moving from stable release to stable release is going to be much simpler.īehind the scenes, we’re always working on improving Compose performance. Instead of defining each version separately, which can become cumbersome and prone to errors when library versions start to differ, you now only need to define one BOM version and all Compose library versions will be extracted from that. It will greatly simplify the way you define Compose library versions in your Gradle dependencies block, especially now that we moved the various Jetpack Compose libraries to independent versioning schemes. Our first BOM release, Compose October ‘22, brings support for Staggered Grids, drawing Text directly to Canvas, Pull to Refresh, as well as performance improvements and bug fixes.Ī BOM is a Maven module that declares a set of libraries with their versions. Today we’re releasing a new stable version of Compose, with some exciting features and news.įirst of all, we’ve heard from you how it can be daunting to track versions across different artifacts that might go on different release schedules, so we’re now publishing, together with every Stable release of any of the Compose artifacts, a Bill of Materials, or BOM, to make your life easier.
It outlines how and where to start, and shows the areas of development where Compose can bring huge added value. Since this year’s Google I/O, the number of top 1000 apps on Google Play using Compose has increased by 50%! To help your team follow in the footsteps of the teams at Lyft, Zepeto, and others, we published a guide on How to Adopt Compose for your Team. It’s great to see how these teams experience faster development cycles, and also feel their UI code is more concise and readable.
0 kommentar(er)
