An大多数朋友开始接触这个问题是因为 App 爆棚了，方法数超过了一个 Dex 最大方法数 65535 的上限，因而便有了插件化的概念，将一个 App 划分为多个插件（Apk 或相关格式）
常用的其他解决方法还包括：Google Multidex，用 H5 代替部分逻辑，删无用代码，买付费版的 Proguard
当插件化作用不止于此，还包括：(1) 模块解耦，(2) 动态升级，(3) 高效并行开发(编译速度更快) (4) 按需加载，内存占用更低 (5) 节省升级流量
droid 插件化 动态升级
http://www.trinea.cn/android/android-plugin/
An most of my friends began to approach the problem is because app bursting, the number of methods more than a DEX maximum number upper limit of 65535, and had the concept of plug-in, a division of the app for multiple plug-ins (APK or format)
Other commonly used methods include: Multidex Google, with H5 instead of partial logic, delete useless code, buy a paid version of the Proguard
When the plug-in effect more than that, it also includes: (1) modular decoupling, (2) dynamic update, (3), parallel development (compile faster) (4) on-demand loading, memory footprint lower (5) saving upgrades flow
Droid plug-in dynamic upgrade
Http://www.trinea.cn/android/android-plugin/
(2015-07-20, Others, 4944KB, 下载13次)