I’m used to extracting navigation logic from android layer (hiding the impl details behind the interface), but I decided to give compose navigation a try. That involves tight coupling of navigation with the ui, triggering navigation from callbacks inside composable functions. I’m wondering if effects such as

onDispose()

are safe to perform such action or it’s rather considered as an anti-pattern/might lead to unexpected state (is there a risk of recomposition causing not intended navigation?). See example code below (where

isInProgress

is a part of collected state

false

by default):

if (isInProgress) {
    CircularProgressIndicator()
    onDispose {
        navigateToDone()
    }
}

😬

Thanks for feedback. Indeed, data flow is what worries me with this approach. Apart from navigation commands data goes through SharedFlow up and StateFlows down. However, all the routing is defined in top-level composables. I’m afraid of loosing a sync between ui and logic.

+1 to what Jim said: trace back to the code that sets

isInProgress

from

true

to

false

when the async operation is done and you've found the spot to dispatch your navigation request.