Flutter lessons for federated plugin development
summary
Lessons from building Stadia’s federated plugins include concrete patterns: use proto buffs to serialize every method-channel message and cogen Dart/Java stubs so unit tests can exercise both sides; replace copied literals with a single text proto that generates cross-language constants; separate platform branching into capabilities and policies (capabilities = runtime/compile checks, policies = RPC/Remote Config) so UI logic stays thin and testable; prefer Dart business logic with thin native implementations; expect to roll out features per-platform and handle missing functionality without crashing.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:53What a Federated Plugin Is
- 1:11Platform Interface
- 2:51Protobufs
- 8:24Solution Capabilities and Policies
- 11:19Preferred Input Type
- 12:03Dependency Injection
- 13:45Bite Size Tips
- 14:17Recap What We Covered Today
related talks
26mPower of federated plugins in Flutter's ecosystem
55mOne Plugin, Six Platforms!
45mBuilding Products Full-Stack with Dart and Flutter
42mAddressing package ecosystem fragmentation
36mFlutter Plugins - From Method Channels to Native Interop
44mBuilding Pieces for Developers Our Journey with Flutter and Dart
32mCloud, Dart, and full-stack Flutter
09mFlutter for Enterprise: How your company should be building with Flutter at scale