Plugin Framework Overview and Performance Optimizations for Android Applications

The document begins with an overview of a plugin framework’s four development stages—exploration, development, quality, and experience—detailing its API, framework, and base layers, and highlights the performance issues encountered during the experience phase.

It then investigates Multidex problems, explaining how heavy Multidex operations on the main thread cause UI jank and ANR, and proposes moving Multidex execution to a background thread and separating versioned artifacts to avoid redundant processing.

Next, the article delves into Dex2Oat and DexOpt challenges on Android 9 and above, describing system restrictions that prevent in‑process compilation, and introduces forced compilation via ADB commands such as adb shell cmd package compile -m speed -f my-package to generate OAT files without impacting the main thread.

For Android 5‑7, a lightweight solution is suggested: providing invalid compilation paths to trigger the VM’s fallback mechanism, thereby skipping Dex2Oat while still loading the original dex files. For Android 8‑9, the use of InMemoryClassLoader is discussed to load dex directly from memory, bypassing compilation entirely.

The final section addresses class‑loader optimization, explaining how the introduction of a custom PluginClassLoader disrupts the native class‑loading chain, leading to extra JNI calls. It proposes replacing the native method ClassLinker#FindClassInBaseDexClassLoader via BL hooking to restore efficient class lookup and reduce overhead.

Overall, the article emphasizes iterative analysis of Android internals, strategic use of system commands, and careful native hooking to achieve significant performance gains in plugin‑based Android applications.