Magpie SDK: Engineering Practices for Flutter Hybrid Development

Background – Flutter offers cross‑platform benefits, but real‑world projects require engineering scaffolding to fully exploit its performance, dynamism, and community support. In late 2019, the team began a Flutter engineering journey to improve development and release efficiency.

Current Situation Analysis & Optimization Practices – The native‑first workflow is a black‑box process that incurs high integration cost, environment inconsistency, unclear responsibilities, limited extensibility, and slow build times. By separating Dart and native parts and linking them via the Magpie workflow, the team reduces coupling, clarifies roles, and speeds up development.

Android Build Process Optimization – The SDK injects Flutter engine dependencies via apply from: "flutter_magpie.gradle" and configures remote Maven repositories. Build artifacts are split into debug and release types, with specific engine binaries and variable assets. Architecture compatibility is handled by moving *.so files to appropriate ABI directories.

iOS Build Process Optimization – The iOS side produces App.framework , snapshot data, plugin registrants, and Cocoapods specifications. Build commands such as flutter build aot --target-platform=ios and flutter build bundle generate the necessary binaries and assets for both debug and release modes. Plugin discovery is automated by parsing .flutter-plugins and generating registration code via Mustache templates.

Toolchain Support – A graphical workflow provides one‑click compilation, attach, and publishing functions, simplifying command‑line operations for developers.

Magpie Mixed Page Interaction Design – The SDK adopts FlutterBoost for engine caching, reducing memory and resource duplication when navigating between native and Flutter pages.

Magpie Communication Design – Communication between Dart and native layers is encapsulated in plugins, with generated registration code and Cocoapods integration to ensure seamless interaction.

Contribution & Feedback – Developers are encouraged to read the source at GitHub , submit PRs or Issues, and participate in community discussions.

Summary & Future Plans – The team will focus on reducing app package size, enabling dynamic business logic, and collaborating with the community for further improvements.

Authors – Huang Xin (Android Senior Engineer, 58.com) and Zhang Dali (R&D Engineer, 58.com).

References – Flutter Add‑to‑App documentation, FlutterBoost, and related open‑source projects.