Android about to drop Liquid Glass done right

I’m giving away some FREE seats for the final Jetpack Compose and internals cohort. Just need to retweet this and follow me in the 🦋 platform. Link in replies 👇

The next cohort starts in around 1 month. Book your seat now before it goes sold out, 30 people in already 🏃🏃🏃🔥 RT this to help me reach more people, and get a chance to win a FREE seat or 375€ 💸, whatever you prefer 👇

Many people exploit CompositionLocals, Id recommend not doing this as possible. CompositionLocals are a form of implicit dependency passing. They are used in Compose because otherwise all Composable functions would be bloated with literally tons of extra parameters for things like context, density, theming and what not. They are indeed handy for things that can be potentially needed from several nodes at different depths on the UI tree, but the official recommendation is to not create your custom ones unless it’s something really, really specific. Otherwise it’s always better to hoist all state and user interactions via callbacks, so dependencies can be wired at the root level. Implicit dependencies are counterproductive for many reasons. They hide what are the requirements from a Composable function, and it’s too easy to break its behavior since it’s affected by external state that can change from many levels. It’s also hard to know if all dependencies required by a Composable are provided. And it’s harder to reason about a Composable on isolation. These are only a few reasons, there are more.