Taaha Rauf
Engineer III at Very Good Ventures
Taaha Rauf is an Engineer III at Very Good Ventures with five years of experience in Flutter development. His background includes contributions to both early-stage ventures and established enterprises. He has experience across the full lifecycle of app development, from initial creation to integration within cross-functional teams. His work on numerous production-scale applications has emphasized the critical importance of performance and optimization. This presentation will synthesize his practical experiences in identifying and resolving memory leaks in complex Flutter environments.
Your router doesn't work here: navigation in add-to-app Flutter
go_router, auto_route, and Navigator 2.0 all quietly assume one thing: Flutter owns the whole app. In add-to-app, it doesn't. The back stack is split across two runtimes, a deep link can start in native code and end in Flutter, and "pop" can mean six different things depending on who's on screen. Most teams reach for their favorite router, fight it for three sprints, and end up with a thousand-line workaround.
This talk is about what a router actually needs to do when Flutter is a guest in someone else's app. We'll tear down why mainstream routers break at the seam, work through the requirements a real add-to-app router has to meet, and walk through a design that keeps navigation sane on both sides. For anyone shipping Flutter modules inside an existing native app — or about to start.