Android Jetpack Compose State Hoisting

State hoisting is a refactoring pattern where you move the state out of a composable function to make it stateless. By passing the data down as parameters and events up via lambdas, you ensure the UI component is highly reusable and easily testable.

Instead of keeping a local `MutableState` variable, you hoist the state by passing the current text string and an `onValueChange` lambda to the parent composable. The parent then holds the source of truth and feeds the data back down, following the unidirectional data flow pattern.

Yes, properly hoisting state isolates changes to the specific components that actually need to update, limiting unnecessary recompositions. When state is kept local to a parent, changing it can trigger wide UI rebuilds, whereas hoisting ensures only the child relying on that data recomposes.

You typically hoist the state from individual UI composables all the way up to a `ViewModel`, which holds the data as a `StateFlow` or `LiveData`. The screen-level composable collects this state from the ViewModel and passes the necessary data chunks down to its children.