html2app docs

    Android App Distribution Overview

    There are three ways to distribute an Android app. Each has different costs, trust levels, and user experience implications.

    Google Play StoreAndroid Developer Console (ADC)Sideloading (Unverified)
    Cost$25 one-time$25 (full) / $0 (limited)$0
    Wait time for usersNoneNone24-hour delay (from Aug 2026)
    Trust levelPlay Protect certifiedVerified developerUnverified
    DistributionGoogle Play StoreAny alt-store, website, directAny channel
    Max installsUnlimitedUnlimited (full) / 20 devices (limited)Unlimited
    Best forPublic release on Play StoreAlt-stores, direct distributionDevelopment, testing, friends
    AvailableNowRolling out Sep 2026+Now (friction added Aug 2026)

    Google Play Store is the standard public distribution channel. Apps are Play Protect certified and users install them with no friction.

    Android Developer Console (ADC) is Google's new system for developers who distribute outside Google Play (alt-stores, your own website, etc.). It links your real identity to your app's package name and signing key, so users see you as a "verified developer." Full accounts require identity verification and a $25 fee. Limited accounts (students, hobbyists) are free but capped at 20 devices.

    Sideloading unregistered apps requires no account. Starting August 2026, users installing from unverified developers must go through Android's "Advanced Flow": enable developer mode, confirm they're acting freely, reboot the device, re-authenticate, and wait 24 hours before the install proceeds. This is a one-time setup per device. ADB installs bypass this flow entirely.

    Google Play Store

    Requirements

    Before you can publish on Google Play Store, you need:

    • Google Play Developer Account: A paid account ($25 one-time registration fee). Register at Google Play Console.
    • Keystore File: A locally generated keystore containing your signing keys (see Create Keystores).
    • Google Account: A Google account to manage your developer account.

    Note: You do not need to compile or sign your app locally. The html2app SaaS platform handles app compilation and signing for you. You only need to provide your keystore file.

    Publishing Process

    1. Create a Keystore - Generate a signing key locally (see Create Keystores)
    2. Build Your App - Compile your app and sign it with your keystore
    3. Create Play Console Account - Register as a Google Play Developer ($25 one-time)
    4. Create App Listing - Set up your app's store listing with description, screenshots, etc.
    5. Upload App Bundle - Upload your signed App Bundle (.aab) to Play Console
    6. Review & Publish - Google reviews your app and publishes it to the store

    Note: Step 2 is handled by the html2app SaaS platform. You only need to provide your keystore file, and html2app will compile and sign your app automatically.

    Android Developer Console (ADC)

    The ADC is Google's identity verification system for developers who distribute apps outside of Google Play — for example, through an alternative app store, your own website, or direct download links. It is not a store itself; it's a developer registry that links your verified identity to your app's package name and signing key.

    Rolling out globally from September 2026, apps on certified Android devices (those with Google Mobile Services) must be registered by a verified developer to install without friction.

    Source: Android developer verification · Register on Android Developer Console

    Registration Process

    1. Create an ADC Account - Sign up at Android Developer Console. Individual full accounts and organizations require identity verification ($25 fee). Limited accounts (students/hobbyists, up to 20 devices) are free with fewer requirements.
    2. Register Your Package Name - Add your app's package name (e.g. com.example.myapp) on the Package names page.
    3. Add Your Signing Key - Provide the SHA-256 fingerprint of your keystore. For new package names this is enough. For existing ones, you must also prove key ownership (steps 4–5).
    4. Build a Verification APK - ADC gives you a snippet (a unique token). Create a minimal APK with the same package name, place the snippet in assets/adi-registration.properties, and sign it with your keystore.
    5. Upload & Get Registered - Upload the signed APK to ADC. Android verifies the signature and marks your package as Registered.

    Note: html2app handles building and signing. To complete ADC registration, a verification build is required with the ADC snippet placed at app/src/main/assets/adi-registration.properties in the Android project. Support for providing this file through html2app is planned and will be added in a future update.

    Sideloading

    Sideloading means distributing your APK directly — via a website, file share, or any channel — without going through a store or registering with ADC. No account or fee is required.

    Starting August 2026, users installing apps from unverified developers on certified Android devices must complete a one-time "Advanced Flow" per device:

    1. Enable developer mode on the device
    2. Confirm they are acting without outside pressure
    3. Reboot the device and re-authenticate
    4. Wait 24 hours before the install can proceed

    This friction is intentional — it's designed to disrupt scams that rely on urgency. ADB installs bypass this flow entirely, so sideloading during development is unaffected.

    Sideloading is suitable for development builds, internal testing, or sharing with a small group of trusted users who understand the process.

    Read the official Google post: Android developer verification: Balancing openness and choice with safety

    Next Steps

    1. Understand App Signing & Keystores - Read App Signing & Keystores to learn more about how signing works
    2. Create Your Keystore - Follow Create Keystores for step-by-step instructions