chrisjenx/dagger-dynamic-features — explained in plain English
Analysis updated 2026-07-21 · repo last pushed 2019-07-10
Build a large e-commerce app where users download the core instantly and heavy features like AR later.
Structure an Android app so on-demand features stay lightweight and independent from the core setup.
Use as a reference pattern for wiring Dagger 2 into apps that support modular, downloadable feature components.
| chrisjenx/dagger-dynamic-features | skevy/11.19.20-kotlin-1.4.20-bug | yingwang/filmic | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Kotlin | Kotlin | Kotlin |
| Last pushed | 2019-07-10 | 2020-11-19 | 2026-04-26 |
| Maintenance | Dormant | Dormant | Maintained |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 3/5 | 1/5 | 3/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
No README documentation, developers must read the Kotlin source directly to understand the implementation and adapt the pattern.
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.
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.
Mainly Kotlin. The stack also includes Kotlin, Dagger 2, Android.
Dormant — no commits in 2+ years (last push 2019-07-10).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.