Summit Session 2 - Past, Present and Future of Native Interop
summary
A practical roundtable outlining the current native interop stack: Dart FFI, FFI gen (C/Objective‑C), jigen (Java/Kotlin) and upcoming build hooks for bundling native libraries without plugins. Covers concrete problems—Xcode 16 and header/version drift, lack of runtime availability checks, transitive dependency and packaging gaps, and real bugs from memory leaks—plus real examples like OpenCV, SQLite, ffmpeg and Pure Data. No big product reveal; useful if wanting specific tooling status, limitations and where documentation or community examples are urgently needed.
AI-written summary · about
chapters (12)
- 0:00Session introduction
- 1:04Native interop state
- 3:31Xcode compatibility with FFI
- 14:08Improving development experience for native interop
- 18:07FFI real-world challenges
- 21:58Integrating large C/C++ projects
- 29:45Low-latency audio callbacks
- 31:51FFI memory management pitfalls
- 36:29Industry FFI gaps
- 37:57Tighter native integration
- 40:08Platform API changes impact
- 42:35Closing remarks
related talks
50mPast, Present and Future of Native Interop
38mThe 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
37mUsing Dart FFI for Compute-Heavy Tasks in Flutter Apps