# mqzhangw/JIMU

一种简单有效的android组件化方案，支持组件的代码资源隔离、单独调试、集成调试、组件交互、UI跳转、生命周期等完整功能。

Repository: https://github.com/mqzhangw/JIMU
Canonical: https://ross.abutalabs.com/products/jimu
Language: Java
License: Apache-2.0
License Family: permissive
Topics: android-application, android-component, android-architecture
Last push: 2021-06-13T15:55:29+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3299, "days_push": 1907, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2411, forks 382 (observed 2026-08-28T04:06:44.436896+00:00)

## What it is
JIMU is an Android componentization framework that isolates each feature module's code and resources so components can run and be debugged independently, then be assembled into a complete app. It provides interface-based inter-component communication, scheme/host routing for UI navigation, generated route tables, dynamic component loading/unloading, and ordered component initialization.

## Use cases
- split a large android app into independently debuggable modules
- decouple android feature modules so code and resources are fully isolated
- navigate between activities across modules with scheme and host routing
- run a single business component standalone for debugging
- integrate multiple components into a host app for combined debugging
- load and unload components dynamically at runtime
- initialize components in a defined order
- support kotlin modules in a componentized android project

## When to choose
- you are building a large android app with multiple teams or feature modules that need strict isolation
- you want components that can be developed and debugged independently then assembled into one app
- you need cross-module navigation and interface-based communication without direct dependencies

## When to avoid
- you are starting a small app where modularization overhead is not justified
- you need a framework with frequent updates and active maintenance
- you prefer Jetpack's recommended navigation and modularization approaches over a third-party gradle-plugin-based solution

## Facets
- artifact type: framework
- maturity: maintenance
- function: mobile-framework, routing, middleware
- domain: mobile-development, android-tools, developer-tools
- platform: jvm
- tags: android-componentization, modular-architecture, gradle-plugin, component-isolation, single-module-debugging, ui-navigation, android

## Member repositories
- mqzhangw/JIMU (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:44.436896+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:33:58.670932+00:00, confidence not recorded.
  - readme: https://github.com/mqzhangw/JIMU (fetched 2026-08-28T04:06:44.436896+00:00, sha 9ea48b7417bf)
- Data as of 2026-08-30T08:39:29.467469+00:00.