Make build sharing part of your CI/CD pipeline
Upload an APK or IPA from your terminal with the AppsOnAir CLI. Add the same upload step to your build pipeline so each new test build is ready to share without a manual handoff.
Upload an IPA or APK, choose who can install it, and share link. Your QA team, clients, or pilot users can start testing without waiting for a public app store review.
AppsOnAir connects the file, the people, and the install page in one release flow.
Upload an APK or IPA from your terminal with the AppsOnAir CLI. Add the same upload step to your build pipeline so each new test build is ready to share without a manual handoff.
Pick a part of the release to see how AppsOnAir keeps it moving.
Share the release with your testers. They follow the link, confirm the build, and install it on their phone. The public app store review can wait until the app is ready for release.
Share it in the channel your team already uses.
Testers can check the version before install.
The build reaches the device without a public store listing.
After you share a build, testers can use the AppsOnAir mobile app on iOS or Android to send feedback or report a bug. Their report reaches workspace users as soon as they submit it.
You can upload IPA builds for iOS and APK builds for Android, then share an install link with your testers.
No. AppsOnAir is for sharing test builds directly, so the team can review a build before its public store release.
Yes. Use password protection and choose the groups that should have access to a release.
AppsOnAir keeps version history, so you can find an earlier release and restore it when needed.
The dashboard shows release, upload, and download activity, helping your team see what happened after a build was shared.
Share your next iOS or Android test release with AppsOnAir OTA.