Epoxy VS Litho (By Facebook)

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

Waiting for Litho to be the new UI development standard https://fblitho.com/

IIRC fb is using this custom list view https://fblitho.com/

Litho by Facebook

Just a little correction, none of facebook or instagram mobile app use react native. On android, facebook, messenger, and instagram use litho library (which facebook team has also developed)

It seems unlikely that FB would give up on Litho, which is extremely performance focused, to use react native instead. Not for their bread & butter flagship news feed anyway https://fblitho.com/

I've seen some old conference talks from their team about https://fblitho.com/. I believe that what they use or at least used.

Facebook's internal android repository is still mostly Java, but there is a large push to switch to Kotlin, and Kotlin's internal support has grown dramatically over the last couple of years. Coroutines have recently been allowed (although I'm personally not a fan of that decision). Flow/Compose are not necessary as we have internal tools that do similar things (looking at you, Litho).