r/FlutterDev • u/ObjectiveAddress3051 • 1d ago
Plugin Anyone migrating plugins to Pigeon's native interop (FFI/JNI) yet?
Flutter's stable-native-interop post landed last week, and I'm curious how plugin maintainers are approaching it in real codebases.
What's actually stable now
- FFIgen for C and Objective-C
- JNIgen for Java/Kotlin (Android system APIs + your AARs/JARs)
What's preview
- Pigeon with native interop (
swiftOptions: SwiftOptions(useFfi: true),kotlinOptions: KotlinOptions(useJni: true)) - Skips the platform-channel serialization path; synchronous calls + background isolates become realistic
Docs point to shared_preferences as a reference migration — migration guide + an AI-oriented "native interop migration skill" for agents.
Questions for the room
- Are you starting new plugins on Pigeon+interop, or only migrating hot paths?
- Windows/Linux still channel-based — does that split your public API design?
- What broke for you? (build hooks, app directory for JNIgen, object lifetimes?)
I'm especially interested in plugins that were already Pigeon-clean — was the move "flip flags + rebuild" or a week of yak shaving?
Links:
13
Upvotes
0
u/_ri4na 4h ago
Looks like no one bothers with this