whatisgithub

What is dagger-dynamic-features?

chrisjenx/dagger-dynamic-features — explained in plain English

Analysis updated 2026-07-21 · repo last pushed 2019-07-10

2KotlinAudience · developerComplexity · 3/5DormantSetup · moderate

In one sentence

A Kotlin code example showing Android developers how to use Dagger 2 with Dynamic Feature Modules, enabling on-demand feature downloads without bloating the initial app install.

Mindmap

mindmap
  root((repo))
    What it does
      On-demand feature downloads
      Dagger 2 dependency wiring
      Keeps core app lightweight
    Tech stack
      Kotlin
      Dagger 2
      Android
      Dynamic Feature Modules
    Use cases
      Large e-commerce apps
      Heavy optional features
      Modular app architecture
    Audience
      Android developers
      Intermediate to advanced
      Reference pattern

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Build a large e-commerce app where users download the core instantly and heavy features like AR later.

USE CASE 2

Structure an Android app so on-demand features stay lightweight and independent from the core setup.

USE CASE 3

Use as a reference pattern for wiring Dagger 2 into apps that support modular, downloadable feature components.

What is it built with?

KotlinDagger 2AndroidGradle

How does it compare?

chrisjenx/dagger-dynamic-featuresskevy/11.19.20-kotlin-1.4.20-bugyingwang/filmic
Stars222
LanguageKotlinKotlinKotlin
Last pushed2019-07-102020-11-192026-04-26
MaintenanceDormantDormantMaintained
Setup difficultymoderateeasymoderate
Complexity3/51/53/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

No README documentation, developers must read the Kotlin source directly to understand the implementation and adapt the pattern.

So what is it?

This repository is a code example showing how to use two specific Android development tools together: Dagger 2 and Dynamic Feature Modules. It is designed for Android developers who want to build apps where users can download certain features on demand, rather than having everything bundled into the initial app installation. By using Dagger 2, a popular tool for managing how different parts of an app share data and resources, this project demonstrates how to keep those on-demand features lightweight and independent. At a high level, the project tackles a common headache for Android developers: managing dependencies when app features are downloaded separately. Normally, Dagger creates a web of connections at the core of an application. However, when a feature is downloaded later, it cannot always access that central web without bloating the initial download. This codebase provides a working example of how to structure an app so that the core setup and the on-demand features can communicate smoothly without breaking the app's architecture. The primary audience for this project is intermediate to advanced Android developers working with Kotlin. For example, if a company is building a large e-commerce app and wants users to download the core shopping experience instantly, but only download the heavy augmented-reality room visualizer if the user specifically clicks on it, this project shows how to wire that up. It serves as a practical reference rather than a standalone app, giving developers a pattern to copy and adapt for their own applications. Because the README does not contain any documentation, the project relies entirely on the code itself to explain its approach. Developers exploring this should expect to dig directly into the Kotlin files to understand the specific implementation choices and how the dynamic feature modules are configured.

Copy-paste prompts

Prompt 1
How do I configure Dagger 2 to provide dependencies to a Dynamic Feature Module without including them in the base APK?
Prompt 2
Show me how to structure an Android app using Dynamic Feature Modules so that a feature downloaded on demand can access core app dependencies set up by Dagger.
Prompt 3
What is the correct Dagger component and subcomponent pattern for Android Dynamic Feature Modules so the core graph stays in the base module?
Prompt 4
How do I keep an on-demand Android feature module lightweight while still letting it communicate with the Dagger dependency graph in the app's core module?

Frequently asked questions

What is dagger-dynamic-features?

A Kotlin code example showing Android developers how to use Dagger 2 with Dynamic Feature Modules, enabling on-demand feature downloads without bloating the initial app install.

What language is dagger-dynamic-features written in?

Mainly Kotlin. The stack also includes Kotlin, Dagger 2, Android.

Is dagger-dynamic-features actively maintained?

Dormant — no commits in 2+ years (last push 2019-07-10).

How hard is dagger-dynamic-features to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is dagger-dynamic-features for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.