# 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. ## 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: release Language: en Sources: [Koin developers]() Topics: [koin](), [dagger-hilt]() Tags: [android](), [bridging](), [claude](), [claude-code](), [compiler](), [dagger](), [dagger-hilt](), [dependency-injection](), [di](), [dsl](), [github](), [hilt](), [human-in-the-loop](), [install](), [inventory](), [kodein](), [koin](), [kotlin](), [ksp](), [mapping](), [migration](), [skills]() ### AI overview The Koin Migration Skill is an open-source Claude Code plugin for moving Kotlin and Android projects to Koin 4.x, with the Koin Compiler Plugin when possible. It supports migrations from Hilt, Dagger, Toothpick, Kodein, older Koin versions, classic Koin DSL, and Koin KSP annotations. It inventories modules and bindings, ranks them by complexity and dependencies, then recommends a leaf-first sequence. Migrations proceed module by module, with the old container kept alongside Koin and Hilt bindings bridged through koin-android-dagger or @EntryPoint bridges. Before editing files, the skill presents a plan and asks about key choices, including whether to make a project-wide Kotlin version update or use Safe DSL without the compiler plugin. Its stated safeguards include per-module, configuration-group, and full-graph compile-time checks, which can be temporarily disabled. The excerpt also notes KMP support and modern Koin conventions. ### 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](), [Library]() Tags: [android](), [api](), [build](), [compiler](), [dag](), [dagger](), [dagger-2](), [dagger-hilt](), [dependencies](), [dependency-graph](), [dependency-injection](), [di](), [diy](), [extension-function](), [factory](), [implement](), [internals](), [java](), [kotlin](), [library](), [map](), [module]() ### AI overview The article builds intuition for dependency injection by progressing from manual construction to simplified versions of Google Guice, Dagger 1, and Dagger 2. Manual injection creates dependencies in order at a dedicated configuration point, but becomes difficult as collaborators grow. The excerpt defines an ObjectGraph as the entry point that supplies requested instances, a Factory as the creator of a type using dependencies from the graph, and a Module as the provider of factories for particular types. The article frames a dependency graph as a DAG and provides Kotlin examples; the supplied text ends while introducing Module, so later implementation details are not available here. ### 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, ... ## Dependency Injection in Legacy Code DevFeed: [Dependency Injection in Legacy Code]() Original publisher: [Read original article]() Author: blundell Published: 2023-10-19T12:26:59Z Content type: tutorial Language: en Sources: [Blundell]() Topics: [Dependency injection](), [dagger-hilt](), [Android](), [Dagger](), [legacy systems](), [software-development]() Tags: [android](), [dagger](), [dagger-hilt](), [dependency-injection](), [di](), [hilt](), [intermediate](), [legacy-code](), [reference]() ### AI overview For Android legacy singletons or other classes outside the architecture managed by Hilt, the excerpt describes using a Hilt EntryPoint to retrieve dependencies from the existing Dagger graph. Define an interface annotated as an entry point, add a function for each required binding (including qualifiers), and install it in the appropriate component. The legacy code can then use the entry point through a Context reference. The approach assumes the required Dagger modules and bindings already exist; the excerpt says it does not work if the class cannot obtain a Context. ### Source excerpt This post explains how you can inject dependencies into Android legacy singletons, or any classes that aren't conforming to your current Android architecture, using Dagger & Hilt. I'll cut straight to the chase, if you have a reference to Context, (which you usually always do in spaghetti legacy code) then you can use your normal [...] The post Dependency Injection in Legacy Code first appeared on Blundell. ## 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](), [dagger-hilt](), [Dagger](), [software-development]() Tags: [android](), [android-development](), [custom](), [dagger](), [dagger-hilt](), [hilt](), [jetpack](), [lifecycle]() ### AI overview A custom LifecycleObserver can move lifecycle callbacks out of oversized Android components. Implement the observer interface and override only the callbacks you need, then register it with an Activity or Fragment lifecycle; observe a Fragment's view lifecycle through its viewLifecycleOwner, which is unavailable in onCreate. Observers need not be explicitly removed, and multiple observers can organize or share lifecycle work. The excerpt also describes observing the Application/process lifecycle and says the observer can be injected with Dagger or Hilt, but its scoping discussion is truncated, so it does not establish how to configure or reuse scoped instances. ### 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](), [client library](), [Dagger]() Tags: [android](), [annotations](), [api](), [auth](), [authentication](), [basic](), [configure](), [custom](), [dagger](), [dagger-hilt](), [dependencies](), [gradle](), [header](), [hilt](), [http](), [kotlin](), [kotlin-android](), [okhttp](), [project](), [retrofit]() ### AI overview The post outlines a Kotlin Android example that uses OkHttp and Retrofit for an HTTP GET request to an endpoint requiring Basic Authentication. It describes routing outgoing requests through a custom component that sets the authentication header, then wiring the repository interface and implementation through Dagger/Hilt for use in a ViewModel. Moshi is listed for JSON handling, with its annotations tied to the API contract. The excerpt does not include the code or specify the exact header construction. ### 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: [dagger-hilt](), [software-development](), [Test-driven development]() Tags: [android](), [dagger-hilt](), [dependency-injection](), [hilt](), [viewmodel]() ### AI overview The excerpt presents a Hilt workaround for accessing the current Activity from a ViewModel without injecting the Activity directly, which could leak across configuration changes. It stores the Activity in a scoped provider, exposes that provider through an Activity-scoped Hilt entry point, and updates the reference through lifecycle callbacks. The approach checks that the Activity is Hilt-aware and is described as supporting multiple simultaneously created Activities while reusing the logical component across configuration recreation. The excerpt omits code and identifiers, so implementation details cannot be fully assessed. ### 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. ## Input validation in Jetpack Compose DevFeed: [Input validation in Jetpack Compose]() Original publisher: [Read original article]() Author: Denys Rudenko Published: 2021-08-22T16:42:02Z Content type: tutorial Language: en Sources: [Denis Rudenko]() Topics: [Jetpack Compose](), [Data validation](), [User interface design](), [Process](), [User Experience](), [dagger-hilt](), [parcelable]() Tags: [android](), [android-app-development](), [androiddev](), [androiddevweekly](), [compose](), [dagger](), [dagger-hilt](), [death](), [error](), [input](), [jetpack](), [jetpack-compose](), [name](), [null](), [observable](), [parcelable](), [process](), [restoration](), [save](), [savedstatehandle](), [sealed-class](), [stateflow](), [switchmap](), [validation]() ### AI overview The excerpt shows a Jetpack Compose form that validates name and credit card inputs and restores useful editing state after process death. A Parcelable input wrapper stores each value with an optional error resource ID in SavedStateHandle; StateFlows expose the fields and combine their validity to control whether the continue button is enabled. The ViewModel can validate as users type or defer validation until continue is clicked, and emits one-time events for success or errors. To restore the editing experience, it tracks the last focused field and uses focus requesters, focus events, and the keyboard controller to restore focus and show the keyboard; IME actions move from name to card number. On successful submission it clears focus and hides the keyboard. The excerpt notes a StateFlow/LiveData distinction for switchMap/flatMapLatest scenarios and suggests debouncing as a possible improvement to auto-validation. Examples use Dagger Hilt and Compose 1.3.0-alpha03. ### Source excerpt This post will not only focus on manual & auto validation of TextField inputs, but also on how to provide a nice UX by handling process death, including highlighting the last focused field upon restoration. https://medium.com/media/7d776a0ec6ff89810e194adf54680973/hrefSetup We'll use composables, viewModels & Dagger Hilt in these samples. Part 1: InputWrapper Let's create a wrapper for inputs, so it can contain both input value and errorId, if there is a validation error. Class is parcelable, so we can save it inside savedStateHandle later. https://medium.com/media/6c74ba5b4f958d63646a819643b45620/hrefPart 2: ViewModel (simplified version)https://medium.com/media/39bf975a63461cd00f68b8360c6a8f6b/href We're getting a stateFlow from the savedStateHandle using .getStateFlow extension. Using savedStateHandle here allows us to retain the latest data after process death happens. You can also use getLiveData, it's a matter of personal preferences unless you plan to perform observable.switchMap/flatMapLatest type of operations, since there is a subtle difference between stateFlow & liveData in such scenarios described here & change proposal created. areInputsValid stateFlow is combining name & creditCardNumber flows into a single one. The results it returns depend on whether input fields are valid or not. It's invoked whenever there is new emition to name or creditCardNumber flows. We'll use it's value to control buttons enabled/disabled state in our composable. _events will be used for one time events emission to the view layer. ScreenEvent is a sealed class representing all of our one time events. onNameEntered & onCardNumberEntered will be invoked when user enters symbols inside the TextField. We find out whether the input is valid by using an InputValidator object. It's returning either a string resource id containing error message, or a null. Latter means that input is valid. We store the new value & errorId using: https://medium.com/media/d9ad9c61328481f3318c143e6daf3 ## 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