Suggested pattern for navigating outside of Presenter

[troyjperales]

Our app has the common use case of navigating the user to the log-in screen due to some asynchronous event (e.g. WebSocket message indicating the account password has changed, etc). I want to isolate the event listening and navigation instead of adding the same logic to each Presenter.

Which approach is recommended for this use case? How might one navigate in non-Presenter classes?

[ZacSweers]

You could create your own Navigator implementation that you pass down that internally observes this state, or hoist it up to the place where you create your back stack and pop the back stack directly

[troyjperales]

A custom Navigator implementation seems like overkill—especially since the Navigator API is more than sufficient.

As for the "hoist it up" option, did you mean something like this?

val backStack = rememberSaveableBackStack(initialScreen)
val delegate = rememberCircuitNavigator(backStack)
val navigator = rememberAndroidScreenAwareNavigator(delegate, this@MainActivity::goTo)

LaunchedEffect(Unit) {
    launch(Dispatchers.Default) {
        // Mock invalidated log-in session event received
        delay(10000)

        navigator.resetRoot(SignInScreen)
    }
}

CircuitCompositionLocals(circuit) {
    NavigableCircuitContent(navigator, backStack)
}

[ZacSweers]

That works