# dagger-hilt Published articles for dagger-hilt. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Migrating to AGP 9.2.1: Kotlin build errors I hit and how I fixed them DevFeed: [Migrating to AGP 9.2.1: Kotlin build errors I hit and how I fixed them]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-05-27T01:03:56Z Content type: tutorial Language: en Sources: [Stories by Nav Singh πŸ‡¨πŸ‡¦ on Medium]() Topics: [Android](), [migration](), [Kotlin](), [Gradle](), [developer tooling]() Tags: [android](), [android-app-development](), [android-gradle-plugin](), [androiddev](), [compiler](), [dagger-hilt](), [errors](), [gradle](), [kotlin](), [ksp](), [migration]() ### AI overview A tutorial documenting a small Android project migration to AGP 9.2.1. It explains build errors caused by AGP 9's built-in Kotlin support and shows fixes involving removal of the old Kotlin Android plugin, migration from KAPT to KSP for Hilt, and replacement of the legacy kotlinOptions DSL. ### Source excerpt Image generate using perplexity I recently upgraded an Android project to AGP 9.2.1 and ran into a chain of build errors. In my case, the project was a very small app, so there might be more issues if the project setup is complicated. Each one pointed to a different part of the new Kotlin/Gradle setup, and fixing them one by one made the migration much clearer. Why this happened AGP 9 introduces built-in Kotlin support that changes the old plugin setup (org.jetbrains.kotlin.android). πŸ›‘ kapt, and kotlinOptions no longer work the same way. Error 1: Cannot add extension with name kotlinCannot add extension with name 'kotlin', as there is an extension already registered with that name. The fix was to remove the Kotlin Android plugin from the module and any root-level declarations that still applied it. AGP 9 already provides Kotlin support, so applying the old plugin causes a duplicate kotlin extension.Fixplugins { id("com.android.application") // remove: id("org.jetbrains.kotlin.android") }Error 2: org.jetbrains.kotlin.kapt is not compatible with built-in Kotlin support After removing the Kotlin Android plugin, the next failure came from kapt The 'org.jetbrains.kotlin.kapt' plugin is not compatible with built-in Kotlin support. Android's migration guide recommends moving to KSP, or using com.android.legacy-kapt only as a temporary fallback.Fix After removing kapt, we need to update the affected libraries. In my case, only Hilt was affected, so I updated it with the KSP plugins { //.... // Remove KAPT kotlin("kapt") // Add KSP id("com.google.devtools.ksp") } // dependencies dependencies { // kapt(libs.hilt.compiler) ksp(libs.dagger.hilt.compiler) // ... }Error 3: Unresolved reference: kotlinOptions Once kapt was out of the way, the build hit another issue 🀯 Unresolved reference 'kotlinOptions' That's because AGP 9 built-in Kotlin uses the new Kotlin compiler options DSL instead of the old android.kotlinOptions {} block. The Android migration doc says to move those setti ## Introducing the Koin Migration Skills DevFeed: [Introducing the Koin Migration Skills]() Original publisher: [Read original article]() Author: Arnaud Giuliani Published: 2026-04-22T13:23:59Z Content type: article Language: en Sources: [Koin developers - Medium]() Topics: [migration](), [Kotlin](), [Claude Code](), [Android](), [Dagger]() Tags: [android](), [claude-code](), [compiler](), [dagger](), [dagger-hilt](), [dependency-injection](), [gradle](), [koin](), [kotlin](), [migration](), [module](), [verification]() ### AI overview The article introduces the Koin Migration Skill, a Claude Code plugin for migrating Kotlin and Android projects from Hilt, Dagger, Toothpick, Kodein, or older Koin versions to Koin 4.x and the Koin Compiler Plugin. It describes module-by-module inventory, ranked migration planning, compile-time verification, and human checkpoints. ### Source excerpt Hello all πŸ‘‹ Migrating a Kotlin or Android project between DI frameworks (Hilt, Dagger, Toothpick, Kodein, or older Koin versions) is one of those strategic refactors that every team puts off. It touches every module, the call sites are everywhere, and the migration plan never quite survives contact with the real codebase. We wanted to take the pain out of it. So we built the Koin Migration Skill: a Claude Code plugin that automates DI migrations to Koin 4.x and the Koin Compiler Plugin, module by module, with compile-time verification and a human-in-the-loop at every step. Koin Migration Project -- 1.0.0What it covers Initially, this project is intended to help Koin developers to migrate to use the new Koin Compiler Plugin. The skill supports every realistic migration path into modern Koin, with Koin Compiler if possible. This uses either annotations or the safe DSL: Hilt -> Koin (with koin-android-dagger bridging during migration) Dagger -> Koin Toothpick -> Koin Kodein -> Koin Koin 3.x -> Koin 4.x upgrade Classic Koin DSL -> Safe DSL Koin KSP Annotations -> Koin Compiler Plugin All paths converge on the same target: Koin 4.x with Annotations or Safe DSL, powered by the Koin Compiler Plugin for compile-time DI graph verification. How it works Project documentation is available: https://github.com/InsertKoinIO/koin-migration. Point Claude at your project and describe what you want to migrate. /plugin marketplace add InsertKoinIO/koin-migration /plugin install koin-migration@koin-migrationAdding Skill in current project The skill opens with a full inventory of your DI setup: every module, binding, qualifier, and scope. It immediately produces a ranked migration table. The NowInAndroid project below has 35 DI files across core, feature, app, and sync layers. The skill maps each one: bindings count, downstream dependants, complexity rating, and a recommended order. Modules inventory, DI features usage and mapping You can't go "big-bang" in that kind of approach. You need to st ## DIY: your own Dependency Injection library! DevFeed: [DIY: your own Dependency Injection library!]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2024-01-18T20:08:04Z Content type: tutorial Language: en Sources: [Py's blog]() Topics: [Dependency injection](), [Dagger](), [Kotlin](), [Library](), [Code](), [Graphs]() Tags: [android](), [code](), [dagger](), [dagger-hilt](), [dependency-injection](), [graph](), [how-to](), [internals](), [java](), [kotlin](), [library]() ### AI overview This tutorial explains dependency injection by progressively building a simple library, moving from manual dependency injection toward simplified versions of Google Guice, Dagger 1, and Dagger 2. It uses Kotlin and discusses dependency graphs, object graphs, factories, modules, and APIs. ### Source excerpt Dependency Injection libraries are powerful tools, but they're often also intimidating & confusing. When that happens to me, I find that understanding how a tool works helps me get over the initial scare of the dark magic internals. In this article, ... ## Slim down your Android components with LifecycleObserver DevFeed: [Slim down your Android components with LifecycleObserver]() Original publisher: [Read original article]() Author: james shvarts Published: 2022-11-17T21:11:40Z Content type: tutorial Language: en Sources: [Android Blog - Mobile Dev Notes]() Topics: [Android](), [Jetpack](), [android-development](), [Development](), [Library](), [Dagger]() Tags: [android](), [android-development](), [dagger](), [dagger-hilt](), [development](), [jetpack](), [library](), [lifecycle](), [logs]() ### AI overview A tutorial on using Android LifecycleObserver to move lifecycle-related logic out of large Activities, Fragments, and Application classes. It covers reusable observers, observing Activity and Fragment view lifecycles, observing the application process, and injecting lifecycle-aware components with Dagger/Hilt. ### Source excerpt Learn to create custom LifecycleObserver components and inject them with Dagger/Hilt ## Basic Auth with OkHttp and Retrofit DevFeed: [Basic Auth with OkHttp and Retrofit]() Original publisher: [Read original article]() Author: James Shvarts Published: 2022-11-05T22:25:12Z Content type: tutorial Language: en Sources: [Android Blog - Mobile Dev Notes]() Topics: [Kotlin](), [Android](), [HTTP](), [API](), [Dagger](), [Library]() Tags: [android](), [api](), [auth](), [authentication](), [dagger-hilt](), [dependencies](), [http](), [json](), [kotlin](), [libraries](), [payload](), [request](), [retrofit](), [viewmodel]() ### AI overview A tutorial showing how to perform authenticated HTTP GET requests in a Kotlin Android project using Basic Authentication with OkHttp, Retrofit, Dagger/Hilt, and Moshi. ### Source excerpt Basic Auth example using OkHttp, Retrofit, Dagger in a Kotlin project ## Using an Activity from a Hilt ViewModel DevFeed: [Using an Activity from a Hilt ViewModel]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2022-09-07T21:59:49Z Content type: tutorial Language: en Sources: [Py's blog]() Topics: [Android](), [Code]() Tags: [android](), [blog](), [code](), [component](), [dagger-hilt](), [dependency-injection](), [lifecycle](), [state](), [view](), [viewmodel]() ### AI overview This tutorial presents a Hilt-based technique for accessing the current Android Activity from a Hilt ViewModel. It uses scoped activity storage, an activity-scoped entry point, and lifecycle callbacks to update the reference while accounting for configuration changes and multiple activities. ### Source excerpt πŸ‘‹ Hi, this is P.Y., I work as an Android Engineer at Block. This blog shares a bit of hackery to be able to access an activity instance within a Hilt ViewModel. If you come up with other interesting ## Dagger/Hilt vs. Koin for Jetpack Compose Apps DevFeed: [Dagger/Hilt vs. Koin for Jetpack Compose Apps]() Original publisher: [Read original article]() Published: 2022-03-13T00:00:00Z Content type: comparison Language: en Sources: [Patryk Kosieradzki]() Topics: [Dagger](), [Dependency injection](), [Jetpack Compose](), [Android](), [interoperability]() Tags: [android](), [comparison](), [dagger](), [dagger-hilt](), [dependency-injection](), [interoperability](), [jetpack-compose](), [koin]() ### AI overview A comparison of Dagger/Hilt and Koin for dependency injection in Jetpack Compose Android applications. It discusses code generation, build and runtime considerations, Google's recommendation of Hilt, and two Compose integration approaches: pure Compose with navigation-compose or Fragments with ComposeView. ### Source excerpt A detailed comparison of using Hilt versus Koin for dependency injection in Jetpack Compose applications. ## Scaling navigation in Jetpack Compose: NavHost structure and a possible solution DevFeed: [Scaling navigation in Jetpack Compose: NavHost structure and a possible solution]() Original publisher: [Read original article]() Author: vaccum (Badoo) Published: 2021-12-23T09:00:11Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [Jetpack Compose](), [navigation](), [Dagger](), [Google]() Tags: [android](), [dagger](), [dagger-hilt](), [google](), [jetpack-compose](), [kotlin](), [navigation]() ### AI overview The article examines how navigation is structured in Jetpack Compose, describes Google's NavHost-based approach, and discusses the maintainability and scalability challenges it can create as the number of composable routes grows. ### Source excerpt Π’ ΠΎΠ΄Π½ΠΎΠΌ ΠΈΠ· ΠΌΠΎΠΈΡ… Π»ΠΈΡ‡Π½Ρ‹Ρ… ΠΏΡ€ΠΎΠ΅ΠΊΡ‚ΠΎΠ² я Ρ€Π΅ΡˆΠΈΠ» ΠΈΡΠΏΠΎΠ»ΡŒΠ·ΠΎΠ²Π°Ρ‚ΡŒ Jetpack Compose Π² качСствС основной Ρ‚Π΅Ρ…Π½ΠΎΠ»ΠΎΠ³ΠΈΠΈ. Π­Ρ‚ΠΎ ΠΎΠ·Π½Π°Ρ‡Π°Π»ΠΎ, Ρ‡Ρ‚ΠΎ ΠΌΠΎΡ‘ ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠ΅ Π±ΡƒΠ΄Π΅Ρ‚ ΠΈΠΌΠ΅Ρ‚ΡŒ ΠΎΠ΄Π½Ρƒ Activity, Π° вся навигация Π±ΡƒΠ΄Π΅Ρ‚ Π²Ρ‹ΠΏΠΎΠ»Π½ΡΡ‚ΡŒΡΡ с ΠΏΠΎΠΌΠΎΡ‰ΡŒΡŽ Compose. Когда я Π½Π°Ρ‡Π°Π» ΠΏΠ»Π°Π½ΠΈΡ€ΠΎΠ²Π°Ρ‚ΡŒ ΠΏΡ€ΠΎΠ΅ΠΊΡ‚, Π±ΠΈΠ±Π»ΠΈΠΎΡ‚Π΅ΠΊΠΈ Compose Navigation Π΅Ρ‰Ρ‘ Π½Π΅ Π±Ρ‹Π»ΠΎ, ΠΊΠ°ΠΊ Π½Π΅ Π±Ρ‹Π»ΠΎ ΠΈ способа Π²Π½Π΅Π΄Ρ€ΠΈΡ‚ΡŒ ViewModel Π² Composable Π±Π΅Π· использования ΠΊΠΎΠΌΠΏΠΎΠ½Π΅Π½Ρ‚ΠΎΠ² Activity, Fragment ΠΈΠ»ΠΈ View. Но ΠΏΡ€ΠΈΠΌΠ΅Ρ€Π½ΠΎ Π·Π° ΠΏΠΎΠ»Π³ΠΎΠ΄Π° Π΄ΠΎ ΠΏΡƒΠ±Π»ΠΈΠΊΠ°Ρ†ΠΈΠΈ этой ΡΡ‚Π°Ρ‚ΡŒΠΈ появилась Π±ΠΈΠ±Π»ΠΈΠΎΡ‚Π΅ΠΊΠ° Jetpack Compose Navigation, ΠΈ Dagger-Hilt стал ΠΏΠΎΠ΄Π΄Π΅Ρ€ΠΆΠΈΠ²Π°Ρ‚ΡŒ Compose. БСгодня я расскаТу ΠΎ ΠΌΠΎΡ‘ΠΌ ΠΏΡƒΡ‚ΠΈ: подСлюсь Π²ΠΈΠ΄Π΅Π½ΠΈΠ΅ΠΌ ΠΏΡ€ΠΎΠ±Π»Π΅ΠΌΡ‹ ΠΌΠ°ΡΡˆΡ‚Π°Π±ΠΈΡ€ΡƒΠ΅ΠΌΠΎΡΡ‚ΠΈ Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠΈ Π½Π° ΠΏΡ€ΠΈΠΌΠ΅Ρ€Π°Ρ… Google ΠΈ ΠΏΡ€Π΅Π΄Π»ΠΎΠΆΡƒ Π΅Ρ‘ Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎΠ΅ Ρ€Π΅ΡˆΠ΅Π½ΠΈΠ΅. Π§ΠΈΡ‚Π°Ρ‚ΡŒ Π΄Π°Π»Π΅Π΅ ## Providing AssistedInject supported ViewModel for Composable using Hilt DevFeed: [Providing AssistedInject supported ViewModel for Composable using Hilt]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2021-06-29T14:52:48Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Dependency injection](), [Dagger](), [Android](), [Jetpack Compose](), [navigation]() Tags: [android](), [compose](), [dagger](), [dagger-hilt](), [dependencies](), [dependency-injection](), [di](), [guide](), [how-to](), [interface](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [learn-coding](), [navigation-component]() ### AI overview This tutorial explains how to provide an AssistedInject-supported ViewModel for Jetpack Compose using Hilt. It describes AssistedInject runtime parameters and an EntryPoint-based approach for accessing the ViewModel factory because Hilt does not directly support this use case. ### Source excerpt Learn how to provide Hilt ViewModels with AssistedInject to Jetpack Compose Composables for dynamic dependency injection with runtime parameters. ## Simplified Android Development Using Simple-Stack DevFeed: [Simplified Android Development Using Simple-Stack]() Original publisher: [Read original article]() Author: Gabor Varadi Published: 2020-11-14T03:32:51Z Content type: tutorial Language: en Sources: [Stories by Gabor Varadi on Medium]() Topics: [navigation](), [android-development](), [Android](), [Framework](), [android-apps]() Tags: [android](), [android-app-development](), [android-apps](), [android-development](), [androiddev](), [dagger-hilt](), [fragments](), [jetpack](), [navigation](), [simple-stack]() ### AI overview An Android development article explains Simple-Stack, a navigation framework for tracking navigation state with immutable Parcelable screen identifiers. It describes the framework's origins in Flow and Mortar and its use for type-safe Fragment navigation. ### Source excerpt It's been a long time since I've wanted to write this article. Time to go at it, shall we? :) People always seem to be surprised and say, "wait, you DON'T use Jetpack ViewModel, Jetpack Navigation, and Dagger-Hilt? Then what DO you use?" This article intends to answer that. We use Simple-Stack. (If you prefer watching talks, then a talk on the same subject is available at https://www.youtube.com/watch?v=5ACcin1Z2HQ) What is Simple-Stack? Simple-Stack is a navigation framework that I've been working on since the beginning of 2017, although its roots go back to 2015 -- when we were still experimenting with multiple versions of Mortar & Flow. (The 90s kids might still remember). Following up on the original proposition by Square, "Advocating Against Android Fragments" and "Simpler Android Apps with Flow and Mortar", we've been using Single-Activity approach in our apps since 2015. Now, the history of Flow and Mortar isn't all roses. I've heard people say "we tried it and it didn't work for us". I can attest to that: we had to manage our own fork, but even with that, we hit some of its limitations over time. We needed something reliable and versioned, so we rewrote Flow's original behavior, and intended to improve upon its limitations. This rewrite is what resulted in the creation of Simple-Stack. Why Simple-Stack? Simple-Stack is based on the idea that you intend to track your navigation state as a list of immutable and Parcelable classes -- screen identifiers (which the library calls "keys"). As long as the underlying navigation implementation allows for "navigation from any state to any state", it is possible to wrap that implementation using Simple-Stack. For example, something I hear often is that "navigation with Fragments is hard". I always point out that in our code, it's been like this since 2016: backstack.goTo(new SecondScreen(detailId)); // java No explicit fragment transaction, no Bundle, no newInstance(), just calling a method. How is this possible? Isn't Fr ## Comparing Three Dependency Injection Solutions DevFeed: [Comparing Three Dependency Injection Solutions]() Original publisher: [Read original article]() Author: Adam McNeilly Published: 2020-08-22T00:00:00Z Content type: comparison Language: en Sources: [Android Essence]() Topics: [Dependency injection](), [Android](), [Dagger](), [App]() Tags: [android](), [dagger](), [dagger-hilt](), [dependency-injection](), [koin](), [unit-tests](), [viewmodel]() ### AI overview This comparison examines three approaches to dependency injection on Android: a do-it-yourself approach, Koin, and Dagger Hilt. It explains constructor and field injection, separation of concerns, and testability, then introduces the additional concerns addressed by dependency injection libraries. ### Source excerpt During a recent live stream on my Twitch channel, we explored three different solutions to dependency injection on Android. A do it yourself approach, Koin, and Dagger Hilt. Let's revisit them side by side, and look at the nuances between them, so we can determine which solution we want to use in our own applications. ## Dagger, Hilt, Koin - a comparison DevFeed: [Dagger, Hilt, Koin - a comparison]() Original publisher: [Read original article]() Published: 2020-08-05T13:02:01Z Content type: comparison Language: en Sources: [maiatoday]() Topics: [Dependency injection]() Tags: [comparison](), [dagger](), [dagger-hilt](), [dependency-injection](), [di](), [gdg](), [hilt](), [koin](), [talk]() ### AI overview A talk presented for GDG Johannesburg compares the dependency injection technologies Dagger, Hilt, and Koin. ### Source excerpt Talk presented for GDG Johannesburg comparing dependency injection technologies. slides