# Dagger A compile-time dependency injection framework for Java, Kotlin, and Android. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Simple MVI Architecture Approach Using LiveData DevFeed: [A Simple MVI Architecture Approach Using LiveData]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2026-09-17T04:13:15.404035Z Content type: opinion Language: en Sources: [Dustin Summers]() Topics: [Android](), [Dagger]() Tags: [architecture](), [architecture-pattern](), [error](), [livedata](), [loading](), [mvi]() ### AI overview A talk from Android Summit 2019 discusses a simple implementation of the MVI architecture pattern using LiveData and the Loading, Content, Error pattern. ### Source excerpt This was a talk provided by myself and Dan Lowe at Android Summit, 2019. In this we discuss a simple approach to the MVI (Model, View, Intent) Architecture Pattern using LiveData and the common Loading, Content, Error Pattern. Link to Dan's blog post is here which is what our talk was based around. ## Hilt in Android Auto: From Manual Factories to a Cleaner Screen Provider DevFeed: [Hilt in Android Auto: From Manual Factories to a Cleaner Screen Provider]() Original publisher: [Read original article]() Author: FunkyMuse Published: 2026-06-05T09:30:00Z Content type: tutorial Language: en Sources: [FunkyMuse]() Topics: [Android](), [Dagger](), [Dependency management](), [App](), [Testing]() Tags: [android](), [android-auto](), [dagger](), [dependency-management](), [di](), [how-to](), [testing]() ### AI overview A tutorial on replacing manual dependency wiring in an Android Auto Car App with compile-time dependency injection using Hilt. It explains using Hilt entry points, screen providers, multibinding, and a central module to reduce constructor boilerplate and improve testability. ### Source excerpt If you've ever followed the Android Auto Codelabs, you've seen the "sample" way of building a Car App. It works, it's functional, but as soon as you try to scale it beyond a simple demo, you hit a wall: Dependency Management. Keep in mind this is only one way to wire things, I'm pretty sure many others exist, I'm exploring things on Android Auto and Android Wear lately and how to connect and w... ## 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 ## Re: Dependency Injection vs. Service Locators DevFeed: [Re: Dependency Injection vs. Service Locators]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-02-20T05:10:16Z Content type: opinion Language: en Sources: [Zac Sweers]() Topics: [Dependency injection](), [Dagger](), [koin](), [Kotlin](), [service](), [multiplatform]() Tags: [dagger](), [dependency-injection](), [koin](), [kotlin](), [metro](), [service]() ### AI overview The article compares dependency injection frameworks with service locators, focusing on compile-time validation, testing, isolation, generated performance, and the tradeoff of requiring more explicit code. It discusses Metro, Dagger, Hilt, Anvil, kotlin-inject, Koin, and manual dependency injection. ### Source excerpt This is a port of a write-up I did in the Kotlin Lang slack here in response to the question "Dagger vs. Hilt vs. Koin vs. Metro vs. . Serious question: Are there any compelling reasons to switch from Koin to Metro in a ## From Dagger to Metro DevFeed: [From Dagger to Metro]() Original publisher: [Read original article]() Author: Andrius Semionovas Published: 2026-02-12T00:00:00Z Content type: article Language: en Sources: [Vinted]() Topics: [Dependency injection](), [Android](), [migration](), [Kotlin](), [Dagger](), [interoperability](), [Compiler](), [modules](), [Gradle]() Tags: [android](), [compatibility](), [compilation](), [dagger](), [dependency-injection](), [gradle](), [interoperability](), [kotlin](), [migration](), [modules]() ### AI overview Vinted's Android developers describe their migration from Dagger and related dependency-injection tools to Metro. The article covers their large, modular codebase, Anvil's maintenance status and K2 migration pressure, and Metro's interoperability with Dagger, Anvil, and kotlin-inject. ### Source excerpt Metro - modern and kotlin injection framework created by Zac Sweers. And we, Android developers at Vinted, officially and fully migrated to it! It was quite a bumpy ride for our huge codebase. Our story begins... ## Container Use for Locally Sandboxed, Background Agents in Zed DevFeed: [Container Use for Locally Sandboxed, Background Agents in Zed]() Original publisher: [Read original article]() Author: Jeremy Adams Published: 2025-07-30T00:00:00Z Content type: tutorial Language: en Sources: [Zed Industries - Blog]() Topics: [Containers](), [AI-assisted coding](), [Git](), [Command-line interface](), [MCP](), [Dagger]() Tags: [agents](), [ai-coding-agents](), [cli](), [container](), [dagger](), [git](), [mcp]() ### AI overview This article explains how to use Zed with Container Use to run background coding agents in isolated containerized environments while maintaining parallel Git worktrees. It describes using MCP, Dagger containers, and CLI commands to manage and inspect agent environments. ### Source excerpt Run AI agents in parallel without interference using containerized environments and Git Worktrees. ## GameChanger and Anvil DevFeed: [GameChanger and Anvil]() Original publisher: [Read original article]() Author: GameChanger Published: 2024-09-18T04:00:00Z Content type: article Language: en Sources: [GameChanger]() Topics: [Dagger](), [Dependency injection](), [Android](), [Architecture & Design](), [Code quality]() Tags: [android](), [code-quality](), [dagger](), [dependency-injection](), [development-tools](), [workflows]() ### AI overview GameChanger describes how its App Platform team integrates Anvil with an existing Dagger setup in an Android codebase. The effort streamlines dependency injection and supports modularization, consistent architecture, reduced cognitive load, faster onboarding, and improved code quality. ### Source excerpt At GameChanger, we have a dedicated App Platform team that focuses on scaling our engineering organization and supporting development teams across the company. Our mission is to make building things the right way the easy way for all developers at GameChanger. This involves: Implementing and maintaining core infrastructure like dependency injection systems Creating and improving development tools and workflows Establishing best practices and architectural patterns Providing support and guidance to feature teams By having a dedicated team focus on these foundational aspects, we achieve several benefits: Consistency across the codebase, making it easier for developers to switch between projects Reduced cognitive load for feature teams, allowing them to focus on business logic Faster onboarding for new team members Improved code quality and maintainability The work on integrating Anvil with our existing Dagger setup is a prime example of how the App Platform team contributes to these goals. By streamlining our dependency injection process, we're making it easier for all teams to build features efficiently and correctly. With this context in mind, let's explore the technical details of our setup and why we chose to augment Dagger with Anvil. What's the setup? The Android codebase has the following Dagger components: a longstanding Application Component, a User Component that lives for as long as the user is logged in, and Game Components that last for as long as any live game. Features usually involve a fragment to render UI and a view model to manage business logic and state. Said view model is supplied by a factory in either the Application Component or User Component and pulls in dependencies from the rest of the Dagger graph that may come from any of the mentioned components. So Why Anvil? 1. Anvil makes modularization easy: We're following, as shown in the diagram above, a format for modules across the codebase to follow that involve the inversion of control princi ## 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, ... ## 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](), [Android](), [android-development](), [legacy](), [Development]() Tags: [android](), [android-development](), [dagger](), [dependency-injection](), [development](), [intermediate](), [legacy](), [legacy-code](), [reference]() ### AI overview This tutorial explains how to use Dagger and Hilt entry points to inject dependencies into Android legacy singletons and other classes that are not managed by the current architecture. It focuses on cases where the legacy code can access a Context and describes defining an entry-point interface for required bindings. ### 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. ## Why Dagger's Provider Interface Is Simple and Flexible DevFeed: [Why Dagger's Provider Interface Is Simple and Flexible]() Original publisher: [Read original article]() Published: 2023-08-10T02:55:50Z Content type: opinion Language: en Sources: [Blogs on Ryan Harter]() Topics: [Dagger](), [Dependency injection](), [Code]() Tags: [apis](), [dagger](), [dependency-injection](), [interface](), [jvm]() ### AI overview The article examines how Dagger's javax.inject.Provider interface supports generated dependency providers and flexible object-creation strategies. It discusses shared instances, lazy and eager instantiation, and lifecycle scoping. ### Source excerpt I recently gave a presentation about how Dagger works under the hood, and I was once again struck by the elegance of the javax.inject.Provider interface. The interface is so simple it almost seems useless, but it's also incredibly flexible, and forms the basis of much of the code generated by Dagger. Like many dependency injection frameworks for JVM languages, Dagger uses and builds on the standard set of annotations for injectable classes defined in JSR-330 and provided in the javax.inject package. ## 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 ## Things you can do in Android Studio DevFeed: [Things you can do in Android Studio]() Original publisher: [Read original article]() Published: 2022-06-18T08:38:44Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Android Studio](), [IntelliJ IDEA](), [Dagger](), [Code]() Tags: [algorithms](), [android](), [android-studio](), [blog](), [career](), [code](), [compose](), [copy](), [dagger](), [dependency](), [development](), [engineering](), [finance](), [function](), [functional](), [growth](), [intellij](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [productivity](), [scopes](), [software](), [startups](), [thoughts](), [tooling](), [training](), [tutorial]() ### AI overview A practical list of Android Studio and IntelliJ productivity features, including excluding generated files with Scopes, using scratch files to test ideas, editing multiple lines simultaneously, and accessing clipboard history. ### Source excerpt Based on a recent discussion on Twitter: a list of things that you can do in Android Studio which can make your life much easier. Hide files you don't care about If you work in a project with lots of generated code (e.g.: you use Dagger), you can exclude generated files from searches using Scopes: ## 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 ΠΈ ΠΏΡ€Π΅Π΄Π»ΠΎΠΆΡƒ Π΅Ρ‘ Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎΠ΅ Ρ€Π΅ΡˆΠ΅Π½ΠΈΠ΅. Π§ΠΈΡ‚Π°Ρ‚ΡŒ Π΄Π°Π»Π΅Π΅ ## 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: [Stories by Denis Rudenko on Medium]() Topics: [Jetpack Compose](), [Dagger](), [Processes](), [User experience (UX)]() Tags: [android](), [android-app-development](), [androiddev](), [androiddevweekly](), [dagger](), [jetpack-compose](), [savedstatehandle](), [stateflow](), [ux](), [validation](), [viewmodel]() ### AI overview This tutorial demonstrates manual and automatic input validation in Jetpack Compose. It uses composables, ViewModels, Dagger Hilt, StateFlow, and savedStateHandle to preserve input state after process death, validate fields, control button state, and emit success or error events. It also discusses restoring focus and improving keyboard-related user experience. ### 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 ## 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. ## Integration verbosity and good layering DevFeed: [Integration verbosity and good layering]() Original publisher: [Read original article]() Published: 2021-04-07T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [Android](), [XML](), [Dagger](), [SQLite](), [MySQL]() Tags: [abstraction](), [dagger](), [dependency](), [design](), [env-file-security](), [integrations](), [mysql](), [net-conf]() ### AI overview The article argues that integration verbosity can be a consequence of good layering. General-purpose libraries such as view binding, Dagger, SQLDelight, and RecyclerView must leave higher-level integration and configuration decisions to their callers, enabling more flexible libraries and platforms. ### Source excerpt One of my favorite non-features from building view binding is that it lacks integration with activities or fragments. If you use view binding with activities or fragments, however, this fact might be to your disdain. Every activity using view binding is forced to do something along the lines of: override fun onCreate(savedInstanceState: Bundle) { super.onCreate(savedInstanceState) val binding = ProfileViewBinding.inflate(layoutInflater) setContentView(binding.root) // Do stuff with 'binding' } This is textbook verbosity, and some would argue boilerplate. It only gets worse with fragments (due to their poor design and to no specific fault of view binding which works the same as any View reference). View binding exists at a different layer of abstraction than is appropriate for integration with higher-level components like activities or fragments. It serves as a type-safe representation of a schema declared in an XML file and that's it. It has no more knowledge of activities and fragments than the associated R.layout.profile_view integer does. Higher-level libraries like androidx.activity and androidx.fragment have integrations with those R.layout integers. If you're upset that view binding has no turn-key solution for activities and fragments then this is the tree you should be barking up. View binding wasn't built with verbosity in mind. Hell, it's not even that verbose. It ended up this way because it's the design the layer of abstraction it operates at demands. The same pattern occurs in some of my other favorite libraries. Dagger offers you nothing and requires that you build up the dependency injectors, their hierarchy, and their lifecycle entirely yourself. SQLDelight makes you specify database info in the build configuration and a database driver in the runtime API. RecylerView requires at minimum an adapter subtype and to choose and configure a layout manager. The layer at which these tools operate is sufficiently general such that their good design requires ## Migrating from Square AssistedInject to Dagger AssistedInject DevFeed: [Migrating from Square AssistedInject to Dagger AssistedInject]() Original publisher: [Read original article]() Author: Jake Wharton Published: 2021-03-31T00:00:00Z Content type: tutorial Language: en Sources: [Jake Wharton]() Topics: [Dagger](), [migration](), [interoperability](), [Library](), [Open Source]() Tags: [bug-fixes](), [dagger](), [interoperability](), [library](), [migration](), [open-source]() ### AI overview This tutorial explains how to migrate from Square AssistedInject to Dagger AssistedInject. It covers staged upgrades, annotation changes, interoperability considerations, and differences between the two libraries, while also noting that InflationInject has its own repository. ### Source excerpt This post was published externally on Cash App Code Blog. Read it at https://code.cash.app/assisted-inject-is-dead-long-live-assisted-inject. ## IntoSet: Dagger Multibindings and Architecture DevFeed: [IntoSet: Dagger Multibindings and Architecture]() Original publisher: [Read original article]() Published: 2021-03-05T09:30:09Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Dagger](), [Kotlin](), [implementation](), [Gradle]() Tags: [algorithms](), [android](), [architecture](), [blog](), [career](), [components](), [compose](), [dagger](), [development](), [engineering](), [finance](), [functional](), [gradle](), [growth](), [implementation](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This tutorial explains how Dagger multibindings with sets can inject collections and register components across Gradle modules. It presents uses including decoupling runtime initialization, isolating third-party SDKs behind facades, reducing dependencies, and registering Moshi adapters. ### Source excerpt Featured in Kotlin Weekly #240 Dagger is typically my DI framework of choice for large projects (insert controversy here) and while most people are familiar with the basic concepts, some aspects immediately cause internal panic when mentioned. Multibindings is one of them, which is a shame because it's a highly useful pattern which can solve real problems. ## Using @JvmSuppressWildcards to resolve Kotlin and Java generic type issues DevFeed: [Using @JvmSuppressWildcards to resolve Kotlin and Java generic type issues]() Original publisher: [Read original article]() Author: Chao Zhang Published: 2021-02-23T16:01:15Z Content type: tutorial Language: en Sources: [Stories by Chao Zhang on Medium]() Topics: [Kotlin](), [generics](), [Java](), [Android](), [Dagger](), [recyclerview]() Tags: [android](), [android-app-development](), [compilation-error](), [compiler](), [dagger](), [generics](), [java](), [kotlin](), [kotlin-generics](), [recyclerview]() ### AI overview This tutorial explains how Kotlin generics interact with Java in mixed Kotlin-Java codebases, including Android applications and Dagger-based dependencies. It shows how the @JvmSuppressWildcards annotation can resolve compilation and type-inference problems when Kotlin generic APIs are consumed by Java code. ### Source excerpt Photo: amirali mirhashemian from Unsplash If generic types are exposed in Kotlin API, consider @JvmSuppressWildcards so that your Java consumer can compile successfully. Kotlin generics are different from (in my opinion, smarter than) Java generics. Kotlin generics has declaration-site variance and type projections, which are officially documented here. Generics is a gigantic topic itself. My usual practice is to leverage IDE warnings and compiler error messages to fix my code since they usually contain the necessary information to show you where you did wrong. However, as we are Kotlinizing our codebase from Java to Kotlin, it is possible to have a sandwich-style code dependency that mixes Java code and Kotlin code. In such cases, when dealing with generics, your compiler and IDE may not be smart enough to help you fix those issues. What is sandwich-style code dependency?πŸ₯ͺ Sandwich-style Kotlin conversion At a certain time during your Java to Kotlin conversion, there could be some Java code depending on Kotlin code, which in turn depends on Java code. A typical example on Android is that your app code in Java depending on your library in Kotlin, which depends on Android SDK in Java. Even if your app code is written purely in Kotlin, the sandwich might still exist: The Java-based annotation processing Dagger, depends on your app code in Kotlin, which depends on Android SDK in Java. Now let's look at how the secret sauce @JvmSuppressWildcards can help us by making our generic sandwich tasty. Sandwich: List in RecyclerView methodshttps://medium.com/media/87fd0c63db2b9c82af2b241bf61cef31/href With the code above, the following compilation error is observed: MyChildAdapter.java:13: error: name clash: onBindViewHolder(MyViewHolder,int,List) in MyChildAdapter overrides a method whose erasure is the same as another method, yet neither overrides the other The error message leads us to think that we need to change our type here: Change the Kotlin generic para ## 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: tutorial Language: en Sources: [Stories by Gabor Varadi on Medium]() Topics: [Dagger](), [Android](), [Architecture & Design](), [Development](), [Scalability]() Tags: [android](), [dagger](), [dagger-2](), [dagger-android](), [dependency-injection](), [development](), [guide](), [interface](), [modularization](), [module](), [scalability]() ### AI overview A guide to using Dagger-Android, explaining its field-injection approach, the modularization constraints it addresses, and alternatives involving interfaces or shared superclasses. The article notes that Dagger-Android has been superseded by Hilt for common injection cases. ### 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 ## 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: article Language: en Sources: [Square Corner Blog - Medium]() Topics: [API](), [Dependency injection](), [Compiler](), [Dagger](), [Kubernetes]() Tags: [api](), [apis](), [cloud](), [compiler](), [dagger](), [dagger-2](), [dependency-injection](), [kubernetes](), [payments](), [pos](), [security]() ### AI overview The Corner Round-up June 2020 recaps selected publications from Square's developer blog. It covers the Square Team API, the Hephaestus open source compiler plugin for Dagger 2, API Explorer's move from beta to general availability, Kubernetes pod security guidance, Loyalty and Customers APIs, and the Square Terminal API beta. ### 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: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Dagger](), [Dependency injection](), [Kotlin](), [Android](), [Gradle](), [Compiler]() Tags: [android](), [compiler](), [dagger](), [dagger-2](), [dependency-injection](), [engineering](), [gradle](), [kotlin]() ### AI overview Square introduces Anvil, a Kotlin compiler plugin that automatically adds Dagger modules and component interfaces to required Dagger components. The tool reduces repetitive setup steps in large modularized Android codebases while preserving compile-time dependency graph validation. ### Source excerpt Make dependency injection with Dagger 2 easier [Next page]()