Fix it tonight.
Not next week.
OverPush sends Dart changes straight to the Flutter apps already on your users' phones, on iOS and Android, without another store review. One command to release, one command to patch.
$ curl -fsSL https://overpush.dev/install.sh | bash
On Windows: irm https://overpush.dev/install.ps1 | iex · Android from Mac, Windows or Linux; iOS from a Mac.
Three commands.
Then you're done.
You keep building with Flutter the way you do now. OverPush adds a release step and a patch step on top.
Link your project
Create an app in the dashboard and connect the project. One config file, one dependency line.
$ overpush login $ overpush init $ flutter pub add overpush
Ship to the store once
Build your store release through OverPush so it knows exactly what shipped.
$ overpush release ios $ overpush release android
Push fixes, any time
Change your Dart code and patch. Users get it the next time they open the app.
$ overpush patch android $ overpush patch ios
Your app, your update UI.
OverPush puts nothing on screen. It tells your app what's happening, so you can show it in your own design or not at all.
Found, downloading, ready.
Listen to OverPush.events and get every step of an update: a new patch found, the download percent, and when it's ready for the next start. The same events on Android and iOS.
OverPush.events.listen((event) { switch (event) { case OverPushPatchFound(): show('New update found'); case OverPushDownloading(:final percent): show('Downloading update · $percent%'); case OverPushPatchReady(): show('Restart the app to apply it'); default: break; } });
main.dart, ready to copy. The banner is your app's code, not OverPush.
Fast to ship, safe to undo.
Every patch is verified on the device
A phone only runs a patch after it confirms the patch is genuine and meant for it. Otherwise it keeps the code it shipped with.
Bad patches undo themselves
If a new patch stops your app from starting, the device removes it and goes back to the shipped code. Even with no network.
Staged rollouts
Send a patch to 10% of devices first, then raise it when you're confident.
Kill switch
One command stops a patch on every device. Anyone on the team can run it.
Small downloads
Patches download in the background, once. On Android a small fix is a few hundred KB.
Your next fix can ship today.
Install the CLI, connect a project, and publish your first patch in about 15 minutes.