Gabriel Palmisano

Flutter, Maps & open source | Mobile Dev @ebworld_team 🧑‍💻 | @maplibre Flutter lead maintainer 🗺️

[antirez @antirez]

Accept the present and the future. Embrace it. Have an evidence based career where you try doing meaningful things. Create open source software that does not exist currently since in the past it required teams of people and there were not the economic incentives but now with AI it is possible for individuals to do it.

[Gabriel Palmisano @gabbpalma]

@ronithhh ok that's crazy

[Gabriel Palmisano @gabbpalma]

@matiwojt @LeanCodePl @typesafeai that’s super!

[Gabriel Palmisano @gabbpalma]

@MarcDietschi @claudeai @ClaudeDevs unusable

[Fluttercon @FlutterconWorld]

One Dart API. Three completely different engines underneath. 💙

@gabbpalma dissects how Flutter MapLibre achieves parity across platforms, at flutterCon Berlin.

🔗 https://t.co/1kFr4LYRz2

#FlutterDev #nextapp26

[Gabriel Palmisano @gabbpalma]

@kpanicd that was the goal! Thanks :)

[Gabriel Palmisano @gabbpalma]

Interactive vector maps in Flutter: Android, iOS & Web from one Dart API.

MapLibre Flutter 0.27.0 is out! Better platform parity, faster startup, large GeoJSON updates off the UI thread.

And a new super cool docs site :)
https://t.co/VKa61THohb

#flutter #dart #maplibre #maps

[Gabriel Palmisano @gabbpalma]

Interactive vector maps in Flutter: Android, iOS & Web from one Dart API.

MapLibre Flutter 0.27.0 is out! Better platform parity, faster startup, large GeoJSON updates off the UI thread.

And a new docs site, with every guide as a live map :)
https://t.co/VKa61THohb

[Gabriel Palmisano @gabbpalma]

@sflorimm https://t.co/oR46KbElS1

[Gabriel Palmisano @gabbpalma]

Google when a screen needs its data, imagery and Street View.
MapLibre when a screen needs vector power and control.

One codebase. The right map for every screen.
The skill was never picking a side. It's building so you never have to.
@maplibre #WhichMapIsThat

[Gabriel Palmisano @gabbpalma]

30,000 elements on a single Flutter map.

Zero stutter. Most map stacks choke way before that.
The trick isn't picking the right engine. It's not picking one at all. 🧵

[Gabriel Palmisano @gabbpalma]

For a while I treated it as either/or. Then I stopped choosing.
Every engine sits behind one map control interface. Each screen picks its engine by context, decided up front. Not swapped live: that'd be a UX mess. The right engine is wired in before the screen loads.