Give your AI agent eyes on your Flutter app.
fdb drives a running Flutter app from the CLI. No MCP needed, works with any bash-capable agent.
https://t.co/bmprr2eFmD
@FlutterComm@biz84@kaushikgopal
@somi_ai@HuyNguyenTw Hooks into the existing Flutter VM service - same one DevTools uses. fdb_helper registers a few VM service extensions on top for things like widget interaction, but the transport is standard.
@justin_vu113@HuyNguyenTw@jezell Thanks!
Main difference is philosophy - Marionette added CLI as a fallback, fdb was CLI from day one. No MCP, no protocol overhead, just bash. Also handles app launch so the agent never touches VM URIs, plus deep links, SharedPreferences, and waiting for widgets/routes.
@itstarun1994@HuyNguyenTw Yes! The agent takes a screenshot to see the coordinates, then taps with fdb tap --at x,y. Just tell your agent: "Fetch and follow instructions from https://t.co/50DYMhBImY" and it sets itself up and figures out the rest.
@Michael08079961@HuyNguyenTw Works with both today! Both support the Agent Skills standard natively - just feed this to your agent and it'll handle the rest: https://t.co/6yLkXHJwQu
Give your AI agent eyes on your Flutter app.
fdb drives a running Flutter app from the CLI. No MCP needed, works with any bash-capable agent.
https://t.co/bmprr2eFmD
@FlutterComm@biz84@kaushikgopal
@TurkishAirlines@TurkishAirlines you lost our luggage on 29 Dec.
6 days later: only generic call-center replies, no updates, no timeline, no interim support.
Is this normal for you?
Exciting moment! The #Flutter app I architected and led the team on at Picnic is now open-sourced on GitHub. It follows best practices of Clean Code, Clean Architecture & MVP pattern using BLoC and solid CI/CD setup. Proud moment! #OpenSource#PicnicApp
https://t.co/jKIRndxl3a
@MateuszBrat "sometimes" was used in a context that it's simply SOMETIMES faster and most of the time its on par with the performance. Using metal under the hood is not an extra block, cause the same block of "extra" is added when developing in native by using swift/kotlin code
@MateuszBrat it only proves someone chose either a bad cross platform technology (FB using html5 which was a disaster and completely not optimized for robust mobile usage). or had simply bad developers delivering the requirements.