This article provides a detailed source‑code analysis of RePlugin's process management, covering process startup, attachBaseContext handling, IPC initialization, PMF setup, plugin installation, synchronization across processes, and the internal mechanisms for loading and updating plugins.
This article dissects RePlugin's process management and plugin loading mechanisms from a source‑code perspective, detailing the startup sequence, framework configuration, IPC initialization, PMF setup, plugin installation flow, and how plugins are registered and synchronized across processes.
This article explains how RePlugin maps plugin-defined custom‑process activities to host placeholder processes, retrieves component information from the plugin APK, generates static or dynamic process‑mapping tables, adjusts component process names, and orchestrates the launch and lifecycle of these activities on Android.
This article explains how RePlugin enables a host app to recognize, map, and start custom plugin processes—including static and dynamic process mapping, adjusting component process names, launching processes via injected providers, handling process reclamation, and managing activity slot allocation for seamless plugin activity execution.
This article explains how the two essential Gradle plugins—replugin-host-gradle and replugin-plugin-gradle—generate configuration files, inject AndroidManifest components, create built‑in plugin descriptors, and use Transform API to modify bytecode, enabling seamless plugin development and integration in Android projects.
This guide explains what Fresco is, shows how to add its dependencies, use SimpleDraweeView in XML, and details a plugin‑friendly approach for sharing Fresco across host and RePlugin modules by converting the drawee AAR to a JAR and handling custom attribute callbacks.
