guide-to-kotlin VS ViewPropertyObjectAnimator

Read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you'll know Kotlin. That, and you can also check the collection APIs which are pretty much the best thing in Kotlin compared to Java.

I would recommend learning Kotlin for Android though, it does help. I wrote this guide https://github.com/Zhuinden/guide-to-kotlin/wiki but you can also look at this video https://www.youtube.com/watch?v=wuiT4T_LJQo

I wrote this guide for Java => Kotlin a few years ago, other than me not adding coroutines it still holds: https://github.com/Zhuinden/guide-to-kotlin/wiki

Check this guide by me to learn Kotlin: https://github.com/Zhuinden/guide-to-kotlin/wiki

but you can read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you will know what you need to know for Kotlin basics (except coroutines, then you watch https://www.youtube.com/watch?v=6P20npkvcb8 )

I wrote https://github.com/Zhuinden/guide-to-kotlin/wiki a few years ago for people who know Java and don't know Kotlin, I've heard many positive feedback for how simple it is to transition from Java to Kotlin once reading through it.

you should probably look into Kotlin (see https://github.com/Zhuinden/guide-to-kotlin/wiki and/or https://www.youtube.com/watch?v=wuiT4T_LJQo ),

You actually can just read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you'll know how to use kotlin lo

I wrote this guide a while ago specifically to cover this kind of migration https://github.com/Zhuinden/guide-to-kotlin/wiki it should be fairly no-nonsense and I've heard people like it (they said it helped them).

I didn't need to because by the time it came out I already knew Kotlin, personally I wrote this https://github.com/Zhuinden/guide-to-kotlin/wiki

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