Skip to main content
Publish your app to Google Play, the App Store, or Microsoft Store, or distribute it as a PWA. Hercules builds your Android and iOS apps, keeps the signing keys for you, and submits iOS builds to App Review.

​
How do I publish my app to the App Store?

Hercules builds your Android app for you. Upload the first release by hand, then Hercules can send every later build to Google Play on its own.
Hercules builds are rolling out gradually. If you do not see a Build Android App button, use the manual steps at the bottom of this tab.
1

Publish Your App on Hercules

Click Publish in the top right corner to get your app URL. Your Android app loads this URL, so publish before you build.
Publish an app in Hercules
2

Set Your App Details

Click Mobile → Publish to App Store, then fill in:
  • App name: the name shown under your icon on the phone
  • Package name: a permanent ID for your app, like app.hercules.myapp
  • App icon: a square PNG at least 512x512px with no transparency
  • Android device permissions: turn on Camera or Microphone if your app uses them
New Android builds require Android 7 or later (API 24). Android 6 devices cannot install or update to these builds; existing installed versions are unchanged. This meets Google Play automatic protection’s minimum-version requirement but does not enable protection.
You cannot change the package name after your first release. Google ties your store listing to it permanently.
3

Build Your App

Click Build Android App. Progress appears live underneath, so you can watch each step.The first build is the slow one, because Hercules installs the Android build tools before it starts. Later builds skip that step.When it finishes, click Download to get your .aab file (the app package Google Play accepts).
4

Upload Your First Release by Hand

Google requires the first release of a new app to be uploaded manually.
  1. Go to Google Play Console. You need a Google Play Developer account ($25 one time)
  2. Click Create app and fill in your app name, language, and type
  3. Click Testing → Internal testing → Create new release
  4. Upload your .aab file. Your package name is inside it, so Play picks it up from the upload
  5. Complete the required forms: privacy policy, data safety, content rating, and target audience
  6. Add your own email as a tester, then install the app from the opt in link on your phone
The forms take longer than the build. Google will not release your app until every one is complete.
5

Connect Google Play for Automatic Uploads

Do this once, and Hercules sends every later build straight to Google Play.
  1. In Google Cloud, create a service account (a robot account that acts on your behalf) and download its JSON key
  2. In Play Console, click Users and permissions → Invite new users, invite the service account email, and give it permission to release your app
  3. In Hercules, click Mobile → Publish to App Store and add the JSON key as a Google Play credential
  4. Attach that credential to your app
Your next build uploads itself to internal testing.
6

Go Live

When your test build looks right, open Play Console and promote the release from Internal testing to Production. Review usually takes a few hours to 2 days.
Hercules creates your app signing key and reuses it for every build, so there are no keystore files for you to save. Keep your mobile settings in place: your key lives with them.
Use this if Hercules builds are not available for your app yet.
1

Generate Android Package with PWA Builder

  1. Go to pwabuilder.com
  2. Enter your app URL (e.g. https://my-app.onhercules.app or your custom domain)
  3. Click “Start”, then “Package for stores”
  4. Select “Android” and download the AAB file
Save signing.keystore and signing-key-info.txt somewhere safe. You must use the same signing key for all future updates. If you lose these files, you cannot update your app.
2

Set Up Digital Asset Links

PWA Builder wraps your app in a browser window, so Google Play needs a Digital Asset Links file to confirm you own your domain. Without it, your app opens with a browser address bar instead of running full screen.
  1. On the PWA Builder Android package screen, copy the assetlinks.json snippet it generates (it includes your package name and SHA256 fingerprint, a unique ID tied to your signing key)
  2. Ask Hercules to add it to your app:
Add Digital Asset Links file
  1. Publish your app again so the file goes live
  2. Visit https://my-app.onhercules.app/.well-known/assetlinks.json (or your custom domain). It should return the JSON you pasted, not your app’s page
If you regenerate your signing key or change your package name, update this file and publish again. If you enroll in Google Play App Signing (the default for new apps), Google re-signs your app with its own key: get the new fingerprint from Play Console → Setup → App integrity and update this file with it.
3

Submit to Google Play

  1. Go to Google Play Console
  2. Click “Create app” and fill in details
  3. Click Production → Create new release
  4. Upload the AAB file and complete your store listing
  5. Submit for review

​
How do I let my Android app use the camera or microphone?

Turn the permission on before you build. Click Mobile → App settings, switch on Camera or Microphone under Android device permissions, then build the Android app again and send that build to Google Play. An Android app can only reach the camera or the microphone if the build declares the permission, so a page that works in Chrome shows nothing in the installed app until you do this. The phone still asks the person for the permission the first time your app uses it.
Turning a permission on changes nothing else about your app. The package name and the signing key stay the same, so the new build goes out as an update to the app you already published. Builds already on the store keep the permissions they were built with, which is why a rebuild is needed.

​
FAQ

Common reasons: crashes/bugs, incomplete features, misleading descriptions, or being too similar to a website. Apple wants apps that provide value beyond what Safari offers. Add native features or unique functionality.
Common reasons: policy violations, inappropriate content, broken functionality, or missing privacy policy. Google is generally more lenient with PWAs than Apple.
  • Google Play: Usually hours to 2 days
  • App Store: Usually 1-3 days
  • Microsoft Store: Usually 1-3 days
First submissions may take longer.
Yes. Each store needs its own package, but the underlying app is the same one. Hercules builds your Android package. For other stores, use PWA Builder.
This affects apps packaged manually with PWA Builder. Your Digital Asset Links file (assetlinks.json) is missing, or does not match your signing key. See the Set Up Digital Asset Links step in the manual section of the Google Play tab above. Apps built by Hercules run full screen without this file.
Not for apps built by Hercules. Hercules creates the key, stores it securely, and reuses it for every build.If you package manually with PWA Builder, save your signing key somewhere safe. Google will not accept an update signed with a different key. You would have to publish as a new app with a new package name, losing your existing users and reviews.
PWAs can cache content for offline use. Ask Hercules to set up a service worker to cache assets and handle offline scenarios gracefully.
PWAs are faster to ship (no review process), update instantly (no waiting for approval), work on all platforms, and don’t require developer accounts. PWAs are downloaded directly from the browser, as opposed to a store. You will have to create a PWA to create a mobile app anyway. We recommend testing with a PWA and then publishing to the app stores when you are ready.