Overview
The core add-to-app concepts and the architectural decisions you need to get right early.
The architecture tier is written for senior and staff engineers, architects, and tech leads. It covers the concepts you need to understand before designing an add-to-app project, the native-Flutter boundary, and how to structure the project so it scales.
Core concepts
Flutter engines, Dart isolates, and platform channels - the three things you need to understand to avoid the most common add-to-app surprises.
Native-Flutter communication
Patterns for moving data and events across the boundary.
Plugins in a multi-engine setup
Per-engine plugin registration, the iOS/Android asymmetry, and which plugin categories survive engines being created and destroyed per screen.
Embedding
Flutter views inside native screens and native views inside Flutter - what each costs, and the alternatives to reach for first.
Project structure
Monorepo, polyrepo, or git submodules - where the Flutter module, the native hosts, and shared code live.
Build integration
Source-level vs prebuilt artifacts (AAR / XCFramework), and the CI/CD pipeline each implies.
Versioning
Keeping the module, the native hosts, and the framework in step as they release.
Scaling & code sharing
Modularizing the Dart side into packages and sharing them with standalone Flutter apps.