Docs
Android application ID & signing
Choose an application ID and decide between the platform default keystore or your own JKS.
Showing example IDs - open this guide from your app dashboard to pre-fill yours.
Application ID
Your Android application ID is a reverse-DNS package name. Example for this app: com.example.app
- Must be unique on Google Play
- Cannot be changed after you publish
- Format like
com.company.app(letters, digits, underscores; each segment starts with a letter)
Platform default keystore
For getting started, WebsiteTo.app can sign production builds with a shared platform keystore. This is fine for testing and early releases.
If you plan to transfer the app to another Play Console or keep full ownership of the signing key, upload your own JKS instead.
Custom keystore (optional)
- Generate a keystore locally (or use an existing Play App Signing upload key)
- In WebsiteTo.app → Configure → Android, enable Use custom keystore
- Upload the
.jks/.keystorefile and enter keystore password, key alias, and key password - Save, then request a production build
On the first production Android build, the wizard asks you to confirm default vs custom signing. Later rebuilds skip that step — change signing anytime on the Android configure page.