preserving-state-across-reloads

Keep Compose state after a hot reload by staying inside HotSwan tier 1 targeted recomposition, which preserves remember values, scroll position, and dialog state. Convert local remember to rememberSaveable for any state that must survive a tier 2 composition reset.

Scroll position resets when the reload escalates to tier 2 or tier 3 and the scroll state is not backed by a saveable holder. Use rememberLazyListState with stable item keys, since it is backed by a Saveable and survives composition reset and Activity recreation.

remember values survive tier 1 targeted recomposition but are disposed during a tier 2 composition reset. rememberSaveable persists through composition reset, making it the right choice for UI state that must survive reloads that may escalate.

Editing a value used by MaterialTheme invalidates the root CompositionLocalProvider content lambda, which HotSwan cannot scope to a single recomposition target, so it escalates to tier 2. Move the value into a local override on the composable being tuned during iteration.

Hoist transient UI state such as selected tab, expanded item, or dialog visibility into a ViewModel during long iteration sessions where edits keep escalating to tier 2 or tier 3. ViewModel survives all three HotSwan reload tiers and configuration changes.

No, staticCompositionLocalOf invalidates the entire content of its provider on any change, forcing HotSwan to escalate to tier 2. Use compositionLocalOf instead, which tracks reads and only invalidates actual readers, keeping reloads inside tier 1.