# luckybilly/CC

业界首个支持渐进式组件化改造的Android组件化开源框架，支持跨进程调用。Componentize your android project gradually.

Repository: https://github.com/luckybilly/CC
Canonical: https://ross.abutalabs.com/products/cc
Homepage: https://luckybilly.github.io/CC-website/
Language: Java
License: Apache-2.0
License Family: permissive
Topics: cc, android-architecture, android-component, component, architecture-components, componentization
Last push: 2023-10-11T01:51:19+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 3205, "days_push": 1058, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4037, forks 631 (observed 2026-08-28T04:08:33.454558+00:00)

## What it is
CC (ComponentCaller) is an Android componentization framework built on a component-bus architecture that supports gradual, incremental refactoring of monolithic Android projects into decoupled components. It enables cross-process and cross-app component calls with a consistent API, and ships with the cc-register Gradle plugin for automatic component registration and standalone component debugging.

## Use cases
- componentize an android monolith gradually
- call components across processes in android
- run a single android module as a standalone app for debugging
- decouple android modules without rewriting existing code
- replace android routing frameworks with a component bus
- register android components automatically at build time

## When to choose
- you are componentizing a large legacy Android app and want incremental adoption without pre-existing decoupling
- you need cross-process or cross-app component invocation without AIDL or bindService boilerplate
- you want components to run and be debugged independently as separate apps

## When to avoid
- you only need simple in-app page navigation, where a lightweight router suffices
- your project is Kotlin-first and you prefer a modern, actively evolving framework
- you need a solution with frequent updates and broad community maintenance

## Facets
- artifact type: framework
- maturity: maintenance
- function: routing, middleware, plugin-system, developer-tools
- domain: mobile-development, android-tools, web-development
- platform: jvm
- tags: android, componentization, component-bus, cross-process-calls, gradle-plugin, modular-architecture, decoupling

## Member repositories
- luckybilly/CC (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:33.454558+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-29T18:23:47.444216+00:00, confidence not recorded.
  - readme: https://github.com/luckybilly/CC (fetched 2026-08-28T04:08:33.454558+00:00, sha a47f3dd7117e)
  - homepage: https://luckybilly.github.io/CC-website/ (fetched 2026-08-29T09:16:15.070310+00:00, sha 3817e0fb9b8a)
- Data as of 2026-08-30T08:39:29.467469+00:00.