Every Flutter plugin lives or dies at one seam: the boundary between Dart and native code. Most of us cross it with MethodChannel, which trades away everything Dart's type system gives us. Method names become magic strings that fail at runtime. Arguments become hand-rolled maps. Return types become hopes. Multiply that across iOS, Android, and desktop, and one plugin becomes three fragile contracts that drift apart the moment someone adds a field.

This talk is about Pigeon, the Flutter team's code generator that turns the native boundary into a single type-safe contract: write one Dart interface, and Pigeon generates the Dart, Swift, and Kotlin sides in agreement. We'll cover both directions of communication, async calls and error propagation, and what Pigeon deliberately can't do. The takeaway: the native boundary should fail at compile time, not in production — so start type-safe rather than graduate to it.