alibaba/flutter_boost
Flutter Boost
Flutter Boost is a hybrid integration framework that embeds Flutter screens inside existing native iOS, Android, and OHOS applications. It provides a cross-platform page router that navigates between native and Flutter pages using a unified page-name scheme, along with lifecycle-aware engine binding that ties the Flutter engine to native platform lifecycle events for proper start, pause, and resume behavior. The framework also includes multi-engine instance management, allowing separate Flutter engine instances per tab to maintain independent page state.
The framework distinguishes itself through container-based hybrid architecture that embeds Flutter views inside native view containers, managing lifecycle and rendering through a shared platform channel bridge. It offers delegate-based navigation routing that intercepts page transitions via a configurable delegate mapping route names to native or Flutter screens dynamically. A result-back channel enables passing data between native and Flutter pages without closing the source page, while transparent overlay page support allows pushing non-opaque Flutter pages as overlays for dialogs and popups that blend with underlying native UI.
The framework supports bidirectional event passing between platforms with automatic listener cleanup, and provides page lifecycle monitoring at both global and individual levels tracking foreground, background, push, pop, hide, and show state transitions. Documentation covers initialization on Android, iOS, and OHOS platforms, along with community contribution workflows for code changes, bug reporting, and feature proposals.
Features
- Hybrid Flutter Integrations - Embeds Flutter screens inside existing native iOS, Android, and OHOS applications with minimal code changes.
- Hybrid Page Routers - Provides the core cross-platform page router that navigates between native and Flutter pages.
- Native-Flutter Page Routers - Provides a cross-platform page router that navigates between native and Flutter pages using a unified page-name scheme.
- Hybrid Integration Frameworks - Embeds Flutter screens inside existing native iOS, Android, and OHOS applications.
- Hybrid Navigations - Ships a unified API to open pages from either native or Flutter code.
- Lifecycle Bindings - Binds the Flutter engine to native platform lifecycle events for proper start, pause, and resume.
- Native App Integrations - Provides the core mechanism for embedding Flutter screens inside existing native apps.
- Flutter Plugin Integrations - Adds Flutter as a dependency to existing native projects and manages lifecycle events across platforms.
- Engine Lifecycle Bindings - Binds the Flutter engine to native platform lifecycle events for proper start, pause, and resume behavior.
- Container-Based Hybrid Architectures - Provides the core container-based architecture for embedding Flutter views inside native view containers.
- Navigation Delegates - Implements a delegate-based navigation router that dynamically maps route names to native or Flutter screens.
- Data Channels - Passes data and results between native and Flutter pages without closing the source page.
- Multi-Instance Flutter Views - Runs separate Flutter instances in native tabs so each tab maintains its own independent page state.
- Multi-Instance Managers - Runs separate Flutter engine instances per tab so each tab maintains independent page state.
- Native-to-Flutter Data Channels - Sends results from a native page back to a waiting Flutter page without closing the native screen.
- Result Channels - Sends a result from a native page to a waiting Flutter page without closing the native page.
- Result Channels - Sends result data from a closing page to the previous page across native and Flutter boundaries.
- Result-Back Channels - Provides a result-back channel for passing data between native and Flutter pages without closing the source page.
- Cross-Platform - Listens for named events from the other platform and cleans up listeners automatically.
- Multi-Engine Instance Managers - Manages separate Flutter engine instances per tab to maintain independent page state and prevent cross-contamination.
- Cross-Platform Event Buses - Ships a cross-platform event bus for bidirectional communication between native and Flutter without manual bridge code.
- Transparent Overlays - Pushes non-opaque Flutter pages as transparent overlays for dialogs and popups.
- Transparent Overlay Pages - Supports pushing non-opaque Flutter pages as transparent overlays for dialogs and popups on top of native content.
- Cross-Platform Event Senders - Sends custom events with a key and data between platforms without writing manual bridge code.
- Page Result Channels - Pops the current page and optionally passes a result value back to the previous page.
Star history
How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.
