How to Fight Android Engineering Decay: Strategies for Code, Resources, and Modules

Overview

Engineering quality is the foundation for fast, stable product iteration, but large projects inevitably suffer from "engineering decay"—the gradual accumulation of useless, redundant, or ill‑designed code and assets that degrade performance, stability, and maintainability.

Root Causes

Decay originates from time‑driven changes (OS upgrades, toolchain updates) and human‑driven rapid iteration. As teams grow and roles multiply—product, design, development, testing, PMO, operations, security—code changes become harder to control, leading to hidden technical debt.

Decay Types

Android projects can be decomposed into five element categories that each may decay:

Build configuration (e.g., excessive ProGuard rules)

Manifest files

Java/Kotlin code

Resources (images, strings, etc.)

Native libraries (SO files)

Governance Approach

The solution balances people (code reviews, standards, lint rules, training) with process (automated APK analysis, gate checks at build, integration, and release stages). Process‑driven gates enforce detection of decay items and block builds when violations occur.

Detection Capabilities

Key analysis tools include:

External dependency list : outputs all external JAR/AAR modules with versions.

com.youku.arch:testlib:0.1-SNAPSHOT@aar
com.youku.arch:testlib2:0.3@aar

Dependency‑by‑usage detection : shows which modules depend on a given module.

com.youku.android:y-core
|-- [provided] com.youku.android:ct-ad
|-- [compile] com.youku.android:catl
|-- [runtime] com.youku.android:MtRec

Version mismatch detection : highlights differences between compile‑time and APK‑time versions.

com.youku.android:YTask
|-- com.youku.android:BFra:1.0.0-SNAPSHOT => 1.0.0.44
|-- com.youku.android:BUIKit:20190617-SNAPSHOT => 1.0.1.66
|-- com.youku.android:YUI:1.4.2.16-SNAPSHOT => 1.4.10

Snapshot dependency detection : flags SNAPSHOT versions that may change unexpectedly.

com.youku.android:YHPage:1.9.35.5
|-- com.ali.android:VCommon:20210309-SNAPSHOT => 11.1.6.4
|-- com.youku.android:YRes:20210309-SNAPSHOT => 1.0.44.2

Process Gates

During critical stages (integration, gray‑release, production), the analysis runs automatically. If any gate fails, the build is aborted and detailed error information is presented, ensuring decay items are fixed before proceeding.

Module Governance

Modules are classified into app‑project, sub‑project, local JAR, flat AAR, and external modules. Understanding module boundaries enables precise impact analysis, such as why an updated module version does not reflect in the APK or why removed modules persist.

Practical Outcomes

Applying these practices at Youku reduced snapshot‑related incidents by over 40% and intercepted dozens of risky builds, demonstrating the effectiveness of a combined people‑process‑tool strategy for long‑term engineering health.

Further Reading

For deeper dives into specific decay categories—ProGuard configuration, manifest issues, Java code, resources, and native libraries—see the linked series articles.