From long press to Play Store.
Testers report on the device. Duo fixes it. The fix comes back to the same phone. Every release is checked for Google Play.
The mobile loop
- Test on device mobile only
- Fix with Duo
- Verify on the same phone mobile only
- Play release check mobile only
- Size guard mobile only
Not a UI fix? A developer gets a note they can act on.
Where others stop
| What it covers | Bug report SDKs | AI code fixers | Bugoro |
|---|---|---|---|
| Report from the device, with build, screen and element | Yes | No | Yes |
| An agent opens the fix MR | No | Yes | Yes |
| The fixed build is installed on the tester's phone | No | No | Yes |
| The merge waits for the tester's Verify | No | No | Yes |
| Google Play policy check on every MR | No | No | Yes |
| Real download size on every MR | No | No | Yes |
- Before/After on real emulators
- Restricted permissions traced to the library that added them
- Target API 36 required from Aug 31, 2026
- Size growth flagged before merge
Three loops
-
Verified on the phone
Verify turns on automatic merging for Duo's fix.
-
Ready for Google Play
Checked on every MR; Duo opens safe fixes.
-
Lighter every release
Measured on every MR; Duo trims unused resources.
How the parts fit
-
The phone
QA build + Bugoro SDK
-
The Hub
Issues, installs, dashboard
-
GitLab
Duo flows + CI
-
The emulator farm
Before/After screenshots