compose-state-hoisting

State hoisting in Jetpack Compose is the pattern of moving UI state and logic to the appropriate ownership level to keep components simple, testable, and reusable. You use it when state needs to be shared across siblings or coupled to business logic.

Choose local remember state for simple UI state within a single composable. Hoist state to a plain state holder when sharing across siblings, and use a screen-level ViewModel when the state involves business logic, repository calls, or influences the entire screen.

To share UI state across siblings, hoist the local remember state to the lowest common parent composable. Implement a plain state holder to manage the hoisted state, allowing siblings to interact without directly coupling to each other's internal state.

Use a plain state holder when sharing state across multiple composables and the logic grows too complex for simple parameter passing. It encapsulates the hoisted state, whereas direct parameter hoisting is better for simpler state passed directly into child composables.

Yes, state hoisting guidance includes preserving the composable lifecycle. By placing state and logic at the correct ownership level, such as screen-level state holders for business logic, you ensure components remain simple while respecting lifecycle boundaries.