Consider adding some sort of integration to allow easier use of shared element transitions between screens. about decompose HOT 7 OPEN

I would be interested in exploring this further if I can get a better idea of what you mean here

Most of the APIs are described in the docs: https://arkivanov.github.io/Decompose/extensions/compose/#animations
Let me know if you need more information.

from decompose.

Well, it was pretty easy to create a new simple example with shared transitions, without predictive back support and without any changes in Decompose. I've uploaded the example to a separate branch. I've also extracted a separate commit that just adds the shared transitions on their own.

The support of the predictive back gesture is tricky and most likely will require some API changes. I will keep providing updates here.

from decompose.

It would be nice to document the option with shared traditions but without predictive back gesture for now.

from decompose.

Thanks for raising this issue! The biggest challenge for now seems to be that Decompose uses its own stack animation API, and so it might be difficult to provide AnimatedVisibilityScope. The custom animation API allows writing custom animations easily almost without limitations.

We'll need to wait until the shared transitions API is available in Multiplatform Compose, then I will investigate and provide updates here. We might need a separate animation API to support shared transitions.

from decompose.

There is also a modifier like sharedElementWithCallerManagedVisibility, which might work.

from decompose.

The custom animation API allows writing custom animations easily almost without limitations.

This sounds very enticing, I would be interested in exploring this further if I can get a better idea of what you mean here!

We'll need to wait until the shared transitions API is available in Multiplatform Compose

Yeap, absolutely. I am raising this issue perhaps a bit early, but it's good to have in mind regardless.

sharedElementWithCallerManagedVisibility

Yeap, I will give this a shot too, thanks!

from decompose.

I've checked the predictive back gesture support further: currently it looks like we'll need to change both the animation and and the predictive back gesture APIs. Indeed, the API will need to provide AnimatedVisibilityScope. Most likely this will be implemented in the next 4.0 major release, together with #695. Or maybe as a separate set of experimental APIs in a minor 3.x update.

from decompose.