Online APK installer: share an Android build with a link

Nov 3, 2026 · 9 min read

"Online APK installer" usually means one simple thing: you have an Android build, and you want someone else to install it on their phone from a link instead of a cable, a USB stick or a file in a chat. Unlike iPhone, Android allows this by design. The phone downloads the .apk from a web page and installs it once the owner allows it. The service in the middle hosts the file, makes the link and the QR code, and helps when the install fails.

This guide is the Android twin of our online IPA installer article. It covers what an install link does on Android, the steps for the developer and the tester, the reasons for "App not installed", what to do with an .aab, and how to stay safe. It is about your own builds. If you are looking for modified or cracked apps, this is not the page for that, and AppForShare refuses those uploads.

What an online APK installer does

An Android app file is an .apk. Android can install it from any source the phone owner allows, so an install link is mostly hosting plus a good page:

You upload the .apk. The service reads the app name, package name, version and minimum Android version from it.
It gives you an install page with a link and a QR code.
The tester opens the link on the phone and taps Install. The browser downloads the .apk.
Android asks whether this browser may install apps, once, and then installs the app.

The service does not install anything by itself. Android does, after checking the app's signature against any copy already on the phone. That is why most failures come from signing, not from the link. There is no device list like on iOS: any Android phone that meets the minimum version can install the build.

Steps for the developer

Build a signed APK. A debug build works for quick tests, but use the same signing key for every build you hand out, so new builds install over old ones. A release build signed with your upload key is the usual choice.
Raise the version code on every build you share. Android will not install a lower versionCode over a higher one without uninstalling first, which wipes the app's data.
Upload it. On appforshare.io, files up to 50 MB need no account and the link lasts 3 days. A Free account takes 150 MB, keeps links for 7 days, lets you set a password and shows the total install count per build. Pro takes 2 GB and links stay live while you subscribe.
Send the link or the QR code. A QR code on a laptop screen is the fastest way to get a build onto a phone on the same desk.

Before you send it, the free APK analyzer reads the file in your browser and shows the package, version, minimum and target SDK, permissions, native libraries and who signed it, including a warning for a debug key. The file is not uploaded.

Steps for the tester

Open the link on the Android phone, in Chrome or the phone's own browser. Links opened inside some chat apps download into the chat app instead; if nothing happens, open the link in the browser.
Tap Install on the install page. The download starts.
Allow unknown apps once. The first time, Android says the browser is not allowed to install apps. Tap Settings, turn on "Allow from this source" for that browser, and go back. This is a per app setting; you will not be asked again for that browser.
Play Protect. Google Play Protect may show a warning for an app it has not seen before, which is normal for a test build. If you trust the sender, tap "More details" and then "Install anyway".
Open the app. It appears in the app drawer like any other app.

The AppForShare install page has an Install help list with these steps, in 7 languages, and it warns before the tap when the phone's Android version is lower than the build needs. See install help.

"App not installed": the usual causes

Cause	How to tell	Fix
Signature conflict	A copy of the app is already installed, signed with another key (often the Play Store version, or a build from another computer)	Uninstall the other copy, then install again. Sign every test build with the same key
Downgrade	The installed copy has a higher version code	Uninstall first, or share a build with a higher version code
Not enough storage	The phone is nearly full	Free some space; an install needs room for the APK and the installed app
Android too old	The build's minimum SDK is above the phone's Android version	Use another phone, or lower the minimum SDK if the app allows it
Wrong architecture	The APK has native libraries only for other CPU types	Build a universal APK or include the phone's ABI
Broken download	The download stopped part way	Delete the file and download again on a stable connection

A signature conflict is by far the most common. It also explains why a tester who installed the app from Google Play cannot simply install a test build on top: unless the test build is signed with the same app signing key, Android refuses it. Our guide to Android app signing explains keys, Play App Signing and signature schemes in detail.

What about an .aab file?

An Android App Bundle (.aab) is a publishing format for Google Play. Play turns it into small APKs made for each device. A phone cannot open an .aab directly, so an online installer has to turn it into an APK first.

On AppForShare, a Free account or higher can upload the .aab itself. The service runs Google's bundletool and the build becomes one universal APK that testers download. The bundle itself is not kept. The APK is signed with your workspace's AppForShare test key, the same key for every later bundle, so test builds update each other. Two things follow from that:

A test key APK cannot update the app installed from Google Play. Testers uninstall the Play version first; the install page says so.
On Pro and Team, an Admin can add the workspace's own upload keystore instead. Builds signed with it update each other, but they only install over the Play version if that key is the app signing key. Most apps use Play App Signing, where Google holds that key, so testers still uninstall the Play version.

The universal APK is not identical to what Play delivers, since Play makes split APKs per device. For testing features that is rarely a problem. More options, including bundletool on your own machine and Play internal app sharing, are in how to install an .aab file on Android. Details of the feature are on .aab upload.

Do not install APKs from strangers

The same openness that makes Android test builds easy makes it easy to pass around harmful apps. A few habits keep testers safe:

Know the sender. Install builds only from the team or developer you are testing for, from a link they sent you directly.
Check the package name and signer. The APK analyzer shows both. A test build of "Acme" should carry Acme's package name, and the same signer every time.
Look at the permissions. A to do list app that asks for SMS and accessibility access deserves a question.
Turn unknown sources back off for apps you used only once, such as a chat app that downloaded an APK.

On our side, uploads whose package belongs to a large company that never ships test builds through us, such as Google, Meta or TikTok, are refused, and so are known malware package names. Guest uploads named like a hack, mod or cheat are refused too. To be clear about limits: this is a check of package names and app names, not a malware scan.

Android developer verification

Google is adding developer verification to Android. As listed on developer.android.com and summarised in our verification guide: from September 30, 2026, certified Android phones in Brazil, Indonesia, Singapore and Thailand check apps installed from seven named app stores. Direct installs from a link, which is what an online APK installer does, are not covered in that first phase. Google says the checks go global in 2027. If you share test builds, register your package name and signing key in good time. Note that the AppForShare test key used for .aab uploads cannot be registered by you, so use your own keystore or upload a self signed APK. The long version is in Android developer verification for test builds.

Picking a service

Several services call themselves an online APK installer. AppsOnAir (by Logicwind) publishes a guide to using its OTA Distribution that way; as listed in its FAQ on November 3, 2026, it takes .apk and .ipa files, needs an account and an app set up before the first upload, and its free plan allows 300 MB builds and links up to 30 days without a password. InstallOnAir, as published on its site in November 2026, takes 200 MB without an account and does not take .aab files. Things worth checking on any of them:

Can you upload without an account, and how long does the link last?
Can you set a password on the link?
Does it take .aab files, and with whose signing key?
Does the install page explain failures, in the tester's language?
Can testers send feedback without installing another app?

On AppForShare, testers send a bug or idea with up to 5 screenshots from the install page, with no app and no sign in, on every account plan (see tester feedback). Our free tiers comparison and AppsOnAir alternative put the services side by side.

Common questions

Can I install an APK from a link without Google Play?

Yes. Allow the browser to install unknown apps once, then install from the page. Play Protect may ask you to confirm with "Install anyway".

Why does my phone say "App not installed"?

Most often another copy of the app is installed with a different signing key, or the installed copy has a higher version code. Uninstall it and try again.

Can I upload an .aab to an online APK installer?

Only to a service that converts it. AppForShare does, on Free and up, into one universal APK signed with your workspace's test key or, on Pro and Team, your own key.

Does AppForShare sign or change my APK?

No. An uploaded .apk is delivered as you built it. The only signing AppForShare does is for APKs made from .aab uploads.