FlutterBoost 3.0: Architecture, Features, and Integration Guide

With the rapid adoption of Flutter in Chinese apps, many projects introduce Flutter pages gradually alongside native pages. Managing routing between native and Flutter pages is a common challenge, and FlutterBoost was created to address this gap.

The mission of FlutterBoost is to let developers add Flutter pages to native apps with minimal effort, although it still depends on SDK openness, prompting the team to push for more low‑level Flutter APIs.

Key problems identified include stability across new Flutter releases, a proliferating set of community issues, and an overly complex design that hinders newcomers.

FlutterBoost 3.0 introduces several major upgrades:

Non‑intrusive engine integration that works with any Flutter SDK version, eliminating the need for separate AndroidX and Support branches.

Architecture simplification—code size is roughly halved.

Unified dual‑end design: Android and iOS share the same interfaces and parameters, reducing learning and integration costs.

Ability to open a Flutter page without creating a container; the withContainer flag controls this behavior.

More precise lifecycle notifications that fire only when page visibility actually changes.

Resolution of legacy issues such as fragment integration difficulties, data passing on page close, status‑bar styling, willPopScope handling, off‑stack lifecycle callbacks, and setState performance.

The plugin consists of platform and Dart sides linked via a MessageChannel. The platform side manages engine configuration, native container lifecycle, and page open/close APIs, while the Dart side offers a Navigator‑like API and route management.

Non‑intrusive engine support is achieved by extending FlutterActivity/FlutterFragment via inheritance and sending an appIsResumed message to Dart, fixing lifecycle‑related page freezes and ensuring compatibility with Flutter 2.0.

Unified dual‑end design aligns Android and iOS APIs at the parameter level, easing cross‑platform development.

Example of opening a Flutter page with and without a container:

InkWell(
  child: Container(
    color: Colors.yellow,
    child: Text('打开外部路由', style: TextStyle(fontSize: 22.0, color: Colors.black)),
  ),
  onTap: () => BoostNavigator.of().push("flutterPage", arguments:
{'from': widget.uniqueId}),
);
InkWell(
  child: Container(
    color: Colors.yellow,
    child: Text('打开内部路由', style: TextStyle(fontSize: 22.0, color: Colors.black)),
  ),
  onTap: () => BoostNavigator.of().push("flutterPage", withContainer: true, arguments:
{'from': widget.uniqueId}),
);

Integration is as simple as adding the following dependency:

flutter_boost:
  git:
    url: 'https://github.com/alibaba/flutter_boost.git'
    ref: 'v3.0-beta.3'

FlutterBoost 3.0 is currently in beta public testing. Future work will continue to improve the single‑engine model, engage with the Flutter team about EngineGroup memory sharing, and explore new hybrid stack possibilities under Flutter 2.0.