Sideloading and alternative app marketplaces security

App distribution is no longer only the two official stores. Android has always allowed sideloading, installing apps from outside Google Play, and since regulatory changes in the EU, iOS now permits alternative app marketplaces and web distribution there too. For users that means apps can arrive without passing the official store's review. For developers it means your app may be distributed, and potentially repackaged, outside the channel you control, which raises the weight of the platform's other protections, app signing, attestation, notarization, and of verifying that a running copy is genuine. Here is what sideloading and alternative marketplaces change for security and how to protect your app.

Short answer

Sideloading is installing apps from outside the official store, long possible on Android and, following EU regulatory changes, now possible on iOS via alternative app marketplaces and web distribution in the EU. Per Apple's notarization for iOS apps and Android's install-unknown-apps model, apps distributed outside the main store may bypass the full store review, though platforms apply baseline checks, Apple notarization and Google Play Protect. For developers, the implications are that your app can be distributed and possibly repackaged outside your control, so verifying app integrity and installation legitimacy matters more: use signing, and platform integrity signals like Play Integrity or App Attest verified server-side. Sideloading raises the importance of the platform's non-review protections and of confirming a running copy is genuine.

What you should know

• Sideloading installs apps outside the official store: bypassing its full review.
• Android has always allowed it: via the install-unknown-apps permission.
• iOS now allows alternative marketplaces in the EU: following regulatory changes.
• Baseline checks still apply: Apple notarization, Google Play Protect.
• Verify integrity and legitimacy: signing and attestation matter more.

How does the distribution landscape compare?

Both platforms now allow distribution beyond the single official store, with differences. The table summarizes.

Android has long permitted sideloading, where a user enables installing apps from a given source outside Google Play, and Google Play Protect provides on-device scanning regardless of source. iOS historically allowed only the App Store, but EU regulation opened the door to alternative app marketplaces and web distribution, with Apple applying notarization, a baseline malware-and-integrity check, rather than full App Review, to apps distributed that way. So on both platforms an app can now reach users without passing the full store review, while each platform applies a lighter baseline check and continues to offer integrity signals and code signing. The practical upshot is that distribution is more open, but the platform protections that do not depend on store review, signing, attestation, and on-device scanning, become relatively more important for both users and developers.

What does sideloading change for security?

It removes the assumption that every installed copy passed full store review and came through one trusted channel. When apps can be installed from outside the official store, users face a higher chance of encountering malware or tampered apps, since the full review gate is bypassed, even though baseline checks like notarization and Play Protect catch some of it. For you as a developer, the key change is that your app, or a modified version of it, can circulate through channels you do not control, so a repackaged or trojanized copy of your app could be distributed on an alternative store or by direct sideload. That raises the importance of the binary-protection and integrity concerns: a tampered copy is more likely to exist, and you cannot assume a running instance came from the official store and is unmodified. It also means installation-source and integrity signals carry more weight, since they let you, server-side, distinguish a genuine, properly distributed copy of your app from a tampered or repackaged one. Sideloading does not make apps insecure, but it shifts trust away from a single review gate toward signing, attestation, and verification.

How do you protect your app?

Lean on signing and integrity verification, and assume copies may circulate. Sign your app properly so the platform can verify its origin and integrity, and rely on the platform's signing as a baseline. Use the platform integrity signals, Play Integrity on Android, App Attest and DeviceCheck on iOS, and verify them on your server, so you can confirm a running instance is a genuine, unmodified copy of your app and, where the signal supports it, judge how it was obtained, rather than trusting the client's word. Apply the binary-protection practices that matter more when repackaging is likelier, not hardcoding secrets, enforcing security-critical decisions server-side, and adding obfuscation and tamper detection as defense in depth, recognizing they raise the cost rather than guarantee. If you distribute through an alternative marketplace, follow that channel's and the platform's requirements, including notarization on iOS. The principle is that with distribution more open, you cannot assume every copy came through full review unmodified, so verify integrity and legitimacy with signing and server-verified attestation, and keep anything that must stay secure off the client.

What to watch out for

The first trap is assuming every running copy of your app came through the official store unmodified, when sideloading and alternative marketplaces mean repackaged copies can circulate; verify integrity with server-checked attestation. The second is leaving secrets in the binary or enforcing critical logic client-side, which is riskier when tampered copies are likelier; keep secrets off the device and enforce server-side. The third is ignoring the baseline checks and signing that carry more weight now. A pre-submission scan such as PTKD.com (https://ptkd.com), which reads the compiled app against OWASP MASVS, surfaces hardcoded secrets and your app's resilience posture, helping you harden the fundamentals that matter more outside the store, while integrity verification is yours to implement server-side.

What to take away

• Sideloading and alternative app marketplaces let apps reach users outside the official store, long on Android and now in the EU on iOS, bypassing full store review while baseline checks like notarization and Play Protect still apply.
• The change shifts trust from a single review gate toward signing, attestation, and verification, and raises the chance that repackaged copies of your app circulate.
• Protect your app by signing it properly, verifying platform integrity signals server-side, keeping secrets off the client and enforcing critical logic server-side, and following alternative-distribution requirements.
• Use a pre-submission scan such as PTKD.com to surface hardcoded secrets and resilience gaps, hardening the fundamentals that matter more when apps are distributed outside the store.