compose-state-hoisting

Hoist Jetpack Compose state by moving UI element state and logic to the correct scope, from local remember state to hoisted composable parameters, keeping UI simple, testable, and stateless.

Use a ViewModel for screen-level business logic and data handling, while local remember state or plain state holders manage UI-only state. Screen-level state holders ensure safe, testable UI state management.

A plain state holder class in Compose separates UI rendering from state management. It manages hoisted state and logic for composables when state complexity outgrows local remember but doesn't require a ViewModel.

For multi-screen Compose flows, hoist state to the correct scope using plain state holders or screen-level ViewModels. This structured decision framework ensures readability, testability, and safe UI state across screens.

Local remember state in Compose resets on configuration change. Hoist state to plain state holders or screen-level ViewModels to persist UI state and business logic safely across lifecycle events.

No, simple Compose UI components can use local remember state or plain state holders. Introduce a ViewModel only when business logic, data handling, or screen-level state management is required for testability.