Who is a Native Bindings Author and why you should be one
summary
Proposes a new role, the native bindings author, who uses FFIgen and JNIgen to generate direct Dart bindings that call native code synchronously with zero serialization overhead, passing pointers instead of copying data and achieving near-native performance. Shows concrete transforms: rename identifiers, convert int flags to enums, make Java lists implement Dart List, and add compositional facades and native escape hatches so packages publish platform-specific, type-safe bindings on pub.dev that plugin authors can compose into unified APIs.
AI-written summary · about
chapters (12)
- 0:00Native bindings authors
- 2:13Role of plugin authors
- 4:19Native bindings as a role
- 6:09Method channels limitations
- 12:39Pigeon improves method channels
- 15:07Native bindings with Dart FFI and JNI
- 19:01Shaping native APIs in Dart
- 24:01Declarative generated bindings
- 26:11Compositional Dart-friendly APIs
- 31:15Reshaping Flutter’s bindings ecosystem
- 34:09Native escape hatches
- 38:45Summary and call to action
related talks
31mSeamless Interoperability: Harnessing JNIGen and FFIGen
39mAdopting native assets for cross-platform FFI plugins
30mBinding Native Plugins with Flutter and Dart
43mSummit Session 2 - Past, Present and Future of Native Interop
50mPast, Present and Future of Native Interop
38mThe past, present, and future of native interop
14mC interoperability with Dart FFI
37mUsing Dart FFI for Compute-Heavy Tasks in Flutter Apps