I would like to navigate to a splash screen, perform an animation for a specified duration and then navigate to another screen. Is there a better way than placing the following inside my splash screen composable function? The navigateTo modifies a property in a Model object.

GlobalScope.launch(Dispatchers.Main) {
    // replace delay with some kind of animation on ui elements
    delay(2000)
    navigateTo(Screen.Question)
}

You will have issues if you put that directly into a composable function rather than in an

onCommit

effect block or similar; if your UI gets recomposed you will get multiple launches happening

Thank you for the input! I am reading up on the differences between

onCommit

and

onActive

. Would it not be better for this use case to use

onActive

? I put some logging into both

onActive

and

onCommit

of the splash screen compostable function.

OnActive

was called once while

onCommit

was called 11 times. Seems that however my code is currently structured is causing the splash screen to recompose a lot.

onActive

is probably appropriate in here, but it's also likely to be removed in a later update. Its docs describe that it's just an alias for essentially

onCommit(true) { }

or

onCommit(Unit) { }

or some other constant that will never change