Release an APK. Know which devices received it.
Bring your Android releases into one catalog, choose which configurations receive them, and check installation reports from the devices. Introduce a release in batches when you need to limit the first deployment.
See a staged app deploymentFrom APK upload to installation report
- 01
Upload
Add standalone APKs to the application catalog.
- 02
Validate
Check package metadata, signatures, version codes, and signing identity. Invalid uploads show an error.
- 03
Assign
Choose the device configuration and its version strategy.
- 04
Deploy
Send the release through the configuration. Use an optional rollout to start with a smaller batch.
- 05
Review
Compare intended versions with device installation reports and investigate errors.
Choose how devices receive new versions
| Version strategy | Use when | What happens |
|---|---|---|
| Pin a release | You need a fixed software baseline. | The assigned version stays in place until you change it. |
| Follow latest | Devices should adopt new releases. | The assignment resolves to the latest available version. |
| Update on an API trigger | Your release process needs an approval or promotion event. | The linked trigger promotes the assignment to the latest version when it runs. |