using-efficient-effects

Wrap the callback with rememberUpdatedState and read the latest reference inside the effect. The coroutine keeps running without restarting while always invoking the most recent lambda passed by the parent.

Use LaunchedEffect when the work suspends or needs a coroutine, such as network calls or animations. Use DisposableEffect for non-coroutine subscribers like listeners or observers, since its onDispose block guarantees cleanup on key change and composition exit.

Wrap the row content in ViewModelStoreScope(key = row.id) from com.github.skydoves:compose-effects-viewmodel, then call hiltViewModel() inside. Without it, every row resolves against the parent store and shares one ViewModel instance.

RememberedEffect from skydoves/compose-effects replaces LaunchedEffect only when the body does not suspend. It reacts to key changes synchronously without allocating a coroutine scope, but it has no onDispose, so pair it with DisposableEffect if teardown is needed.

The effect restarts whenever any key in its key set changes value. Lying about the key set or capturing values not listed as keys causes missed updates or surprise restarts; key the effect on every value it closes over that should trigger a restart.

Avoid SideEffect for per-frame work or anything that allocates, because it runs on every successful composition commit. Reserve it for thin writes that publish Compose state to a non-Compose system you cannot subscribe to via DisposableEffect.