The same Dart API should give you the same map behavior on Android, iOS, and Web. Achieving that behavioral parity is the hard part: there is no single map engine. A C++ core runs on mobile, a JavaScript engine on the Web, each reached through a different interop boundary.

This talk dissects the federated architecture of Flutter MapLibre, the open-source maps plugin: how an abstract factory unifies distinct runtimes under one stable contract, and exposes platform gaps honestly where features cannot match.

We follow one call down to native code on each platform, into an interop stack that is itself moving: the Web is already modern and Wasm-ready, while the Mobile roadmap drops the Java and Swift wrappers to reach the C++ engine directly, a breaking shift.

Even if you never touch a map, you will leave knowing how Flutter reaches native code, when to use Method Channels, js_interop, or FFI, and how to architect a federated API that holds behavioral parity without breaking it.