DeclarativeAdapter-kt VS groupie

yes but there are tons of high level libraries that provide better abstractions over adapter api. check out epoxy. or even my own library DeclarativeAdapter

you can check out my library, declarative adapter: https://github.com/andob/DeclarativeAdapter-kt with it, you can define recycle view adapters more easily, but typing what you want, not how you want, step by step. also you can check out other open source libraries I made. I love declarative + functional style :)

I've been hearing for 2 years that the primary benefit of Compose is that you "no longer need to write a RecyclerView.Adapter", not realizing that you can use something like Groupie and effectively turn RecyclerView into adapter.setItems(listOf(Item1(), Item2())) just like in Compose.

https://github.com/lisawray/groupie Maybe it can help for your purposes

Been using RecyclerView and haven't written an adapter in a very long time because you can abstract it away

Technically you can also use a library that hides this from you, for example I tend to use https://github.com/lisawray/groupie with BindableItem

There are also libs that help you handle this, there's gorupie here https://github.com/lisawray/groupie and also Expandable RV here https://github.com/thoughtbot/expandable-recycler-view

RecyclerView utilities: Epoxy, Groupie, AdapterDelegates

I think Groupie is nice, although Google seems to think of each Adapter being able to describe itself "as an item view type". So you could build "multiple item view types" using a concatAdapter of N ListAdapters. Tricky.

We've been using https://github.com/lisawray/groupie/ which offers a common GroupAdapter for all Items, so that each RecyclerView Item type can be encapsulated in its own class, Item.

Don't write adapters or view holders for RecyclerView, use something like Groupie.