Then you’re golden, won’t need to do anything else...

# compose-destinations

[Stylianos Gakis]

Then you’re golden, won’t need to do anything else. The users themselves can then decide on their own how the want to propagate that down to the place where they want to add the shared transitions.
Since those APIs are still experimental, even the android team is still experimenting with the best approach for that, but in one sample they’re working on they seem to have tried looking into doing the composition locals approach https://github.com/android/compose-samples/blob/cc61fa7846ca7f5234db521af4ecc78924[…]tsnack/app/src/main/java/com/example/jetsnack/ui/JetsnackApp.kt
Then client-side one can decide if they want to do the same or if they just want to mark all composables with the necessary scope. Or even to use context receivers and do

@Composable
context(AnimatedVisibilityScope, SharedTransitionScope)
fun ScreenComposable() {}

Most likely not something you should worry on your end in this library