HomeKnowledge BaseDownload Build
Publish

How to Download Your Build for Testing

Before submitting to the App Store, you can install a test build directly on your device to verify the final app experience. Here's how to download and install it.

5 min read6 sectionsUpdated Mar 2026

1   Testing options overview

MobiDrag gives you several ways to test your app before it reaches the App Store. Choose based on how much fidelity you need and how quickly you need it:

MethodSetup timeFidelityBest for
QR Code PreviewInstantHigh — live data, real blocksQuick design checks during building
Beta Build20–30 min buildFull native appPre-launch UAT, stakeholder review
TestFlight (iOS)~1 hr (Apple review)Full native appDistributing to a team of iOS testers
Android APK20–30 min buildFull native appSideloading on Android test devices

2   Option A: QR code live preview (quickest)

For most design and content checks, the QR code preview is the fastest way to see your app on a real device. No build needed — it opens in your phone's browser in seconds.

  1. 1In the App Builder, click Publish to open the App Preview page.
  2. 2In the right sidebar, click Generate QR Code.
  3. 3Scan the QR code with your phone's camera.
  4. 4The live preview opens full-screen in your browser.
QR code modal with scan instructions and Copy Preview Link button
QR Code modal — scan to open the live preview instantly on your phone

The QR preview does not require a build to complete. Use it freely during design iterations — it reflects your last saved state.

3   Option B: Submit a Beta build

A Beta build is a full native app binary, identical to a production release, but flagged for internal testing rather than public distribution. This is the closest you can get to the real app without going through full store review.

  1. 1Go to the App Listing form (click Publish on the App Preview page).
  2. 2Under Platform & Region, select Beta as your target platform.
  3. 3Complete the required fields and click SUBMIT FOR PUBLISHING.
  4. 4The build pipeline runs (~20–25 minutes).
  5. 5Once the build is complete, a download link or distribution invite is sent to your registered email.

4   Option C: TestFlight for iOS testers

If you submit with App Store selected as the platform, you can use Apple TestFlight to distribute the build to up to 10,000 external testers before public release:

  1. 1After a successful build, log in to App Store Connect (appstoreconnect.apple.com).
  2. 2Find your app and go to the TestFlight tab.
  3. 3Add tester email addresses in the External Testing group.
  4. 4Testers receive an email invite to install TestFlight from the App Store and then download your beta.
  5. 5Apple's TestFlight review takes up to 1 business day for the first beta submission.
ℹ️

TestFlight links expire after 90 days. Submit a new build before the link expires to keep testers on the latest version.

5   Option D: Android APK sideload

For Android, you can request an APK file to install directly on a test device without going through Google Play:

  1. 1Contact MobiDrag Support and request an APK build for your app.
  2. 2MobiDrag generates and emails you a signed debug APK.
  3. 3On your Android device, go to Settings → Apps → Special App Access → Install Unknown Apps and allow your file manager or browser.
  4. 4Open the APK file on your Android device and tap Install.
  5. 5The app installs like any Play Store app. You can keep it alongside the production version.
⚠️

APK sideloading requires enabling Unknown Sources on your Android device. Remember to disable this setting again after installing, as a security best practice.

6   Finding your builds in the App Listing

All your submitted builds are visible in the Publish Your App page. The status of each build is tracked in real time:

App Listing form showing build status and Publishing Requirements panel
Publish Your App — App Listing form with Publishing Requirements and build submission

From the App Listing page you can:

  • Monitor the current build status (Queued, Building, In Review, Published, Failed)
  • View the build log if a build failed
  • Re-submit after fixing a rejection
  • Save a draft to update metadata before the next release