Android Toolkit at Google
| Moderator at Android Dev BR | Opinions are my own.| Site | https://marcellogalhardo.dev |
| Github | https://github.com/marcellogalhardo |
| BlueSky | https://bsky.app/profile/marcellogalhardo.dev |
Android Toolkit at Google
| Moderator at Android Dev BR | Opinions are my own.| Site | https://marcellogalhardo.dev |
| Github | https://github.com/marcellogalhardo |
| BlueSky | https://bsky.app/profile/marcellogalhardo.dev |
Just published "Scoping ViewModels in Compose".
https://marcellogalhardo.dev/posts/scoping-viewmodels-in-compose

Lifecycle ViewModel 2.11.0-alpha02 introduces rememberViewModelStoreOwner, an API to scope ViewModelStore directly within the Compose hierarchy. Why It Matters Until now, ViewModelStore scoping was tied to navigation destinations, activities or fragments. There was no clean way to scope a ViewModel to an arbitrary part of your UI (such as a Pager page, a LazyList item, or a custom layout) without building your own ViewModelStoreOwner from scratch. These new APIs close that gap:
@ianlake and I are speaking at #KotlinConf this year!
We'll be peeling back the layers of Navigation3 - exploring the NavDisplay API, the decisions behind each overload, and the helper APIs that let you build custom navigation logic.
See you there!
No, I don't want generative AI anywhere.
I don't want AI to write.
I don't want AI to draw.
I don't want AI to learn.
And I certainly don't want AI to make any decisions for me or about me.
Now our governments (using OUR money) are following the AI tech bros into the AI-Hell pit! ๐ซ
Please stop this madness already!
I wrote about how we (nominally) cut IDE sync time by 97% for our 2000+ module Gradle Kotlin backend project
with this upcoming change, the dependency analysis plugin will be able to detect usage of reflection, offering much better protection to your runtime classpath than it currently offers
https://github.com/autonomousapps/dependency-analysis-gradle-plugin/pull/1577