A modern programming language that makes developers happier.

kotlinlang

Is there a way do to shared element transitions?

It’s in Focus from the Roadmap
<https://developer.android.com/jetpack/androidx/compose-roadmap>

Wow I just realised in this list that chips are not yet on Compose

You can do both of those today, it's just fairly manual

For Chips is quite simple, that’s why I’m surprised it’s not there yet, but I understand that the official implementation needs a lot of work, so I don’t mind. For the shared transition I remember seeing some repo based on early compose versions but unfortunately I wasn’t able to adapt everything to most recent ones, so I was hoping for something official, but I see it’s on the roadmap :slightly_smiling_face:

Wait, but there are <https://developer.android.com/reference/kotlin/androidx/compose/material/package-summary#Chip(kotlin.Function0,androidx.compose.ui.Modifier,kotlin.Boolean,androidx.compose.foundation.interaction.MutableInteractionSource,androidx.compose.ui.graphics.Shape,androidx.compose.foundation.BorderStroke,androidx.compose.material.ChipColors,kotlin.Function0,kotlin.Function1)|Chip> and <https://developer.android.com/reference/kotlin/androidx/compose/material/package-summary#FilterChip(kotlin.Boolean,kotlin.Function0,androidx.compose.ui.Modifier,kotlin.Boolean,androidx.compose.foundation.interaction.MutableInteractionSource,androidx.compose.ui.graphics.Shape,androidx.compose.foundation.BorderStroke,androidx.compose.material.SelectableChipColors,kotlin.Function0,kotlin.Function0,kotlin.Function0,kotlin.Function1)|FilterChip>. What do you mean by "are not yet on Compose", <@UBW2MSDDK>?

<@U039G2ZP6G6> my bad for not trying it, I just opened the Roadmap liink and it’s there, so I thought it wasn’t on the library yet

I guess they didn't updated roadmap yet :slightly_smiling_face:

Shared element transition is definitely in focus - it's been my focus these days. :stuck_out_tongue:

<@UBW2MSDDK> Is there a specific shared element transition that you are trying to build? I'd love to see a mock if you don't mind sharing.

<@UNH9ZT3NZ> thanks for your efforts :hearts: I'm trying a very simples transition. I've a list with movies posters and when clicking on it to see details I would like the poster to transition to the movie details screen

Basically like this <https://rubygarage.s3.amazonaws.com/uploads/article_image/file/3177/1_-_Tutorial_on_Shared_Element_Transitions_in_Android_Apps.gif|https://rubygarage.s3.amazonaws.com/uploads/article_image/file/3177/1_-_Tutorial_on_Shared_Element_Transitions_in_Android_Apps.gif>

Cool! Thanks for sharing! I'll add this to my prototype list to make sure it's well supported. :slightly_smiling_face:

If you have more elaborate examples that you could share, I'd love to see them too.

is the api going to cover transition between compose-navigation destinations?

&gt;  is the api going to cover transition between compose-navigation destinations? 
Yes, that's one of the important use cases we are aiming to support. Do you have a specific use case of sharing something between compose-navigation destinations in mind?

I’m thinking the usual Scaffold elements and list/detail interactions
• ListItem -&gt; Item Detail Image/Title/Text (similar to above example)
• TopBar (think animation up icon)
• BottomBar (show/hide)
Do these make sense?

The first two make sense.  I'd love some clarification on the 3rd one - How would you use shared element for BottomBar show/hide?

&gt; Do you have a specific use case of sharing something between compose-navigation destinations in mind?
Since this is still in focus, would love to add on this.

My use case : Have a card in List view , tapping would open the bottomsheet, and this card should animate position to the top of bottomsheet.