How Xianyu’s FlutterBoost Enables Seamless Hybrid Mobile Apps

Background

Large‑scale apps often rely on mature native libraries; rewriting them entirely in Flutter is costly, so a progressive hybrid migration is preferred. Xianyu’s team built a distinctive hybrid solution.

Current Mixed Scheme

The existing approach shares a single Flutter view as a canvas inside a native container. Only one logical page is visible at a time; page switches require popping the top of the stack, which loses state and can mistakenly close dialogs.

FlutterBoost – Next‑Generation Hybrid Architecture

FlutterBoost introduces a reusable, non‑intrusive hybrid framework that supports complex patterns such as tabbed home pages, provides a unified page lifecycle, and defines clear design concepts.

Key Concepts

Native layer : Container (native controller), Container Manager, Adaptor (Flutter as adaptation layer), Messaging (channel‑based communication).

Dart layer : Container (Navigator subclass), Container Manager (show/remove APIs), Coordinator (receives messages and controls containers), Messaging.

Page Model

Pages are defined by a native container and its associated Flutter widget. All routing operations target the native container; the Flutter widget follows its state.

Differences from the Old Scheme

The old scheme used a single Navigator stack in Dart. FlutterBoost replaces the stack with a flat key‑value map of containers, each identified by a unique ID, eliminating stack‑top limitations and intrusive engine modifications.

Multi‑Navigator Implementation

Only one Flutter Navigator is visible at a time, each linked one‑to‑one with a native container. Lifecycle events are synchronized, and a manager handles container switching.

Page Creation Flow

Create a native container (iOS ViewController, Android Activity/Fragment).

Native container notifies Flutter Coordinator via messaging.

Flutter Container Manager creates the corresponding Flutter container and loads the widget.

When the native container appears, it sends the page ID to the Coordinator.

Flutter Container Manager brings the matching Flutter container to the foreground.

Engine and Framework Details

Flutter consists of a C++ engine and a Dart framework. A process can host multiple engine instances sharing a single Dart VM. Each FlutterViewController (iOS) or Activity (Android) creates its own engine and isolate.

Official Recommendations

Long‑term advice is to share a single engine across windows, but current support is limited. Multi‑engine mode is simple but incurs resource duplication, plugin registration complexity, and increased communication overhead, so FlutterBoost avoids it.

Performance Optimizations

When switching between two Flutter pages, a screenshot cache stores only 2‑3 recent images in memory, writing others to disk to balance memory usage and user experience. Flutter’s AOT compilation provides fast page rendering.

Adoption and Integration

FlutterBoost powers all Flutter‑based features in the Xianyu client, serving billions of users. It is distributed as a reusable plugin; projects that already integrate Flutter can add it with minimal code changes. The solution has been tested through Release 1.0 without issues.