I'll also note that the AndroidX Transition and framework Transition classes that those Material Motion examples are built on only apply to Android Views, not to Composables. You'd have to use the Compose Transition APIs for composables and that's what Navigation Compose will be adding support for
➕ 1
🙏 1
c
Colton Idle
02/21/2021, 4:42 AM
Curious if there's an interop story for this potentially.
i.e. my team is planning on sticking to fragments and aac nav and we already use a few material transitions. But we are going to move 1 page at a time to compose and it'd be nice (since the composable page is going to be hosted in a fragment) to be able to do animations between them.
a
Albert Chang
02/21/2021, 6:05 AM
@Colton Idle If you are using fragments (or activities) to show different screens, I don't think there's any problem to stick with current transition APIs (though shared elements won't work because it's view-based).