From your terminal
to their phone, in minutes.
Keep building with Flutter the way you do today. OverPush adds one step when you release and one when you fix something.
Connect your project
Create an app in the dashboard, then connect your Flutter project from the terminal. Your repo gets one small config file and one dependency line. No changes to main.dart, no native code.
$ overpush login ✓ Signed in $ overpush init ✓ Connected to my-shop $ flutter pub add overpush
Release to the store, once
Build your App Store or Play Store release through OverPush. It records exactly what shipped, so every later fix can be checked against it. Then submit the build the way you always do.
$ overpush release android ✓ App bundle ready for the Play Store $ overpush release ios ✓ Release ready to upload $ overpush upload ios ✓ Sent to App Store Connect
Fix, patch, done
Found a bug? Fix the Dart code and run one command. Start with a small share of users if you want, and raise it when you're happy. The CLI tells you if your change needs a store release instead.
$ overpush patch android --rollout-percent 10 ✓ Patch 4 published · 10% $ overpush patch ios --rollout-percent 10 ✓ Patch 4 published · 10%
Invisible to your users. Obvious to you.
No prompts, no loading screens, no "update available", unless you want one: your app gets update events to show in its own design.
Check
The app quietly looks for a fix when it opens.
Verify
It makes sure the patch is genuine and meant for it.
Download
In the background, once per patch.
Apply
The next launch runs the fixed code from the first screen.
Stay healthy
If a patch breaks startup, the device rolls it back.
A one-line bug shouldn't take a week.
Store update days
- MonBug report arrives. You fix it in ten minutes.
- MonBuild, archive, upload, fill in the release form.
- Tue–WedWait for review. Maybe a rejection over an unrelated screenshot.
- ThuApproved. The update starts rolling out.
- Next wkHalf your users still haven't updated.
OverPush minutes
- MonBug report arrives. You fix it in ten minutes.
- +2 minPatch published for Android and iOS, to 10% of users.
- +1 hrPatched devices look healthy on the dashboard.
- +1 hrRollout raised to 100%.
- Next openEvery user who opens the app gets the fix.
See it on your app.
The getting-started guide takes you from install to first patch in about 15 minutes.