Skip to main content
Not every Android app needs to go through the Play Store. Capwrapper produces a signed APK alongside the AAB in every Android build, and you can distribute that APK directly to users — no store listing, no review process, no waiting. This approach is common for enterprise internal tools, private beta programs, and deployments in regions where Google Play is unavailable or unreliable.

​
When to use direct APK distribution

Direct APK distribution is a good fit when:
  • You are deploying an internal tool to a known set of employees or field teams
  • You need a private beta without the overhead of a Play Store track
  • You are targeting markets where the Play Store is restricted or not available on devices
  • You want to ship an update immediately without a store review cycle
  • Your app is not suitable for public listing (e.g. enterprise-only, white-labeled for a single client)
If your app is intended for public discovery, automatic updates, and broad consumer distribution, the Play Store is the better long-term path. Play Store apps benefit from Google’s security scanning, automatic update delivery, and user trust signals that direct APK installs do not provide.

​
Download your APK from Capwrapper

Once your Capwrapper build completes, open the build result in your dashboard and click Download APK. The file is fully signed using the keystore you configured — it is the same binary that users will install.

​
How users enable APK installation

Android blocks installation of APKs from outside the Play Store by default. Users need to grant permission to install from an unknown source once before they can install your APK. The exact path varies by Android version:
When a user opens the APK, Android will prompt them to allow installation from the specific app they used to open it (browser, file manager, email client, etc.). They tap Settings, toggle Allow from this source, then return to complete the install.The permission is granted per source app, not system-wide, which limits exposure.
Only distribute APKs from trusted, controlled channels. Direct APK installs bypass Google Play’s security scanning. If your distribution link is compromised or the APK is tampered with, users have no automated protection. Use HTTPS for any hosted download links and consider checksums or code signing verification for high-security deployments.

​
Distribution methods

Choose the method that fits your deployment scale:

​
Small teams and beta testers

Share the APK file directly over:
  • Email — attach the APK and send to your testers
  • Slack or Teams — upload as a file attachment in a dedicated channel
  • Cloud storage — upload to Google Drive or Dropbox and share a link; both support direct file download on Android

​
Self-hosted download page

Host the APK on your own website or internal portal. Link to the .apk file directly — Android browsers will prompt the user to download and install it. This approach gives you control over versioning and access.

​
Enterprise MDM deployment

For fleet deployments across many devices, use a Mobile Device Management (MDM) system such as Microsoft Intune, Jamf, VMware Workspace ONE, or Google’s Android Enterprise. MDM systems can push and install APKs silently without requiring user interaction, making them ideal for managed corporate devices. Capwrapper APKs are compatible with all major MDM platforms — treat the signed APK as you would any other line-of-business app package.

​
User installation steps

For users installing manually without MDM:
1

Download the APK

Open the download link on the Android device. The file will download to the device storage. You will see a notification when it is complete.
2

Open the APK file

Tap the download notification, or open the Downloads app and tap the APK file.
3

Grant install permission if prompted

If Android asks for permission to install from an unknown source, tap Settings, toggle Allow from this source for the app you used to open the file, then press the back button to return to the installer.
4

Tap Install

Review the permissions listed on the install screen and tap Install. The app will appear on the home screen once installation completes.

​
Updating your app

Direct APK distribution does not include automatic updates — you are responsible for notifying users and distributing new versions. To update:
  1. Increment appVersion in your Capwrapper build config and trigger a new build
  2. Distribute the new APK through the same channel you used originally
  3. Users install the new APK on top of the existing app — Android preserves app data as long as the package ID and signing key remain the same

​
Over-the-air web content updates with NativeOTA

If your changes are limited to web content (UI, logic, copy) rather than native configuration, you can push updates without redistributing the APK at all. Capwrapper’s NativeOTA bridge allows your web app to update itself over the air — users get the latest content the next time they open the app, with no install step required. This is particularly useful for enterprise deployments where redistributing an APK to hundreds of devices is operationally expensive.