Past, Present and Future of Native Interop
summary
Unconference session drills into concrete pain points and prototypes: FFI gen and JNI gen exist as experimental code generators (including a Google Summer of Code Swift Gen), used already by Cronet and Certino HTTP backends, and a partial WebView rewrite reveals real issues. Native bundling via native assets aims to stop fragile Docker/QEMU cross-compiles that take 10–15 minutes, enable bundled libc-like dependencies, and avoid C rewrites. Multi-language debugging remains a pipe dream; codegen and improved docs are the immediate roadmap.
AI-written summary · about
chapters (17)
- 0:00Native interop introduction
- 1:54Current native interop tools
- 3:03Pain points with interop
- 5:53Native assets challenges
- 7:59Cross-compilation issues
- 12:12Pigeon for event channels
- 18:03Method channels vs FFI gen
- 21:57Synchronous native API calls
- 27:55Gradual interop roadmap
- 31:49Plugin workflow pain points
- 33:15Documentation and IDE improvements
- 37:12Debugging mixed-language code
- 38:15Multi-language debugging
- 40:39Debugging cross-language APIs
- 42:27Message passing vs direct access
- 44:58WebView complexity
- 48:58FFI gen feedback
related talks
43mSummit Session 2 - Past, Present and Future of Native Interop
36mFlutter Plugins - From Method Channels to Native Interop
31mSeamless Interoperability: Harnessing JNIGen and FFIGen
30mBinding Native Plugins with Flutter and Dart
39mAdopting native assets for cross-platform FFI plugins
40mWho is a Native Bindings Author and why you should be one
56mFuture of Dart Panel
21mBridging, Compiling, and Rendering: How Cross-Platform Frameworks Work