A modern programming language that makes developers happier.

kotlinlang

Hi. Is there something built-in for shared transition animation between screens?

Short answer: not yet.
But it's a high priority item on our roadmap. :slightly_smiling_face:

Thx. Is there a public roadmap for Compose?

This particular work item is tracked here: <https://issuetracker.google.com/172112072>
I'm not aware of other forms of public roadmap for Compose.

Is it going to be separated from navigation component?

It would be nice if it was part of jetpack compose animation

Or we can add separate artifact `androidx.compose.transition:transition:1.0.0-alpha01`

Is there a particular reason for preferring it to be separate from the navigation component? :slightly_smiling_face:

I’m using decompose from <@UHAJKUSTU> for navigation :grinning:

image.png

There could be composable function which manages transitions of child composables

The idea I have in mind is using `Transition` as a vehicle for all the animations in (any level of the) children, including shared element, during the screen/destination change. `Transition`'s state change can be observed by navigation (or anyone else) and therefore can be used as a signal for when things should be destructed.

Looking at the snippet above, it shouldn't be hard for decompose to support such a concept. We need to experiment with that idea some more and build necessary pieces in `Transition` to support that.  We'll keep your use case in mind when we build it. :slightly_smiling_face:  Animation features such as shared element will most likely be in the animation library, while navigation component being a client of it.

Decompose supports animations with `Crossfade`-like API. I hope there will be more animations like Crossfade.

`Crossfade` is actually now built on `Transition` . Glad to hear that Decompose already supports that. I'm hoping to build more layout animation with `Transition` . Stay tuned. :slightly_smiling_face: