Signing guide

Sign every build with the key your users already trust

Android and iOS only install apps that carry a valid signature. This guide explains why, then shows how to add a signing credential to html2app and assign it to a project.

iOS builds are planned and not available yet. Android builds are live now.

01 Why signing

A signature tells devices and stores who sent the app

Your build is only a bundle of files until a key signs it. The signature does two jobs: it proves the author, and it proves the file was not changed after signing.

  1. Your web app HTML, CSS and JS
  2. Build html2app wraps it in a native shell
  3. Sign Your keystore or certificate signs it
  4. Check Store and device verify the signature

Signed and verified. The device accepts the install.

Updates need the same key

An installed app accepts an update only when the new build has the same signature. Changing the key blocks the update.

Tampering is detected

Any change to a signed file breaks its signature, so the store and the device reject the file.

Keys are yours to protect

Whoever holds the key can publish updates as you. Store the keystore and its passwords in a safe place.

02 Android and iOS

Each platform signs with different files

Android

Keystore

  • A keystore file (.jks, .keystore, .p12 or .pfx) holds your signing key.
  • Each keystore entry has an alias and a password.
  • Used for two build types: Signed APK for direct install, and App Bundle (.aab) for Google Play.
  • Google Play App Signing lets you keep an upload key while Google signs the installed app.

iOS (planned)

Certificate and provisioning profile

  • A .p12 certificate holds the signing identity.
  • A .mobileprovision profile links the certificate, your App ID and, for Ad Hoc, the allowed devices.
  • Used for two build types: Ad Hoc for a limited device list, and App Store for review and release.
  • An Apple Developer account is required ($99 per year).

03 In html2app

Add a signing credential to html2app

Credentials live in two places. The credentials page stores them, and each project chooses which one to use for each platform and build type.

  1. 1

    Upload the credential

    Open app.html2app.dev/credentials. Upload your Android keystore, or your iOS certificate and provisioning profile, then enter its details and passwords.

  2. 2

    Open the project settings

    Open your project, then go to its settings page.

  3. 3

    Assign a credential per platform

    Under Signing Credentials, pick a credential for each platform and method, then select Save Settings.

  4. 4

    Build

    Start a build. html2app signs the output with the credential you assigned for that method.

Signing Credentials
Android / Signed APK None
Android / App Bundle None
iOS / Ad Hoc planned None
iOS / App Store planned None

Example only. The names of your credentials will differ.

Stored credentials are encrypted. You can delete them from the credentials page at any time. Under the current terms, stored credentials expire after one year. See the Terms of Service.

04 Video

Watch the walkthrough

TODO: embed the YouTube video here.

05 Keep your keys safe

Back up before you upload

Back up the keystore

Keep a copy of every keystore and iOS certificate outside html2app, for example in a password manager or encrypted drive.

Save the passwords

A lost keystore password cannot be recovered. Store it with the keystore.

Or keep production keys on your machine

Build with test credentials and re-sign the download locally with your production keys. The re-signing guide covers both platforms.

06 FAQ

Common questions

Why does my Android app need to be signed?

Android installs only signed APK and AAB files. The signature proves that an update comes from the same developer as the installed app.

What happens if I lose my Android keystore?

With Google Play App Signing, you can register a new upload key with Google Play. Without that, updates signed with a different key are rejected. Keep backups.

Do I have to upload my keystore to html2app?

No. You can build with test credentials and re-sign the downloaded build locally with your production keys.

Can I build an iOS app with html2app today?

Not yet. iOS builds are planned. The iOS options appear in the app so you can prepare credentials in advance.