koin VS kotlinx.serialization

Building UIs with Compose Multiplatform is getting more and more popular. If you're looking for a solid way to structure your app, you might have heard of Circuit from Slack for UI architecture and Koin for dependency injection. They work great together!

Koin - Dependency injection

In the Kotlin ecosystem, dependency injection (DI) frameworks are essential for managing dependencies, improving modularity, and streamlining application development. Koin has emerged as a popular DI framework for Kotlin developers, especially valued for its simplicity, lightweight nature, and multiplatform support. At the time of writing, Koin 4.0 has been released. Built on Kotlin 2.0, this release introduces a wide range of enhancements and Compose Multiplatform features. As we move into 2025, Koin continues to be an excellent choice, particularly because of its Kotlin-first design, ease of use, and adaptability across platforms.

The Koin framework is now updated to support the latest Kotlin version, now integrating with Google KSP. Koin Annotations 2.0.0-Beta1 to take advantage of Kotlin 2.0.20 and KSP 2.0.20-1.0.25, and target Koin 4.0. This release is based on the stable 1.4.0 version.

Added Koin as Dependencies Injection framework

Koin to manage dependency injection (more explanation about that later)

Let's see how we can use Koin to achieve Dependency Injection (DI) and incorporate a third-party iOS Swift SDK in a KMM project. Koin supports KMM development, making it the ideal choice for KMM projects.

Good API design dictates that you should be flexible as to what you accept and strict about what you serve. Being flexible doesn't really break anything.

Elasticsearch and Opensearch both actually have partial support for JSON5 (comments), which is a nice feature if you want to document e.g. a complex query or mapping choice. It won't return any comments in the response. So it won't break other parsers. Implementing JSON 5 support like this is a valid thing to do for any server. More broad support for this in parsers would be nice.

I'd probably enable this on my own servers if this was possible. I'd need that to be supported in kotlinx.serialization. See discussion on this here: https://github.com/Kotlin/kotlinx.serialization/issues/797

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