timber VS kotlinx.serialization

To try and fix this problem fast I knew I needed some sort of logging and that is when I discovered Timber and Firebase Crashlynics. I then used THIS video to set both of them up and to create a decent crash reporting system.

Timber

Do you still use the Android Timber lib? The only real pro I see is that you don't need to declare the Tag, other than that that "pro" where each call checks if debug or not I wonder why you would like to have that, I mean what I want is all debug-only logs to get stripped out from the code, and instead of calling if(BuildConfig.Debug) on each Timer.xy() call why not create an extra Application class under the debug folder where logs are activated? Just trying to figure out of this lib that actually started like 9 years ago is still needed or not really anymore. https://github.com/JakeWharton/timber

One of the options could be to setup logging to the file within the app and sync it with backend once necessary or required. This could be achieved by using library, such as Timber and setting up local file. Depending on your constraints, such as file size, you might want to include a file rotation strategy, e.g. start a new file and remove the old one.

Timber for logging

Same as in Timber

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