Preview builds for every pull request (Android, Flutter, React Native, Expo)

Web teams take preview deployments for granted. For mobile apps, a reviewer needs an installable build on a real phone. Here's how to get one on every pull request.

Why preview builds

Code review catches code problems; using the app catches the rest: layout on small screens, slow screens, broken flows. A preview build per pull request lets reviewers test exactly that change.

Option 1: automatic (no CI to write)

Connect your GitHub repo to Digidropp. It detects Android, Flutter, React Native or Expo, opens a pull request that adds the build workflow, and from then on:

• Every pull request gets a comment with an install link and QR code.
• The link follows the pull request: it always installs the newest build from it.
• Builds from main update your app's main install link; previews never touch it.

Option 2: add one step to your existing CI

Already build in GitHub Actions? Add the digidropp/upload-action step after your build. It uploads the APK or IPA and posts the same PR comment.

Signing that doesn't break updates

CI runners create a new debug key on every run, which forces testers to uninstall. Digidropp's automatic builds use one stable signing key per repo, so testers can always update.

Digidropp · Guide · Docs · Alternatives