Thanks for the PR ! I actually was working on a fix at b11a085. Basically, we should be running the logic in the when statement for the previous and new entry. To make sure both can have a fallback. Do you mind merging master to your branch and making sure that the custom key you added in the sample app still behaves as you expect?

I merged your commit to my branch. Behavior is not as expected. Even the forward transition is not the same as before.
You have the transition associated with only one screen. I think the transition is defined between the current screen and the next screen, they have a similar animation. You have a combination of two different animations

I merged your commit to my branch. Behavior is not as expected. Even the forward transition is not the same as before. You have the transition associated with only one screen. I think the transition is defined between the current screen and the next screen, they have a similar animation. You have a combination of two different animations

Screen record

I think your recording here is showing the proper transitions.

I gave this article a read:
https://medium.com/androiddevelopers/animations-in-navigation-compose-36d48870776b

So my understanding is the following:

• Details Screen plays its exit transition (Slide left + fade out) then custom key screen plays its enter (Slide in up)
• When you pop, the custom key will play its slide out while the details screen will play its slide in animation

That's basically what I understood when going through the fragment transition doc and the accompanist animation library for NavHost.

If I'm mistaken please let me know, it's actually quite confusing trying to understand.

I'm confused too.
I think a navigation library has different approaches.
You want to use the same approach as the accompanist animation library, but there is a different API.
Let's say we use your approach. Can you please tell me how to achieve the same animation as here with keyTransition/nodeTransition?

That's actually a good point. I'm actually doing some research now and trying out different use cases to see what fits better in Guia.

Alright, I think for Guia it makes more sense the previous/your approach. Let's go with your changes! Fix conflicts and let's get this PR in. Thank you!