Compose state and effects

Core principle

Give every piece of UI state one lowest responsible owner, then run imperative work through the effect whose lifecycle follows that owner. Composition renders; state and effects make rendering change safely.

Procedure

1. Establish the requested scope and visible behavioral requirements. Treat an ownership change as a finding only when code or task evidence shows a lifecycle, testability, business, or coordination need.
2. Inventory mutable UI state, app state, event streams, app dependencies, and imperative work in the affected screen or component.
3. Place each state value at its lowest necessary owner: local UI state, hoisted state, a plain UI state holder, or a screen state holder.
4. For a screen boundary, keep durable data and intents in the wiring owner, Compose runtime objects in composition or a plain UI state holder, and rendering in a previewable content composable that takes immutable state and callbacks. Read State hoisting for the implementation shape; naming only state and intents is not that boundary.
5. Choose an effect API whose lifecycle matches the work, and key it by the semantic input that should restart or dispose it.
6. Load the focused reference for every material concern below. Do not use a reference merely because its topic is adjacent.
7. Route frame-rate reads, cross-phase back-writing, and @ReadOnlyComposable contracts to Compose performance.
8. Before responding to a screen-ownership review, verify all three screen seams in step 4 when visible code needs them.
9. Finish when every state value has one owner, every effect has a justified lifecycle and key, and the UI can be previewed and tested without app dependencies. For review-only work, report no change when no evidence-backed issue remains; do not invent product requirements.

Topic router