From the analysis of Tmall, Meituan and Qunar, how should front-end developers control the dynamic development of mobile APP (I)?

Tangram focuses on three things: business orientation, multi-endpoint consistency, and high performance.



















Forced the



Forced the



Forced the



Forced the

























Forced the
Forced the
Forced the
Forced the
Forced the

Technical architecture:

WebView, Download, Share, and even Protobuf can be basic plug-ins.

RePlugin claims to be plug-in by hook of a single system call. Replugin uses RepluginClassLoader to replace the system’s PathClassLoader at application startup and modifysthe behavior of the loadClass method to load the plug-in’s classes.

Replugin also came up with the concept of a “pit”. A pit is a component (Activity, Service, Content Provider, but no Broadcast Receiver) that is registered in the Host Manifest. The code for these pit components is generated by the Gradle plugin at compile time and is not actually used. When a plug-in component is started, these pits are used to replace the component to be started, and a mapping between the pits and the real component (represented by ActivityState) is established. RepluginClassLoader then tricks the system by using the plug-in’s PluginDexClassLoader to load the real component class to be launched during class loading based on the tampered behavior mentioned earlier, which is the sole hook point mentioned above.

Bring about summary

RePlugin’s stability is improved by hooking only one system API, and the “pit” concept eliminates the need for plug-in frameworks to “bury” plug-in components in the host APP, allowing them to be installed and run independently of the host. Replugin is a revolution in Android plug-in technology.

Although pluggable can bring enough flexibility to APP, all functional modules can be theoretically independent installation package, realize the user’s on-demand download, but have to say that the security risks, load the external executable code, a question that starts is to ensure the safety of the external code, we don’t want to load some of unknown origin plugin APK, These plug-ins sometimes have access to the host’s critical data.

In this paper, we respectively introduce the dynamic component of Tmall -Tangram and the plug-in scheme of 360 -RePlugin to show the dynamic development of current mobile APP from its technical principle, technical architecture and their respective advantages. The following will continue to introduce the development status and future trends of mobile terminal technology from Qunar and Meituan in more depth. Stay tuned!