groupie VS kotlinx.serialization

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.

Have you tried this:? https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/serializers.md

Regardless, I followed the documentation to register List for polymorphic serialization and my static code analysis does not seem to be happy with it.

I think kotlinx.serialization might come close, but looks like custom Encoders and Decoders are still experimental.

This example will not work on a multiplatform project. you are using gson, gson runs only on jvm, you should use https://github.com/Kotlin/kotlinx.serialization for the json parsing

This is the issue to +1 https://github.com/Kotlin/kotlinx.serialization/issues/1931

Fun fact, kotlinx.serialization had a release just recently which makes it come with some bundled proguard rules to make this experience easier. Yes you'll still have issues if you're using things via reflection and try to serialize things that proguard deemed unused and removed them, but it's a step forward https://github.com/Kotlin/kotlinx.serialization/releases/tag/v1.5.0-RC

Kotlin Serialization

Kotlin Serialization is also a newer option, but doesn't have as much traction.

``` see the docs