# dagger-2 Published articles for dagger-2. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Koin Skills: Koin, the Right Way, with Your Agent DevFeed: [Koin Skills: Koin, the Right Way, with Your Agent]() Original publisher: [Read original article]() Author: Arnaud Giuliani Published: 2026-11-05T09:01:03Z Content type: release Language: en Sources: [Koin developers]() Topics: [Dependency injection](), [koin](), [Agent Skills](), [Claude Code](), [Dagger](), [dagger-hilt]() Tags: [agent](), [ai](), [ai-agent](), [android](), [android-compose](), [annotations](), [compile](), [compiler](), [compose](), [crashes](), [dagger](), [dagger-2](), [dependency](), [dependency-injection](), [di](), [diagnose](), [frameworks](), [hilt](), [koin](), [kotlin](), [skills]() ### AI overview The Koin plugin for Claude Code provides four skills for setup, writing Koin code, DI migration, and diagnosis, plus an optional Kotzilla MCP server. The skills target Koin 4.x and adapt to Annotations or DSL workflows; the Compiler Plugin is recommended but optional, and checks Koin DSL graphs at build time. Migration from Hilt, Dagger 2, Toothpick, Kodein, or older Koin versions is staged so both containers can coexist while modules move incrementally. Code-level diagnosis works without Kotzilla; runtime investigations such as slow startup, memory issues, duplicate instances, and scope leaks require the Kotzilla SDK for session data. The plugin is built for Claude Code; other agents can use skill archives and configure the MCP endpoint manually. ### Source excerpt Hello, dear Koin community 👋 AI agents write good Kotlin. With Koin, it's another story: outdated patterns, wrong DI decisions, or a build error fixed without looking at what happens at runtime. Today, I'm happy to share the official Koin skills for AI agents, released as the koin plugin for Claude Code. They help your agent write today's Koin: compile safety for all Koin DSL with Koin Compiler 1.2, migration from Dagger 2, Toothpick and other DI frameworks (Hilt...), and a koin skill that pushes back on DI mistakes. With the Kotzilla MCP Server, included in the plugin, your agent can also investigate how your app really behaves. Let's go through what it does, and how it helps you every day. Your coding agent, now writing today's KoinTL;DR The koin plugin brings four skills and one MCP server. Your agent picks the right one when a task touches dependency injection, and you can always call a skill by name. koin-setup: adds Koin to a new or legacy project (Android, Compose, KMP, Ktor), compile-safe from day one. koin: writes definitions, modules and injection in your project's style, and pushes back on DI mistakes. di-migration: moves you from Hilt, Dagger, Toothpick, or Kodein, one module at a time, while your app keeps shipping. It also upgrades Koin 3.x and Koin KSP projects. koin-diagnose: fixes Koin errors and crashes, and explains slow startup or instances created twice. Kotzilla MCP Server: included and optional. Once you sign in, it brings runtime data from your debug and production sessions. All skills target Koin 4.x and adapt to your project: Koin Annotations, Koin DSL with the Compiler Plugin, or Koin DSL without it. The Compiler Plugin is recommended, never forced. Why skills, why now Ask any AI agent to add Koin to your project today, and there is a good chance you get something like this: // Old Koin generate ... // build.gradle.kts ksp("io.insert-koin:koin-ksp-compiler:1.3.1") // KSP: replaced by the Koin Compiler Plugin // Application startKoin { module ## 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, ... ## Dagger Tips: Guide to using Dagger-Android effectively DevFeed: [Dagger Tips: Guide to using Dagger-Android effectively]() Original publisher: [Read original article]() Author: Gabor Varadi Published: 2021-02-13T05:05:50Z Content type: article Language: en Sources: [Gabor Varadi]() Topics: [Dagger](), [Dependency injection](), [dagger-hilt](), [software-architecture](), [software-development]() Tags: [android](), [dagger](), [dagger-2](), [dagger-android](), [dependency-injection](), [fragment](), [hilt](), [modularization](), [module](), [scalability](), [type-safe](), [viewmodel](), [worker]() ### AI overview Dagger-Android uses map multibinding to dispatch field injection when feature modules cannot call inject on an application component directly. With AndroidInjectionModule and @ContributesAndroidInjector, Dagger generates injector factories; DispatchingAndroidInjector looks up a factory by the target class, creates an injector, and injects the instance. For maintainability, the excerpt recommends defining a module per screen, aggregating screen modules within each feature module, then including feature aggregates in the app component, instead of collecting all screens in global activity, fragment, and ViewModel modules. Dagger-Android is superseded by Hilt, which handles common Android types through @AndroidEntryPoint, @HiltViewModel, and @HiltWorker; the article frames Dagger-Android's dynamic injection as mainly useful for legacy or modularized cases. The text is an excerpt, so it may not cover the article in full. ### Source excerpt Something people could ask me as they're reading this title: "Hold on a second, isn't Dagger-Android no longer in active development? Isn't it made obsolete with the introduction of Hilt?" Technically, yes. Dagger-Android is superseded by Hilt. So there is a good chance that if you are already using Hilt, then for the most common cases (injecting Activity, Fragment, ViewModel, Worker), you don't need to think about Dagger-Android whatsoever. However, as I still see @ContributesAndroidInjector popping up every now and then, I feel that it's best if I write an article on how it works, what it intended to solve, how to use it, and how NOT to use it (for better scalability). What was Dagger-Android? Dagger-Android was a way to field-inject classes (not necessarily just Android classes since Dagger 2.20+) without having to define a fun inject(target: MyConcreteClassTarget) injector method on the component -- as we don't know the class itself. When do you want to avoid creating fun inject(t: T) in a component? After all, this is what normally allows field injection to be type-safe. The answer is, when you can't. If you use a modularization pattern where :app contains the ApplicationComponent(or SingletonComponent), then while ApplicationComponent can see any Activity or Fragment within the app, the submodules don't see :app and therefore don't see ApplicationComponent. Therefore, they can't call component.inject(this)! On the other hand, if you were to define an Application.ActivityLifecycleCallbacks to do it automatically, that wouldn't work with the standard approach -- as you see only the superclass, but not the concrete class! So if one wants to use field injection with our provided restrictions, there are two options: Expose an interface from the child module that defines the injection targets, and implement that on the ApplicationComponent -- then make it possible to access it (for example, using the ApplicationContext for lookup) and cast it to the interface to be abl ## Structural and navigation anti-patterns in modularized Android applications DevFeed: [Structural and navigation anti-patterns in modularized Android applications]() Original publisher: [Read original article]() Author: Gabor Varadi Published: 2020-12-25T11:38:05Z Content type: article Language: en Sources: [Gabor Varadi]() Topics: [Android](), [Gradle](), [modules](), [navigation](), [Code](), [Dagger](), [Dependency injection](), [RxJava]() Tags: [android](), [android-app-development](), [antipattern](), [architecture](), [clean-architecture](), [code](), [dagger](), [dagger-2](), [dependency-injection](), [domain-driven-design](), [gradle](), [modularization](), [modules](), [navigation](), [navigation-architecture](), [rxjava]() ### AI overview This article examines structural and navigation anti-patterns in modularized Android applications. It traces the history of Android Clean Architecture and argues that organizing an application around top-level data, domain, and presentation modules can be problematic, particularly when the structure is adopted from educational examples rather than feature-based organization. ### Source excerpt Structural and navigation anti-patterns in multi-module and modularized applications: The case against "Android Clean Architecture" and the "domain" moduleTop-level "domain" module is a code smell. Merry Christmas to all! The subject of this article is one that has been on my mind for a very long time. After all, "Clean Architecture" is often seen as the end goal, the hallmark of the finest of Android application code structure -- it is the best of the very best. The name itself, "Clean Architecture", signals that it's a good thing ~ after all, who wants to work with "messy" code in comparison? Of course, the title of this article shows that this isn't the conclusion we'll come to. The following tweet is closer to our final evaluation -- let us analyze why it might be accurate. Clean architecture + Android for us was like building a beautiful sailing boat in your backyard because someone on TV convinced you it's better for crossing the sea than an inflatable, while you live in the mountains and also your house is on fire. https://t.co/iGqy25wk7m The history of "Android Clean Architecture"The origins To understand "Clean Architecture" as done on Android, we must trace it back to its roots, and where/when it was made popular in the first place. As far as I'm aware, it dates back to 2014, the original proposition in "Fernando Cejas: Architecting Android... the clean way?". It was a highly influential article, as it revolutionized the structure of Android apps. Code that is actually separated across layers (back when Fragments were untrustworthy, and all code was in OS-level components), rather than just throwing everything into 2000+ line Activities? A pioneer of its time. One interesting decision however in the representative sample code was that in order to signify the strict separation of layers, these layers were each separated from one another using top-level Gradle modules, each labeled data, domain, and presentation. As we will see, this is the downfall of the sampl ## The Corner Round-up June 2020 DevFeed: [The Corner Round-up June 2020]() Original publisher: [Read original article]() Author: Richard Moot Published: 2020-06-30T22:59:20Z Content type: news Language: en Sources: [Square Corner]() Topics: [API Economy](), [control-plane]() Tags: [2020](), [api](), [apis](), [automatically](), [beta](), [blog](), [cloud](), [compiler](), [component](), [created](), [custom](), [customers](), [dagger](), [dagger-2](), [data](), [dependency](), [dependency-injection](), [developer](), [june](), [published]() ### AI overview The roundup highlights Square developer updates: the Team API supports managing team data across platforms, including automated bulk edits and real-time third-party synchronization; Hephaestus is an open-source compiler plugin that merges Dagger 2 modules and component interfaces; and API Explorer moved from beta to general availability with improvements for API testing. It also points to Kubernetes pod security guidance, describes combining the Customers and Loyalty APIs to offer rewards on other platforms, and announces a Terminal API beta for connecting Square Terminal to custom POS systems across platforms and operating systems. This is a brief recap, with details deferred to The Corner Blog. ### Source excerpt In order to keep some of the followers still here on Medium, we wanted to provide a quick recap on some of the things that have been published over at The Corner Blog's new home https://developer.squareup.com/blog (in case you didn't know that already). We'll just be doing a quick summary of each new thing, but you can check out each topic in detail over at our new home. Manage Team Data from Any Platform with Square Team API We released a new Team API to allow managing Team data from any platform. You can track and edit large volumes of team member data automatically and synchronize data with any third-party platform in real time! Introducing Hephaestus In order to make dependency injection with Dagger 2 easier, we had created Hephaestus. It is an open source compiler plugin that automatically merges Dagger modules and component interfaces to make development more enjoyable. API Explorer Moves to General Availability The Square Developer team also transitioned the API Explorer from Beta to GA, bringing with it a lot of improvements to make testing Square APIs much more enjoyable and easy. Kubernetes - Pod Security Policies The cloud team at Square also did a write-up that provides some useful guidance and examples for handling Pod Security in Kubernetes. Reward Customers Wherever They Shop with Loyalty API and Customers API Additionally, Square Loyalty now has an API to make providing rewards to customers on other platforms. Using the Customers API and Loyalty API in combination can allow any developer to create a great rewards system, no matter where their customers are. Announcing Square Terminal API Beta Finally, we also released Terminal API, which lets you programmatically take payments using Square Terminal. This API allows developers to connect Square Terminal, an all-in-one card payments device, to their custom-built POS systems, no matter which platforms or operating systems they're developed on. Now that isn't everything that we've published since you've ## Introducing Anvil DevFeed: [Introducing Anvil]() Original publisher: [Read original article]() Author: Ralf Wondratschek Published: 2020-06-23T19:00:00Z Content type: release Language: en Sources: [Square Corner]() Topics: [Dagger](), [Dependency injection](), [dagger-hilt](), [gradle-plugin](), [Dependency management]() Tags: [android](), [anvil](), [compiler](), [component](), [components](), [dagger](), [dagger-2](), [dependency-graph](), [dependency-injection](), [developer-productivity](), [engineering](), [framework](), [github](), [google](), [gradle](), [hilt](), [ide](), [kotlin](), [kotlin-compiler](), [plugin](), [productivity]() ### AI overview Anvil is a Kotlin compiler plugin that reduces Dagger setup work by automatically adding annotated Dagger modules and component interfaces to the components for their declared scopes. Developers mark modules with `@ContributesTo` and components with `@MergeComponent`, avoiding manual component wiring and IDE syncs; the benefit grows when modules are shared across applications. The article also cites explicit module scopes, closer alignment between Dagger dependencies and Gradle modules, and easier decomposition of large composite modules. It says Hilt offers a similar `@InstallIn` feature, so Anvil is unnecessary for Hilt users; the authors report choosing Anvil because Hilt includes features they do not need and restrictions they cannot accept. ### Source excerpt Make dependency injection with Dagger 2 easier ## Keeping the Daggers Sharp DevFeed: [Keeping the Daggers Sharp]() Original publisher: [Read original article]() Author: P-Y Ricau Published: 2017-10-11T17:41:33Z Content type: article Language: en Sources: [Square Corner]() Topics: [Dagger](), [Dependency injection](), [Boilerplate]() Tags: [abstract-class](), [android](), [best-practices](), [boilerplate](), [cache](), [dagger](), [dagger-2](), [dependency-injection](), [engineering](), [kotlin](), [performance]() ### AI overview The article recommends constructor injection for ordinary classes: it avoids field-injection constraints and missed annotations, and supports immutable objects without partially constructed state. Field injection remains useful for system-created objects such as Android activities. It advises using singletons for centralized mutable state, with scoping for expensive or frequently recreated objects only in rare cases; stateless objects generally need no singleton scope. Keep bindings and implementation details together by avoiding redundant `@Provides` constructors. Static `@Provides` methods can reduce generated-code overhead, and abstract modules make Dagger reject nonstatic providers at compile time. Use abstract `@Binds` methods to map implementations to interfaces, without scoping the binding. The authors say these practices suit their small, varied teams working on a shared Android codebase and should be adapted to other contexts. ### Source excerpt Dagger 2 is a great dependency injection library, but its sharp edges can be tricky to handle. Let's go over a few best practices that... ## How to use Dagger 2 on Android with Kotlin (KAD 20) DevFeed: [How to use Dagger 2 on Android with Kotlin (KAD 20)]() Original publisher: [Read original article]() Published: 2017-04-11T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Dagger](), [Android](), [Kotlin](), [Dependency injection]() Tags: [android](), [dagger](), [dagger-2](), [dependency-injection](), [how-to](), [kotlin]() ### AI overview A tutorial on configuring Dagger 2 in an Android project using Kotlin. It covers Kotlin-specific setup, compiler and library dependencies, and implementing the application module and main dependency-injection graph. ### Source excerpt Everything Android, Kotlin and other random topics ## Introducing Cleanse: A Lightweight Dependency Injection Framework For Swift DevFeed: [Introducing Cleanse: A Lightweight Dependency Injection Framework For Swift]() Original publisher: [Read original article]() Author: Square Engineering Published: 2016-06-14T16:11:00Z Content type: release Language: en Sources: [Square Corner]() Topics: [Dependency injection](), [Swift](), [Library](), [Dagger](), [Java](), [Code generation](), [iOS]() Tags: [code-generation](), [dagger](), [dagger-2](), [dependency-injection](), [engineering](), [ios](), [library](), [objective-c](), [swift]() ### AI overview The article introduces Cleanse, a pure Swift dependency injection library. It explains the limitations of the authors' earlier Objective-C and code-generation approach and describes how Cleanse uses Swift's type system to provide compile-time safety and a feature set inspired by Guice and Dagger 2. ### Source excerpt Cleanse is a pure Swift dependency injection library. ## The Journey of Android Engineers: Tech Talks DevFeed: [The Journey of Android Engineers: Tech Talks]() Original publisher: [Read original article]() Author: Square Engineering Published: 2016-03-03T17:11:00Z Content type: release Language: en Sources: [Square Corner]() Topics: [Android](), [Dagger](), [Kotlin]() Tags: [android](), [android-development](), [bias](), [bugs](), [dagger](), [dagger-2](), [discussion](), [engineering](), [kotlin](), [lightning](), [panel](), [talks](), [videos]() ### AI overview The event videos cover four practical topics in Android engineering: John Rodriguez explains why Square Register incrementally migrated from Dagger to Dagger 2 as its scope hierarchy and complexity strained the existing setup. Effie Barak shares what was easy, difficult, surprising, and exciting when she moved from Windows Phone to Android after a decade at Microsoft. Eric Burke offers tips for interrupting unconscious bias before, during, and after interviews. Christina Lee describes how Highlight built a Redux-like framework in Kotlin to simplify state management and reduce bugs in challenging UI components, while keeping its Android app and existing expertise. ### Source excerpt Lightning talks and panel discussion videos. ## Using Dagger 1 and Kotlin DevFeed: [Using Dagger 1 and Kotlin]() Original publisher: [Read original article]() Author: Michael Evans Published: 2016-02-17T18:43:25Z Content type: article Language: en Sources: [Gadget Habit]() Topics: [Dagger](), [Kotlin](), [Android](), [Compiler](), [software-development]() Tags: [2](), [android](), [android-development](), [beginner](), [compiler](), [dagger](), [dagger-2](), [dependencies](), [development](), [di](), [java](), [kotlin](), [property]() ### AI overview This article explains how to use Dagger 1 with Kotlin in an Android app. It describes Kotlin annotation-processing limitations, Dagger module compilation problems, and a workaround that converts modules to Java classes. It also explains how to inject Kotlin properties by targeting the annotation at the backing field because Dagger does not support method injection. ### Source excerpt Unless you've been hiding from all the news about Android development, you've likely heard about Kotlin (which hit version 1.0 on Monday!). I've been toying around with it lately (the Kotlin Koans are a great place to start for a beginner) and wanted to try building an app with it - that is, until I hit a few road blocks. Personally, I'm still a fan of Dagger 1 (or as I refer to it, Dagger Classic), and when I started working on my Kotlin app, that's what I was planning to use. I knew Annotation Processing support was a relatively new addition to Kotlin, so I began to search for some information about how to get Dagger to play nicely with the Kotlin compiler. There's a lot of information about using Dagger 2 with Kotlin but not so much about Dagger Classic. Finally, I stumbled upon this article, which said, "Unfortunately, Square's Dagger 1 does not appear to work with Kotlin while Google's Dagger 2 does". Bummer. This didn't really deter me, however, because I'm stubborn like that. So I proceeded to give it a try with kapt1 anyway (which seemed like it might do what I want). Modules The first thing I did was try to create the various Dagger Modules that I'd need, which is where I hit my first roadblock. Attempting to compile my module gave the following error: 1 Error:Modules must not extend from other classes: org.michaelevans.example.AppModule My intial thought was that Kotlin was causing my Module to extend Any, rather than Object. (Any is the root of the class hierarchy in Kotlin, similar to the way that Object is the root of the Java class hierarchy.) Upon closer inspection, that didn't seem to be the issue, but rather than get hung up on this - I just converted my modules to Java classes and decided to come back to this issue later. @Inject So now I had my modules set up, and I went about trying to @Inject some fields on an Activity or two. This yielded another problem: Kotlin doesn't have fields, and we obviously can't do constructor injection on something f