App Install Links That Control Who Installs Your Build, and How
Every release gets app install links you control: public or private, plain or branded, one release visible or the whole history. Share an IPA or APK once, and testers install it from a link or QR code.
WHAT YOU GET
What Every Install Page Includes
Password Protection
Keep a release open to anyone with the link, or lock it behind a password so only the people you've actually shared it with can install.
Public Downloads
Skip the password entirely for an open beta or a public demo, no login or credential needed on the visitor's end.
All Releases, One Page
Show older releases on the same install page, so a returning tester can install any version, not just the latest one.
Step 01
Create an app
- 1
App Name
Up to 24 characters, shown on the public page.
- 2
Custom tags
Up to 16 characters, helps you find the app later.
- 3
App stage
Mark it Staging, Development, or Production for your team.
- 1
Logo
Upload your own, shown at the page's top.
- 2
Layout
Portrait or landscape, whichever fits your page better.
- 3
Favicon
Set what shows in the visitor's browser tab.
- 4
Theme
Pick a color theme for the whole page.
STEP 02
Configure the publish page
Step 03
Upload the build
- 1
Upload
Drag in your .apk or .ipa file, up to 2GB on Business.
- 2
Link type
A fresh Unique URL, or one Persistent URL for every release.
- 3
Per-release settings
Adjust password protection independently on each release, if needed.
- 1
Page link
The public page itself, ready to open anywhere.
- 2
Install link
A direct link that triggers the install itself.
- 3
QR code
Scan-to-install, for testers standing right in the room.
STEP 04
Share the page link
FAQ
Questions About Install Links
What are app install links?
App install links are direct URLs that install an iOS or Android build on a tester’s device with one tap, no app store involved. Every AppShare release gets three: an install link that starts the download, a page link to a public install page with build details, and a QR code for scanning in person.
Do app sharing links expire?
Yes, every release has an expiry date. The maximum depends on your plan: 15 days on Free, 30 on Starter, 60 on Growth, and 90 on Business. You can set a shorter expiry on any release, or extend it in release settings before it runs out. After that, the install page stops accepting new installs.
How do I keep a build out of search results?
Turn on the hide-from-search-engines toggle on the publish page. It works separately from password protection, so a public install page can stay open to anyone with the link while staying out of search results. Password-protected pages never appear in search, so use both when a build should stay fully private.
How do I share an IPA or APK with testers?
Upload the .ipa or .apk to your app in AppShare, then send the install link, page link, or QR code it generates by email, Slack, or any chat. Testers install from their phone with no store account. For an ad hoc IPA, the tester’s device UDID must be in the build first, or the install fails.
Should I use a Unique URL or a Persistent URL?
Use a Unique URL when each build should have its own link, since one is generated automatically for every release and can’t be customized. Use a Persistent URL when testers should keep one bookmark: it uses a custom slug and stays the same across releases, so the page is updated in place with each new build.
Can I password-protect just one release and leave others public?
Yes. Password protection is set per release, so one build can sit behind a password while others on the same app stay public. Turn it on in that release’s settings. It suits client demos or pre-release builds you want contained, while an open beta on the same page stays installable for anyone with the link.
Get Started
Set Up Your First Install Page
Create an app, configure the page once, and every release after that has somewhere to live.
Free plan available
Public or private, your choice
Custom domain support