ViewPropertyObjectAnimator VS android-dev-challenge-compose-design

I've been using https://github.com/blipinsk/ViewPropertyObjectAnimator and it's amazing

you just use https://github.com/blipinsk/ViewPropertyObjectAnimator for everything, and if you need shared element transtiions you cry (then again, it's not like Compost can do that at all, so)

Animations with views were much easier, you just had to use this lib https://github.com/blipinsk/ViewPropertyObjectAnimator and animator sets made it trivial. If you needed fancy crossfades then TransitionManager.beginDelayedTransition(container) and that's it.

Honestly, they're pretty even in that regard. Whether you use XML or Compose in "simple apps" is up to you. Some things are easier in Compose, and some things are just stupid tricky. Animations in Compose are the worst imo, with ViewPropertyObjectAnimator they used to be trivial for XML layouts.

This is probably just my experience, but with Compose I have to muck around with LaunchedEffects and manual interpolation, while with XML views I could just use https://github.com/blipinsk/ViewPropertyObjectAnimator and AnimatorSet().playTogether().

That, and animations with https://github.com/blipinsk/ViewPropertyObjectAnimator were much easier than linear interpolating in a LaunchedEffect, and shadow support is basically non-existent (Modifier.shadow() doesn't work as you expect, even android:elevation was better).

I like this library https://github.com/blipinsk/ViewPropertyObjectAnimator

I don't know how to write animations without ViewPropertyObjectAnimator https://github.com/blipinsk/ViewPropertyObjectAnimator

Really? I just used https://github.com/blipinsk/ViewPropertyObjectAnimator + AnimatorSet for everything and it always just worked

you're asking about how to do this

I still don't know why I needed this Layout, but it's true that replacing drawables and styleables with mere function calls and function arguments respectively is promising

You can extract logical components to the top of a composable as local functions and retain reasonable scoping while also creating local components, thus making the actual code straightforward to read (even if you sometimes need to also add hacks because Compose be Compose)

Yeah, both for measuring the current width/height of the layout (like getting the screen size), and also when things like Modifier.fillMaxSize(0.5f) doesn't work and I have to write code like this

Oh, that's unique to Navigation-Compose's design, and has nothing to do with declarative UI in particular. For me, navigation in compose is just this

Although I personally would rather pass in lambdas and then make the connection