Compose State Management Mastery Hub: The Industry Foundatio

In the context of Jetpack Compose state management, what is the fundamental difference between `State` and `MutableState` when observing recomposition?

Consider a complex UI where a list of items is displayed, and each item has its own internal state (e.g., whether it's expanded or collapsed). If you were to manage the expanded/collapsed state of each item individually using `remember { mutableStateOf(...) }` within the `ItemComposable`, what potential performance bottleneck might arise during frequent list updates or scrolling?

focuses on local state within items. Option D is a common pitfall with `LazyColumn`/`LazyRow` if state isn't managed correctly (e.g., by hoisting it to the parent or using `rememberSaveable`), but the question specifically asks about managing state *within* the item composable using `mutableStateOf`, which doesn't inherently cause state loss on scroll. The core issue described is the potential for the individual item state changes to indirectly cause broader recompositions or for the list management to be inefficient when dealing with many individual state objects. Question: When dealing with complex, shared state across multiple composables that needs to be modified by different parts of the UI, what is the idiomatic Compose pattern to avoid passing state down through many layers of composables (prop drilling) and ensure efficient updates?