https://carrion.dev/en/tags/koin/Recent content in koin on Carrion.devHugo -- gohugo.ioenignacio@carrion.dev (Ignacio Carrión)ignacio@carrion.dev (Ignacio Carrión)©{year}, All Rights ReservedTue, 04 Mar 2025 08:00:00 +0100https://carrion.dev/en/posts/koin-compile-safety/Tue, 04 Mar 2025 08:00:00 +0100ignacio@carrion.dev (Ignacio Carrión)Tue, 04 Mar 2025 08:00:00 +0100https://carrion.dev/en/posts/koin-compile-safety/Achieving Compile-Time Safety in Koin: A Comprehensive Guide Dependency injection is a fundamental pattern in modern Android development, but how can we ensure our DI configuration is correct before running the app? In this post, we’ll explore two powerful approaches to achieve compile-time safety with Koin: using the DSL’s verify() function and leveraging Koin Annotations with KSP. The Problem: Runtime vs. Compile-Time Validation Traditional dependency injection often reveals configuration issues only at runtime:Ignacio Carriónfeatured imagekotlinandroidkoinhttps://carrion.dev/en/posts/koin-cmp/Thu, 02 Jan 2025 08:00:00 +0100ignacio@carrion.dev (Ignacio Carrión)Thu, 02 Jan 2025 08:00:00 +0100https://carrion.dev/en/posts/koin-cmp/Using Koin in Compose Multiplatform Dependency injection is a must-have for scalable applications, and Koin makes it straightforward, even in Compose Multiplatform projects. With the new KoinApplication composable function, you can initialize Koin directly from commonMain code, reducing boilerplate while maintaining platform-specific flexibility. Let’s walk through an example. Project Setup Start by creating a Compose Multiplatform project using the KMP Wizard, selecting Android, iOS, Desktop, and Web targets. For this example, we won’t include a server target.Ignacio Carriónfeatured imagekotlinmultiplatformcmpcomposekoin