Keep your signing key. Keep control of your app.
For a normal app update, keep the same Android package identity and signing key, and increase the version code.
Create and protect your key
The key is created in your browser. Choose a password of at least 10 characters, download its encrypted backup, and keep the password somewhere separate. The current importer accepts Web2Apk encrypted key backups, not JKS or P12.
Unlock a saved key
Open Build and enter its password to unlock the encrypted backup stored in this browser. If you changed devices, import the key backup or a project backup that contains it. A project export includes only the encrypted key, never its password.
Make an update
Keep the package name unchanged, restore the original signing key, save your changes, and build. Version codes are tracked locally across projects with the same package name. If your backup is old or you released builds elsewhere, set the minimum version code above the latest published value.
Changing identity
A different package name creates a separate app. A different signing key with the same package name does not normally update the installed app. Uninstalling can remove the app's saved data. Store-managed signing and key-upgrade processes have separate rules.
Backups and build snapshots
Each build uses a fixed saved configuration. Later edits do not modify older packages. Export project backups before clearing browser data. Workspace backups do not contain historical APK/AAB binaries, so download those separately.