Issue #24
Whatโs up, geeks ๐ค
Took some vacation last week, but now itโs time to get back to the weekly Newsletter ๐๏ธ
Hereโs what I have for you today ๐
If these links don't work in your email client, try reading this issue on my website.
1) The K2 Compiler is going stable in Kotlin 2.0
2) Android library compatibility and public API management with binary compatibility validator
3) Space Hoisting: Should I use the padding Modifier or the Spacer composable?
4) Leveraging the Snapshot Mutation Policies of Jetpack Compose
1) Quite a big update. The K2 compiler will become stable in the Kotlin 2.0 release. Bear in mind the next Kotlin release will be a 1.9.0, so we have to wait a bit for the 2.0 ๐
๐ ย The K2 Compiler is going stable in Kotlin 2.0
2) Android library compatibility is a major concern for developers, as it affects the performance and stability of the applications they create. It is essential to ensure that the libraries used are compatible with the Android platform, so as to ensure a smooth and successful user experience. How can you achieve it? You can find more about it below.
๐ ย Android library compatibility and public API management with binary compatibility validator
3) If you've ever used Compose, youโre probably familiar with padding Modifiers and the Spacer composable. But have you ever wondered if there are any pros and cons of using them and when is the right time to use one of them?
๐ ย Space Hoisting: Should I use the padding Modifier or the Spacer composable?
4) Recompositions. Recompositions everywhere. But seriously, how does Jetpack Compose know when the state has changed and that itโs time to recompose? Have a look at how Snapshot Mutation Policy works ๐ต๐ป
๐ ย Leveraging the Snapshot Mutation Policies of Jetpack Compose
Thatโs all for today. Donโt forget to recommend this Newsletter to a friend or someone who might be interested.
Thanks for reading and see you at the next one!
All the best,
Patryk
patrykkosieradzki.com | androiddevnews.com | androidtalks.com
P.S.
Would you like to ask me something?
Just answer this email and I will be happy to get back to you!
If youโd like to read previous issues, please visit the archive on my website.