How to share a mobile app build with testers and friends
The quickest way to get a build onto someone's phone is an install link. Upload the .apk or .ipa to buildtree, then send the link or its QR code. Android testers tap Install. iPhone testers can install too, once their device is registered in your ad-hoc provisioning profile. There is no app store review, no TestFlight, and no tester account on public projects.
This works for any framework: Expo, React Native, Flutter, native Android and native iOS.
Share an Android app
1. Build an APK
Android phones install .apk files. An .aab (Android App Bundle) is for the Play Store and does not install directly.
| Framework | Command | Output |
|---|---|---|
| Expo | eas build --local --platform android --profile preview --output build/App.apk | build/App.apk |
| React Native | cd android && ./gradlew assembleRelease | android/app/build/outputs/apk/release/app-release.apk |
| Flutter | flutter build apk --release | build/app/outputs/flutter-apk/app-release.apk |
| Native Android | ./gradlew assembleRelease | app/build/outputs/apk/release/app-release.apk |
For Expo, the preview profile in eas.json needs "android": { "buildType": "apk" } to produce an APK instead of an AAB.
2. Upload it
Pick whichever fits:
- Dashboard: create a project, then drag the file onto Upload build.
- CLI:
npx @buildtree/cli upload build/App.apk --env dev - AI agent: with the MCP server connected, ask "upload this build to buildtree and give me a QR code".
3. Send the link or QR code
Every upload gets an install link like https://buildtree.sh/install/<id> and a QR code. The person opens it on their Android phone and taps Install on Android. The first time, Android asks them to allow installs from their browser; that is a one-time system prompt.
Share an iPhone app without TestFlight
Apple only lets an ad-hoc build install on devices listed in its provisioning profile. buildtree collects those devices for you:
- Open the project's Devices page and send testers the registration link.
- Each tester opens it in Safari on their iPhone, enters their name and email, and installs the small configuration profile that shares the device ID.
- Approve the devices, then Download for Apple Dev Portal and add them in your Apple Developer account.
- Regenerate the ad-hoc provisioning profile, rebuild the
.ipa, and upload it. - Send the install link. The tester taps Install on iOS in Safari.
You need an Apple Developer Program membership to sign ad-hoc builds. Details and troubleshooting are in iOS distribution.
Which link to send
- Pinned link (
/install/<id>): always installs that exact build. Good for "can you check this fix". - Folder link (
/install/folder/<project>/<env>): always the latest build for that environment, or for a branch. Good to bookmark for QA and stakeholders. - Release link (
/install/release/<project>/<tag>): frozen to a version tag.
More in Install URLs and QR codes.
Keep it private
Install links are public by default, so anyone with the link can install. On paid plans you can require email verification and allow specific addresses or whole domains. See Private install links.
Get feedback back
Every install page has a Send feedback button. Testers pick Bug, Works or Suggestion, write a note, and attach screenshots. It lands on the build in your dashboard and in your inbox. See Tester feedback.
Related
- Quickstart
- buildtree vs TestFlight, Firebase App Distribution, Diawi and EAS
- FAQ
- Share Expo builds with testers
- Share React Native builds with testers
- Share Flutter builds with testers
- Troubleshooting installs and uploads
Last updated