Advanced layout animations in Compose (Shared elements)

[@JimPekarek]

Thanks for showing off Shared Element Transitions with a non-trivial example. This was really well-presented

[@monsterbrain]

It's looking great and found this really adding a smoothness to the app. Keep up the great work.

[@HoussamElbadissi]

Amazing presentation! Super clear and to the point. Love the new APIs, as idiomatic and powerful as ever!

[@carlfe4891]

I might finally use shared element transitions. Great work making this easy to customize and implement.

[@occasus7964]

These are the kinds of helpful videos that I look forward too.

[@PauliDev]

I loved your presentation and Droidcon Berlin! That was superb informative and now I'm glad those jetsnack examples are online and I'm able to experiment with them. I did my first sharedElementTransition today! These are the "fireworks" developers love Compose for!

[@__J____ff]

yes this is really well presented ! must be the very precise/accurate use of the visuals and the perfect examples.

[@oleksee]

My god this is complex and not obvious stuff over here. Haven't had much chance to work with animations in Compose so that makes it an extra layer harder for me to understand. Nevertheless thank you for the helpful video!

[@AbdulBasit-kd5vk]

very nice explanation and demos.

[@jeffhow4550]

Thanks for the useful video. Just some suggestions for if you were to do another UI video... The visuals/animations were useful, but they would be much more understandable if you could show a "Before" animation side-by-side with an "After" animation at each step of the process. It can be hard to tell what's exactly changing at each step. Having to scrub through the video sometimes isn't enough. Thank you!

[@kenyakking]

💯great presentation! Thanks!

[@deviantstudio]

i hope all these tricks will be documented in the docs

[@mohamedkarim-p7j]

Thank for sharing 👍

[@Vatk4LI]

Why there is no blur background effects in compose built in libraries. It would be great for designs.

[@GakisStylianos]

There is the .blur modifier

[@Vatk4LI]

@@GakisStylianos did u ever use it? It's not a blur BACKGROUND modifier isn't it?

[@GakisStylianos]

You might be looking for the "Haze" library by Chris Banes for this

[@Vatk4LI]

@@GakisStylianos yeah i saw it but its not quite well. For me it doesnt work even sdk 31 and above.

[@GakisStylianos]

What do you mean it doesn't work?

[@erfansn869]

Great and nice content

[@serhii.petrosiuk]

Great job!

[@evilexus]

How something as "simple as animations" can add problems and add new features to fix those problems, What irony don't you think ?😅 Anyway thanks for the well explained tutorial ✌

[@aligold22]

شكرا على الشرح انا تعلم برمجة تطبيقات الموبايل من النت ولدي تطبيقات شكرا على مجهودكم ❤

[@嘿嘿嘿-z1v]

油條 is so cute 😂❤

[@austin17ng]

lots of information

[@omyadav1866]

Very nice 👍 thanks for your support help me

[@calixtoandrade996]

thanks for this

[@muzamilabdallah6768]

Great

[@akashmanna2099]

Great

[@Chirag-Redij38]

While using predictive back gesture with sharedTransition I am not able to render the lazyGrid behind... It just shows a black screen

[@markocicak4004]

Latest Compose Multiplatform 1.7.0 is supposed to support shared element transitions. Does anyone know what to import in commonMain.dependencies to support the sharedElement API?

[@ahmadprogrammer136]

I have a first screen with a list of images, and when I click on any image, it moves to another screen with a HorizantelPager that displays all images with the HorizantelPager configured to start from the index of the image that was clicked, and a SharedElement is applied to this image. Now, if I change the image that the SharedElement was applied to in the second screen (HorizantelPager Screen) by swiping left or right, the SharedElement will not occur when I return to the first screen (which contains the list of images), but the SharedElement will be applied to the image that was clicked on the first page. I want the SharedElemnt to be applied even if I change the image in the second screen (HorizantelPager). I hope that I was able to describe the problem correctly 😅 Is there a solution to this problem?

[@AndroidRecovery-BRICKED]

I only have android honeycomb:(

[@omyadav1866]

Google meet great success Android phone Android

[@omyadav1866]

ANDROID DEVICE ID SUPPORT PRIVACY POLICY WITH VISITORS

[@techietoons]

You people keep on making things complex. Flutter is much better for animations. Developer can focus on implementing the business logic, rather that these low level managements.

[@j2shoes288]

1) Compose Animation can still be janky.