komm
Kotlin Object Multiplatform Mapper (by Scogun)
koin
Koin - a pragmatic lightweight dependency injection framework for Kotlin & Kotlin Multiplatform (by InsertKoinIO)
| komm | koin | |
|---|---|---|
| 1 | 21 | |
| 12 | 9,122 | |
| - | 0.7% | |
| 8.0 | 9.4 | |
| 2 months ago | 8 days ago | |
| Kotlin | Kotlin | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
komm
Posts with mentions or reviews of komm.
We have used some of these posts to build our list of alternatives
and similar projects.
koin
Posts with mentions or reviews of koin.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-09-10.
-
Modern Dependency Injection with Koin: The Smart DI Choice for 2025
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.
- When developing a Compose application......
-
Koin is now updated to support the latest Kotlin version
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.
-
Day 1. Deep breath and dive.
Added Koin as Dependencies Injection framework
-
Building a subscription tracker Desktop and iOS app with compose multiplatform
Koin to manage dependency injection (more explanation about that later)
-
Kotlin Multiplatform and Swift - Overcoming Interoperability Challenges for Multiplatform Development
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.
- [Typescript] Quelqu'un peut-il suggérer une bibliothèque d'injection de dépendance simple pour TypeScript / JavaScript?
-
Best Practices When Splitting Compose Functions Into Separate Files
Might want to tell koin that : https://insert-koin.io/
-
KVision 6.0.0 is released
New modules allow you to easily build KVision apps with the Ballast opinionated application state management framework. You can see how Ballast (together with Koin) can help you design your application architecture in the new todomvc-ballast example.
-
Multiplatform dependency injection libraries equivalent to Dagger/Anvil
I started looking into using Kotlin/JS, and hopefully reusing a bit of code that I have, which is using Dagger and Anvil - which of course are JVM only. So I've been looking for other solutions, namely Koin and Kodein. Koin's multibinding support is... not really amazing (e.g. here, and while Kodein does support multibinding, it doesn't seem to support things like that at the declaration site - everything needs to be specified in a "DI container" (module).