Most Flutter teams discover Shorebird, integrate it in an afternoon, and ship their first patch feeling like they've unlocked a superpower. Then they hit production at scale and things get quietly broken. This talk picks up exactly where the getting-started guides leave off. We'll open with a precise look at how Shorebird actually works under the hood: the modified Flutter engine, bytecode diffing, and why iOS patches go through a custom Dart interpreter while Android runs at full native speed. Then we'll walk through the war stories that Scapia faced after the early stage setup, the iOS patches that vanished for months while the console showed them as "available," and the embarrassingly simple lock file trap that caused it all. The second half is a production blueprint. We built a custom control plane on top of shorebird_code_push and Firebase Remote Config that transforms Shorebird from a silent background utility into a surgical precision tool, targeting patches by platform, user onboarding state, and experiment cohort, with a hard-blocking overlay for critical security fixes.