The problem
Mobile delivery across the team ran on separate native iOS and Android codebases, with Ionic filling in elsewhere — meaning UI work was duplicated per platform, every screen change meant multiple implementations, and shipping a new app leaned on a dedicated mobile team per platform rather than one shared workflow.
My role
Sponsored and led the evaluation-to-adoption decision as Engineering Manager, COE UI.
Approach
Ran a structured evaluation, then a production pilot, before committing to FlutterFlow as permanent tooling across the mobile engineering practice — a deliberate bet on low-code UI development for the parts of mobile delivery where it fit.
Outcome
FlutterFlow is now permanent tooling across the mobile engineering practice — new mobile features ship from a single low-code codebase instead of parallel native builds, freeing the team’s iOS and Android engineers to focus on the pieces that still need native code.