A modern programming language that makes developers happier.

kotlinlang

Finally <https://android-review.googlesource.com/c/platform/frameworks/support/+/1704159>  AnimatedContent :heart_eyes:

is it the missing piece for Lazy Column/Row animations?

I think it's related to Screen Animations which is based on new changes on AnimateVisibility child animations introduce in beta 08.

&gt;  is it the missing piece for Lazy Column/Row animations?
This is a more generic container that performs a `ContentTransform` when its content changes. More specifically it'll animate in the new content and animate out the previous content using customizable enter/exit transitions. What I'm particularly excited about is the support for a `SizeTransform` (also customizable) to automatically kick off a size animation when the content changes. Aside from these customization support, it is somewhat similar to `Crossfade`.

One concept employed in `AnimatedContent` that could be helpful for Lazy Column/Row animations is the ability to define enter/exit transitions for children at the parent level. Meanwhile, the children can access an `AnimatedVisibilityScope`  to add any additional enter/exit animations (e.g. on color, corner radius, etc) local to that child.

Doris, this got me thinking... If I use single activity, multiple fragments, but each fragment is just a Composable (we're doing this because we're not quite ready to jump into pure compose app), do you know if the material transformations that work with fragments (<https://material.io/blog/android-material-motion>) would still work in our scenario?

It should still work in theory, since the transformations (fade, slide, etc) can still be done on the `ComposeView` in your fragments. <@UJBPFB3SN> can probably give you more details when he's back from vacation. :slightly_smiling_face:

In that case... I hope Ian doesn't get back to me for a longggg time. Well deserved vacation!

Is this api something that might support shared element transitions in the future?

This API is intended to be one of the APIs that support shared element in the future. :stuck_out_tongue: