alibaba/flutter_boost

FlutterBoost is a hybrid navigation and container management library for Flutter that enables seamless integration between native mobile applications and Flutter views. It provides a unified API for routing, lifecycle management, and platform communication across Android, iOS, and HarmonyOS. The system has been refactored to use Pigeon for message channel generation and modernizes the architecture by removing legacy singleton and container classes in favor of a more modular, options-based approach.

27 changes.

This period focused on modernizing the FlutterBoost library by removing legacy Android and iOS implementation layers, including old navigation services, container managers, and singleton patterns. The refactoring introduced cleaner public APIs, updated build configurations for AndroidX and modern Dart SDKs, and replaced manual message channels with Pigeon-generated channels for improved cohesion.

12 changes.

This period focused on standardizing the communication layer between native and Flutter code using the Pigeon tool, which generated consistent message channel interfaces across platforms. The team refactored the iOS and Android native layers to support hybrid navigation and improved container management, while simultaneously expanding the example application with comprehensive demos and tests for image handling, animations, and navigation scenarios.

6 changes.

This period focused on the initial implementation of HarmonyOS (Ohos) support, introducing the necessary build configurations, ETS components, and example project scaffolding. The work established the core infrastructure for integrating Flutter with native ArkUI pages and managing routing between native and Flutter contexts.

The HarmonyOS example application has been added, providing a complete reference implementation for integrating Flutter with native ArkUI pages. This includes the entry point (EntryAbility) that initializes the Flutter engine and registers plugins, a custom router (RouterModule) to manage navigation between native and Flutter pages, and specific UI components (FlutterUIPage, FlutterUIDialog, FlutterUIComponent) that host Flutter content within the native navigation stack. The example also includes a simple PlatformView implementation and test suites to verify the routing and parameter passing between native and Flutter contexts.

example/ohos/entry · high confidence

Added multiple new example pages in the \example/lib/case\ directory to demonstrate various Flutter and Boost capabilities. These include an animation demo using \AnimationController\, image handling demos for precaching, APNG/GIF comparison, and support for diverse image formats (HDR, HEIC, HEIF, TIFF, WBMP, WEBP, etc.). The update also introduces demos for clipboard access, bottom navigation with webviews, Cupertino page routes, Hero animations, image caching, dual-screen hinge angle sensors, extended image gestures, Flutter-to-Flutter navigation, and native view integration. These examples serve as test cases and usage references for developers.

example/lib/case · high confidence

A new example widget, SimpleWidget, has been added to the tab demo area. It demonstrates the use of the PageVisibilityObserver mixin to receive onPageShow and onPageHide lifecycle events, providing a concrete reference for developers implementing page visibility tracking in their applications.

example/lib/tab · high confidence

Added essential project files including a Travis CI configuration (.travis.yml) for automated testing, an AUTHORS file listing contributors, and documentation files (Frequently Asked Question.md, INTEGRATION.md, CHANGELOG.md, README.md, README\_CN.md) that provide integration guides, release notes, and FAQs for the FlutterBoost library.

(repo-wide) · high confidence

The example/ohos directory now contains the complete scaffolding for a HarmonyOS application, including build configuration (build-profile.json5), package management (oh-package.json5 with @ohos/hypium and flutter\_ohos overrides), and essential metadata files (app.json5, string resources). This provides a functional starting point for the Flutter Boost example on the Ohos platform.

example/ohos · high confidence

The Android example application now includes several new Java classes to demonstrate native integration patterns. A \FlutterBoostView\ implementation is added to the example, allowing developers to see how to manage Flutter views within a native container. The example also introduces a tabbed navigation structure (\TabMainActivity\, \TabCustomViewActivity\) that switches between native fragments and Flutter pages. Additionally, new classes demonstrate custom native views integrated with Flutter's platform view system, including a \SimpleTextView\, a \GlSurface\ (OpenGL renderer), and a \RunBall\ animation view, all registered as platform views. A \NativeRouter\ class is also added to handle URL-based navigation within the example.

example/android · high confidence

The project now uses the Pigeon code-generation tool to automatically generate the Dart, Java, and Objective-C interfaces for the native-Dart message channel. This replaces manually written channel code with generated classes like \NativeRouterApi\ and \FlutterRouterApi\, which define the communication contract for routing and events between the Flutter and native layers.

pigeon · high confidence

The example app now includes a new \FlutterIndexRoute\ page that demonstrates page visibility lifecycle callbacks (show, hide, foreground, background) via the \PageVisibilityObserver\ mixin. The main entry point (\main.dart\) has been updated to register this route and several others (image picker, hero animation, safe area, etc.) in the router map, and includes global page visibility observers and custom interceptors to demonstrate route interception and argument modification. Additionally, \simple\_page\_widgets.dart\ was refactored to use \StatefulWidget\ for better lifecycle management and includes new demo buttons for Flutter-to-Flutter and native page navigation.

example/lib · high confidence

This change introduces the initial implementation for the HarmonyOS (ohos) platform, adding the necessary build configuration, package manifest, and entry point files to support Flutter-Boost on this new target. This enables developers to integrate Flutter with native HarmonyOS applications using the standard Boost API.

ohos · high confidence

Added new Android classes to manage Flutter containers: \FlutterActivityLaunchConfigs\ for passing launch parameters, \FlutterBoostActivity\ and \FlutterBoostFragment\ for managing the lifecycle and rendering of Flutter views, \FlutterViewContainer\ as a common interface for container operations, \LifecycleStage\ to track activity/fragment states, and \FlutterTextureHooker\ to handle texture view lifecycle on older Android versions.

android/src/main/java/com/idlefish/flutterboost/containers · high confidence

Added new ETS files including FlutterBoost, FlutterBoostRouteOptions, FlutterBoostSetupOptions, FlutterBoostUtils, and various container and message handling classes (such as FlutterBoostAbility, FlutterBoostEntry, and message codecs) to support the FlutterBoost framework on OpenHarmony. These changes provide the core infrastructure for managing Flutter containers, handling routing parameters, and facilitating communication between native and Flutter sides.

ohos/src · high confidence

The iOS portion of the \example\_new\_for\_ios\ sample has been updated to integrate the \flutter\_boost\ plugin, enabling hybrid navigation between native iOS views and Flutter pages. The \AppDelegate\ and \BoostDelegate\ classes manage the routing and state, while \HomeViewController\ demonstrates pushing Flutter views and handling return data, providing a working example of Flutter-Boost integration on iOS.

_example\_new\_for\ios · high confidence

The iOS example app has been refactored to demonstrate embedding Flutter views within native view controllers, introducing FLNativeView and NativeViewController to show how Flutter can be embedded in a native hierarchy. Routing is modernized via the FlutterBoostRouteOptions API, replacing the previous DemoRouter singleton with a more flexible, options-based approach for opening and closing pages. The app now supports passing Dart entrypoint arguments, registers native view factories for platform views, and updates the UI to include buttons for pushing embedded views. Additionally, the Info.plist is updated with required camera, microphone, and photo library usage descriptions, and the GeneratedPluginRegistrant is updated to handle newer plugin import styles.

example/ios/Runner · high confidence

The iOS example project was updated to support embedding a FlutterViewController as a subview. This includes adding new source files (FLNativeView, NativeViewController, MyFlutterBoostDelegate) and their corresponding build file references, linking the libPods-Runner.a static library, and configuring the Xcode project to include these files in the build. Additionally, the project structure was adjusted to remove obsolete framework embeddings and router components, and the Xcode scheme was cleaned up by moving test configurations to the correct section.

example/ios/Runner.xcodeproj · medium confidence

The \BoostPageRoute\ class and the \Router\ utility class have been removed from the \lib/router\ directory. This eliminates the previous custom page routing and navigation abstraction, meaning applications can no longer use \BoostPageRoute\ for transitions or the \Router.openPage\/\closePage\ methods for navigation.

lib/router · high confidence

The \BoostContainer\, \ContainerCoordinator\, and \ContainerManager\ classes in \lib/container\ have been removed. This eliminates the previous container lifecycle and overlay-based management system, requiring users to adopt the newer container architecture.

lib/container · high confidence

The Android \NavigationService\ and its associated handler classes (including \NavigationServiceRegister\, \NavigationService\_closePage\, \NavigationService\_onFlutterPageResult\, \NavigationService\_onShownContainerChanged\, \NavigationService\_openPage\, and \NavigationService\_pageOnStart\) have been deleted from the codebase. This removes the native Android-side implementation for managing page navigation and container state changes, likely as part of a migration to a different navigation architecture.

android/src/main/java/com/taobao/idlefish/flutterboost/NavigationService · high confidence

The Android source files for the FlutterBoost library have been deleted, including the core implementation classes such as \FlutterBoostPlugin\, \FlutterViewProvider\, \ContainerRecord\, and related interfaces and utilities. This removal eliminates the native Android layer responsible for managing Flutter view containers, handling page lifecycle states (create, appear, disappear, destroy), and coordinating with the Flutter engine on the Android platform.

android/src/main/java/com/taobao/idlefish/flutterboost · high confidence

The \BoostFlutterActivity\, \BoostFlutterFragment\, and \FlutterViewStub\ classes in the \com.taobao.idlefish.flutterboost.containers\ package have been removed. This eliminates the previous implementation of Flutter view containers, likely as part of a migration to a new container architecture.

android/src/main/java/com/taobao/idlefish/flutterboost/containers · high confidence

A change to existing behaviour in example/ohos/dta — 1 commit, 1 file.

example/ohos/dta · low confidence · unverified

A new hvigor-config.json5 file has been added to the example/ohos/hvigor directory, establishing the build tooling configuration with model version 5.0.0 and an empty dependencies list, supporting the adaptation to API 12 and DevEco Studio 5.0.3.300.

example/ohos/hvigor · medium confidence

A new workspace settings file (WorkspaceSettings.xcsettings) was added to the iOS example project, configuring the build location style to 'UseTargetSettings'. This change affects how Xcode manages build artifacts for the iOS application, ensuring consistent build output locations across the workspace.

example/ios/Runner.xcodeproj/project.xcworkspace · high confidence

The example iOS project now includes a default breakpoint list file (Breakpoints\_v2.xcbkptlist) within the user-specific workspace data. This file configures the Xcode debugger's breakpoint state, ensuring that the example app's debugging configuration is consistent across different developer environments.

example/ios/Runner.xcworkspace/xcuserdata/zhongchengguo.xcuserdatad · medium confidence

The Android side now manages Flutter view containers through a new \FlutterContainerManager\ singleton, which tracks active and all containers to support features like finding the top activity container. Additionally, an example app now includes a \RunBallView\ test utility that implements \PlatformView\ to facilitate automated testing scenarios.

. · medium confidence

The Android implementation of FlutterBoost has been refactored to improve code cohesion and align with the Flutter 3.x embedding API. A new \FlutterBoost\ singleton class now manages the Flutter engine lifecycle, including initialization, teardown, and back/foreground event dispatching. The \FlutterBoostPlugin\ has been updated to use Pigeon-generated message channels (\Messages.java\) for communication with Dart, replacing the previous manual channel setup. Additionally, a new \FlutterBoostDelegate\ interface and \FlutterBoostRouteOptions\ class provide a cleaner way for native code to handle route navigation and pass arguments, while utility classes like \Assert\ and \EventListener\ support the new structure.

android/src/main/java/com/idlefish/flutterboost · high confidence

The library's internal implementation has been reorganized into the \lib/src\ directory, with specific components such as \BoostCacheWidget\, \BoostChannel\, \BoostContainer\, \BoostNavigator\, and \FlutterBoostApp\ moved from the public API to the internal source tree. This change hides the concrete implementation details and exposes the public interface through \flutter\_boost.dart\, providing a cleaner separation between the library's internal logic and its public API.

lib/src · high confidence

The iOS example app now includes a new \WorkspaceSettings.xcsettings\ file that configures Xcode's build location to use app preferences, sets the custom build location relative to derived data, and enables live source issues and automatic scheme display. These are local user/workspace preferences that affect how the Xcode project is built and organized on a developer's machine.

example/ios/Runner.xcworkspace/xcuserdata/wubian.xcuserdatad · high confidence

The iOS-side implementation for the NavigationService has been removed. This eliminates the native bridge methods that previously handled page lifecycle events (such as didShowPageContainer, willShowPageContainer, didDisappearPageContainer, willDisappearPageContainer, didInitPageContainer, and willDeallocPageContainer) for Flutter-to-iOS communication, meaning these specific navigation callbacks are no longer available on the iOS platform.

ios/Classes/Messaging/Generated/NavigationService/service · high confidence

The \lib/AIOService/NavigationService\ directory has been removed, eliminating the legacy \NavigationService\ implementation and its associated handlers (e.g., \didShowPageContainer\, \willShowPageContainer\). This change removes the direct integration with \flutter\_boost\ and \xservice\_kit\ for page lifecycle management, likely as part of a broader reorganization or migration to a new navigation architecture.

lib/AIOService · high confidence

The \message\_proxy.dart\, \native\_page\_container\_event\_handler.dart\, and \page\_result\_mediator.dart\ files have been removed from the \lib/messaging\ directory. This eliminates the \MessageProxy\ abstraction for page navigation, the \NativePageContainerEventHandler\ interface for native container lifecycle events, and the \PageResultMediator\ for handling page results, indicating a simplification of the messaging and page management architecture.

lib/messaging · high confidence

The Main.storyboard file has been simplified by removing the default Flutter view controller scene and its associated layout guides and background color settings. This change updates the Xcode/Interface Builder tooling version and removes the initial view controller configuration, likely to allow the application to manage the root view controller programmatically or via a different mechanism.

example/ios/Runner/Base.lproj · high confidence

The iOS implementation of FlutterBoost has been refactored by removing the \FLBFlutterApplication\ singleton and several legacy classes including \FLBFlutterAppDelegate\, \FLBPlatform\, \FLBResultMediator\, \FlutterBoostConfig\, and \FlutterBoostPlugin\. This change eliminates the previous global state management and singleton pattern, likely to support co-existing with newer versions of FlutterBoost or to modernize the architecture.

ios/Classes/Boost · high confidence

The iOS implementation for the NavigationService has been removed. Specifically, the generated Objective-C handler files for closePage, onFlutterPageResult, onShownContainerChanged, openPage, and pageOnStart have been deleted from the codebase. This eliminates the native iOS bridge for these navigation operations, meaning these specific navigation events and actions will no longer be handled by the iOS native layer.

ios/Classes/Messaging/Generated/NavigationService/handlers · high confidence

The iOS adaptor layer for Flutter has been refactored by removing the legacy \FLBFlutterEngine\, \FLBFlutterEngineOld\, and \FLBFlutterViewControllerAdaptor\ classes, along with the \FLBFlutterViewProvider\ protocol and \FLBViewProviderFactory\. This removes the older implementation of the Flutter engine and view controller adaptor, likely as part of a migration to a newer Flutter integration approach.

ios/Classes/Adaptor · high confidence

The \lib/flutter\_boost.dart\ entry point has been refactored to expose a cleaner, modular public API by exporting specific internal modules (e.g., \boost\_channel\, \boost\_navigator\, \page\_visibility\) from the \src\ directory. Concurrently, internal implementation details such as \ObserversHolder\ and \Tracer\ have been removed from the public interface, reducing the exposed surface area and decoupling the library's core navigation and lifecycle management from its internal state holders.

lib · high confidence

The \doc/api\ directory has been updated with new and revised Dartdoc HTML files for the \boost\_channel\ and \boost\_container\ libraries. This includes generated documentation for the \BoostChannel\ class (covering \addEventListener\, \sendEventToNative\, and the \instance\ property), the \EventListener\ typedef, and the \BoostContainer\ class (including its constructor and \addPage\ method). These changes reflect the current state of the core API, ensuring the public documentation accurately describes the available methods and types for developers.

doc · high confidence

The Android build system now uses Gradle 4.10.1 instead of the previous 4.6 version. This change updates the underlying build tooling to a newer release, which may affect build performance and compatibility with other Android/Gradle plugins.

android/gradle · high confidence

The example iOS project updated its plugin symlinks to point to specific versions of the image\_picker (0.6.7+17) and video\_player (0.10.12+5) packages, while removing symlinks for the flutter\_boost and xservice\_kit plugins.

example/ios/.symlinks · medium confidence

The iOS workspace settings have been updated to include the 'IDEWorkspaceSharedSettings\_AutocreateContextsIfNeeded' flag, which enables automatic context creation within the Xcode workspace. This change modifies the workspace configuration to streamline the development environment setup.

example/ios/Runner.xcworkspace/xcshareddata · high confidence

The iOS implementation of the Flutter container system has been restructured to improve stability and consistency. The previous \FLBFlutterViewContainer\ and \FLBFlutterViewContainerManager\ classes have been replaced with a new \FBFlutterContainer\ protocol and \FBFlutterContainerManager\ to manage container states. This change introduces a more robust lifecycle management via \FBLifecycle\, ensuring that the app's resume and pause states are correctly synchronized with the Flutter engine. Additionally, the removal of the \FLBStackCache\ and \FLBMemoryInspector\ indicates a shift away from aggressive memory caching and memory-pressure-based optimizations, likely to prevent crashes and memory leaks associated with the previous caching strategy.

ios/Classes/Container · medium confidence

The iOS native implementation has been refactored to use Pigeon for generating the message channel, replacing the previous manual implementation. This introduces new \FlutterBoostSetupOptions\ and \FlutterBoostRouteOptions\ classes to configure the Flutter engine (including warm-up and entrypoint settings) and route parameters. The \FlutterBoostPlugin\ and \FlutterBoostDelegate\ interfaces have been updated to align with this new structure, ensuring consistent behavior with the Android side.

ios/Classes · high confidence

Add HDR/HEIC/HEIF/TIFF/WBMP/WEBP image format tests; Added tests for FlutterBoost navigation methods; Updated example/widget\_test.dart to use Flutter Boost example package and null-safe syntax.

The FlutterBoost package is updated to version 4.6.5, raising the minimum supported Dart SDK to 2.12.0 and adding a dependency on the \collection\ package. The Android build configuration has been modernized to use AndroidX, updating the Android Gradle Plugin to 7.4.0, setting the compile SDK to 31/33, and migrating from \android.support\ libraries to \androidx\ equivalents. The iOS configuration has been updated to use the standard \flutter\_install\_all\_ios\_pods\ helper, and the \xservice\_kit\ dependency has been removed in favor of direct dependencies like \image\_picker\ and \video\_player\ in the example app.

(dependencies) · medium confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 55 → 61 (+6.1)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 99 → 92 (-6.9)
• Architecture 95 → 95 (+0.8)
• Maturity 37 → 49 (+12.2)
• Readiness 46 → 58 (+12.3)
• Security 90 → 73 (-17.0)
• Domain Modelling 100 → 100 (+0.0)

• Change coupling: boost_channel.dart ↔ boost_flutter_router_api.dart (lib/src/boost_channel.dart)
• Change coupling: boost_channel.dart ↔ boost_navigator.dart (lib/src/boost_channel.dart)
• Change coupling: boost_flutter_router_api.dart ↔ boost_interceptor.dart (lib/src/boost_flutter_router_api.dart)
• Change coupling: boost_flutter_router_api.dart ↔ boost_navigator.dart (lib/src/boost_flutter_router_api.dart)
• Change coupling: boost_flutter_router_api.dart ↔ container_overlay.dart (lib/src/boost_flutter_router_api.dart)
• Change coupling: flutter_boost_app.dart ↔ page_visibility.dart (lib/src/flutter_boost_app.dart)
• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• No exposed public API
• Test reliability not included
• complexity unreadable for .dart, .java, .swift — churn × complexity hotspots could not be measured
• dormant codebase — no living knowledge left to concentrate

• ClassTooLong: FlutterBoostAppState (lib/src/flutter_boost_app.dart)
• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no contributor guidance (README.md)
• Documentation: no installation or build instructions (README.md)
• Documentation: no licence statement (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (10 lines × 3) (example/lib/case/native_view_demo.dart)
• Duplicated block (10–11 lines × 2) (example/lib/flutter_page.dart)
• Duplicated block (10–11 lines × 3) (example/lib/case/media_query.dart)
• Duplicated block (10–11 lines × 3) (example/lib/case/native_view_demo.dart)
• Duplicated block (10–11 lines × 9) (example/lib/case/platform_view_perf.dart)
• Duplicated block (13 lines × 3) (example/lib/case/flutter_to_flutter_sample.dart)
• Duplicated block (13 lines × 4) (example/lib/flutter_page.dart)
• Duplicated block (14 lines × 2) (example/lib/case/image_pick.dart)
• Duplicated block (14–15 lines × 3) (example/lib/case/flutter_rebuild_demo.dart)
• Duplicated block (15 lines × 2) (example/lib/case/flutter_to_flutter_sample.dart)
• Duplicated block (15–18 lines × 2) (example/lib/case/transparent_widget.dart)
• Duplicated block (16 lines × 3) (example/lib/case/apng_vs_gif_route.dart)
• Duplicated block (19 lines × 2) (example/lib/case/native_view_demo.dart)
• Duplicated block (19 lines × 3) (example/lib/flutter_page.dart)
• …and 47 more

• Containers 0 added · 0 removed · contexts 2 added · 1 removed · edges 1 added · 0 removed

• app
• flutter_boost

• .

• app → flutter_boost

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

alibaba/flutter_boost was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.