Splitties VS kotlinx.serialization

https://github.com/LouisCAD/Splitties don’t use it because I think it leads to dependency bloat but there you go

I've successfully used single activity with multiple fragments in the past. In one app we even dropped the fragments and inflated custom views (fueled with splitties: https://github.com/LouisCAD/Splitties when compose was in early stage) with screens logic implemented as suspendable functions.

XML is not the only way to use Android Views. With Kotlin, you can get pretty compelling results: https://github.com/LouisCAD/Splitties/tree/main/modules/views-dsl#ide-preview

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