Gabriel Palmisano
Mobile Developer @ EBWorld
I am a Mobile Developer at EBWorld and maintainer of the Flutter MapLibre package (maplibre_gl), specialized in building mobile apps with advanced mapping. My mission is to bring geospatial data out of the office: I build Flutter apps that turn complex infrastructure, such as telecom networks or aqueducts, into essential operational tools for the people working out in the field.
I have been writing code since I was very young, driven by a curiosity to explore the limits of the technologies I use. Beyond my work at EBWorld, I actively contribute to open source to improve the tools developers rely on every day.
As a speaker, I love bringing real-world use cases to the stage, translating complex architectural challenges into practical solutions for the community.
Chasing Behavioral Parity: Java, Swift and JS Interop in Flutter
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.