Are there plans to make the default transition animation in `navigation-compose` optional? With sepa...

# compose

[Florian]

Are there plans to make the default transition animation in navigation-compose optional? With separate app bars per screen it looks pretty bad.

[Slava Glushenkov]

https://google.github.io/accompanist/navigation-animation/

[Florian]

ah, thank you

[Florian]

but it feels heavy to add another library just to set the animation to null

[Slava Glushenkov]

What if

navController.navigate(YOUR_ROUTE,
    NavOptions.Builder().setEnterAnim(0).setExitAnim(0).build())

?

[Florian]

doesn't seem to have any effect

[Ian Lake]

If you want to control your animations, you'll need to use Accompanist Navigation Compose until Navigation 2.5 comes out, as per the blog post: https://link.medium.com/XhegCCsdUib

[Florian]

Thank you @Ian Lake

[Ian Lake]

Specifically, I'm excited to see how shared elements end up in Compose 1.1 as being able to customize the transition between the app bar in one destination and its twin in the next screen seems like a really good use case