Pontoon VS datmusic-android

I've implemented it before in my open source app Pontoon using motion layout. It isn't too difficult to do.

A separate object that's scoped outside of the activity's lifecycle (Singleton, or something like dagger-hilt's @ActivityRetainedScoped), that exposes state to your app ViewModel to consume. Here's an example on how I approached it personally using a media library called exoplayer & a reactive library.

I like to think my pet project Pontoon is well written in some parts. The package structure is a little messy since I was playing around with modularizing the app for making an android TV version. It's mostly kotlin+rxjava2+dagger hilt. The architecture itself is basically mvvm with extra steps. But overall it's a fairly performant app with a complex feature set (in app & system picture-in-picture, custom theming engine). Feel free to ping me about it if you have any questions.

I have learned a lot from reading Tivi's code over the years, here's my app using similar libraries & arch datmusic-android

Didn't expect the migration process to M3 would be this much involved. I thought just changing the MaterialTheme would be enough (new color schema/names, all different Typography names, no Shapes yet etc.). But all other components such as Text, Button, Icon, Progress/Slider, Scaffold, Surface need to be replaced with M3 versions..

I'm using it in production in my small music app (source) and I couldn't be happier about it. I was worried about scrolling until I tried release/prod build. navigation-compose and bottom-sheet integration also has some bugs. But we're not far from a perfect UI toolkit.