simple-stack VS ViewPropertyObjectAnimator

As someone who had been using single-activity since 2015 (a'la Flow) and eventually just rewrote the whole thing to fix all the bugs we had with it in 2017, I find it sad that the single-activity approach was questioned not because it was harder, but because people made their own lives harder. And then Google made their lives harder.

I've been using single-activity but with Simple-Stack since 2016 and never deprecated it because Navigation just has these quirks that impede you a lot. I know how to use it but wouldn't really pick it.

This is why we've been using https://github.com/Zhuinden/simple-stack and it was never deprecated. We've been using it for 6 years, I'd say there was a critical bug but it was fixed in 2.3.1...

I mean, we use Simple-Stack because it makes things easier, if it didn't we'd have ditched it long ago https://github.com/Zhuinden/simple-stack

Agreed. I also added support for it 2 weeks ago.

I don't, because we use this and it's better than activities+intents 😅

We've been making single activity apps with https://github.com/Zhuinden/simple-stack and it has been easier than multi-activity.

I still use https://github.com/Zhuinden/simple-stack to this day, although I still use it with fragments.

I have been using Fragments instead of compound viewgroups lately with simple-stack as the navigator for the single-activity, although I need to figure out how to switch to use onBackPressed+onBackInvokedCallback and not just onBackPressed.

You can think of Simple-Stack as a direct successor of Mortar+Flow.

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