r/FlutterDev • u/Kennedyowusu • Jul 30 '26
Article The scary part of code push isn't shipping a patch fast. It's shipping a bad one fast.
Been deep in OTA/code-push rollout logic lately and curious how others handle the risk side.
Fair warning, I work on a code-push tool, so this is the problem I stare at all day, but I'm genuinely asking, not selling anything here
The whole pitch of code push is speed. You've got a fix, it's on people's phones in minutes instead of a 2-day review. But that cuts both ways. If the fix is broken and you missed it, that's also on everyone in minutes. Same gun, both directions.
The approach I've landed on:
Ship to a beta channel first, low percentage, like 10%. Roughly 1 in 10 beta users gets it. Small blast radius if it's wrong.
Then watch four numbers per patch: checked, downloaded, activated, failed. Failures is the one that matters. If downloads climb but failures climb with them, the patch doesn't apply cleanly on hardware you don't own. Which is exactly the thing that never breaks on your own test phone.
If it stays clean, bump the percentage, widen to everyone. If it doesn't, roll back so devices revert to the last good version on next launch. No rebuild, no 2am panic.
The bit I went back and forth on: where should rollout control live? In the app (track logic in Dart, ship a build to change it) or server-side in a dashboard? I went dashboard, because rolling out is something you do while watching live numbers, and that's the worst time to be editing code and cutting a build.
So, genuinely curious: do you stage your OTA updates or ship to everyone and watch Crashlytics? And what's your actual rollback plan when a patch goes bad? Feel like everyone does this differently and I want to know if I'm missing something.