# kodein

Published articles for kodein.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Moving forward with the Kodein Open Source Initiative

DevFeed: [Moving forward with the Kodein Open Source Initiative](<https://devfeed.tech/articles/moving-forward-with-the-kodein-open-source-initiative-22864.md>)

Original publisher: [Read original article](<https://medium.com/kodein-koders/moving-forward-with-the-kodein-open-source-initiative-9fc4f6160c84?source=rss----f311f45ef54---4>)

Author: Salomon BRYS

Published: 2022-06-08T12:53:24Z

Content type: opinion

Language: en

Sources: [Kodein Koders - Medium](<https://devfeed.tech/sources/kodein-koders-medium.md>)

Topics: [Kotlin Multiplatform](<https://devfeed.tech/topics/kotlin-multiplatform.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Development](<https://devfeed.tech/topics/development.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [application-development](<https://devfeed.tech/tags/application-development.md>), [dependency-injection](<https://devfeed.tech/tags/dependency-injection.md>), [kodein](<https://devfeed.tech/tags/kodein.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [library](<https://devfeed.tech/tags/library.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [open-source](<https://devfeed.tech/tags/open-source.md>)

### AI overview

Kodein Koders announces the sunset of Kodein-Framework and the creation of the Kodein Open Source Initiative, or KOSI. Its libraries will receive independent identities while continuing to be maintained and advanced, with organizational and project changes planned for the following weeks.

### Source excerpt

Photo by Daniel Lerman on Unsplash Back in the very early days of Kotlin Multiplatform, when the KODEIN Dependency Injection library was the very first community library ever being ported to this new promising technology, I dreamt of an integrated suite of components that, together, offered mobile developers tools to quickly and easily develop multi-platform mobile applications. In essence, I wanted to create a framework providing DI, DB, Logging, MVI, and more, all integrated into a cohesive platform. However, as time went on, I realised that Open Source development is quite long and difficult (who knew, right?), especially when you're a team of two, and that you also need to work for clients, in order to, you know, eat. I also realised that I was promoting our work backwards. The message "This lib is part of a framework that does not really exist yet, but it is also its own independent library that you can totally use without any other of our libs" is actually very ambiguous. Furthermore, full fledged frameworks are nowadays a lot less attractive to developers. As application craftsmen & craftswomen, we want to own our architecture, and make choices that reflect our very own business needs, opinions, and experience. It's not because you are using the Kodein Dependency Injection container that using SQLDelight (instead of Kodein-DB) should feel a mistake, or vice-versa. I came to the realisation that when we advertise each library as part of a whole framework, we harm each individual library by preventing them to be evaluated only by their own merits. We (Romain and I, founders of Kodein Koders) decided that it is time to sunset the Kodein-Framework. This by no means signifies that we will stop working on our Open-Source libs, but simply that each library will be given its very own independent identity. We will be maintaining & advancing these libraries as the "Kodein Open Source Initiative", or KOSI for short. The biggest change that this decision will bring is th