Epoxy VS simple-stack

You may use epoxy recyclerview by airbnb. Check it out here

Epoxy by Airbnb

Because that's what the grown folks do!!! HERE is the Epoxy library which is AirBnb's open source custom view library for complex RecyclerViews

Epoxy is sharing viewpools on an activity level by default, for example https://github.com/airbnb/epoxy/blob/master/epoxy-adapter/src/main/java/com/airbnb/epoxy/ActivityRecyclerPool.kt

There's a library called Epoxy https://github.com/airbnb/epoxy/

RecyclerView utilities: Epoxy, Groupie, AdapterDelegates

I used to hate recyclerview and writing their adapters each time until i came across Airbnb Epoxy. Now I've forgotten how to write View Holders and sh*t. This library has made more comfortable with RV. I haven't started compose because i feel it's still not ready for complicated apps like content apps or e commerce etc.

Airbnb built epoxy as a way to help do the second approach: https://github.com/airbnb/epoxy

I would suggest epoxy as well. The bigger cards would use Grouping and then everything is just EpoxyModel.

Epoxy: https://github.com/airbnb/epoxy

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.