using-efficient-effects

Wrap the callback with rememberUpdatedState and reference the latest value inside the effect. The coroutine keeps running without restarting while always invoking the freshest lambda passed from 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 that need explicit setup and onDispose cleanup.

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 screen's 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 for teardown.

The effect restarts whenever any key in its key set changes value. Lying about the key set or passing unstable keys causes unexpected restarts; conversely, omitting a value the effect closes over makes it miss updates.

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.