rememberCoroutineScope สำหรับเหตุการณ์

LaunchedEffect runs as composition happens. But scrolling a list or showing a snackbar should start from a callback like onClick, not on entry.

A rememberCoroutineScope gives you a CoroutineScope bound to the composition. You keep it around and launch from event handlers.

Inside a click lambda you call scope.launch to start suspend work. The body itself stays free of coroutines.

LaunchedEffect fires on composition, so it cannot react to a user event. The scope lets you decide exactly when to launch.

The scope is cancelled automatically when the Composable that created it leaves composition. Pending jobs are cleaned up for you.

Showing a snackbar is a suspend call, so it must run in a coroutine. Trigger it from a button using your remembered scope.

Programmatic scrolling like animateScrollToItem is also suspending. Launch it from the scope when the user taps a jump button.

Because you call remember, the same scope survives recompositions. You will not accidentally create a new scope every redraw.

One launch block can sequence multiple suspend steps. They run in order on the same coroutine, which keeps event logic readable.

For composition-triggered work prefer LaunchedEffect. Reserve rememberCoroutineScope for user-driven and other callback-driven launches.

Read state, run a suspend save, then show feedback, all inside one launch fired by the tap. The remembered scope ties it to the screen.

Think about where each coroutine helper belongs.

Great! Use rememberCoroutineScope to launch suspend work from callbacks like onClick. It is scoped to the composition and cancels itself when the Composable leaves. ✨