Skip to content

Google Play

Export a generated app as a Play-ready signed AAB. Open it from ⋮ → Google Play.

Which apps can be published

Almost all of them. The generated APK's low targetSdk is an APK-packaging detail and never reaches Play — you upload the AAB, and the exporter gives it a Play-compliant targetSdk (currently 36).

App typePlay AAB
Web · Multi-Web · HTML · Offline Pack · Frontend · Media · GallerySupported
Node.js · PHP · Python · Go · WordPressNot supported
Any type with resource encryption enabledNot supported

Why server-runtime apps are excluded. They need targetSdk 28 to fork+exec their bundled runtimes from app storage, and Play requires a target level that turns on W^X — which blocks exactly that. Converting one would produce a bundle whose app can never start its own server, so AAB export is refused outright rather than silently degraded. Distribute those as APKs instead: sideload, enterprise, or any store that accepts targetSdk 28. Nothing else about them is limited.

A Multi-Web app is always publishable. Server-runtime apps cannot be embedded as multi-web sites in the first place — their runtimes are not packaged into a multi-web APK — so such a site falls back to its URL at export and the app never runs one.

AAB export

One tap runs the full pipeline, with visible stages:

  1. Building APK — assemble the APK on demand.
  2. Assembling — convert to AAB.
  3. Signing — sign the bundle.
  4. Signed — done; ready to share or upload.
  • targetSdk rewrite — the AAB's targetSdk is rewritten to the Play-required level (currently 36).
  • Metadata — protobuf metadata is generated locally.
  • Cancellable — stop mid-build.
  • App count — see how many apps are eligible.

Keystore

Create, import, and manage the signing keys used for the AAB.

Notes

  • You can also launch AAB export for a specific app from its Build APK dialog.
  • The generated APK keeps targetSdk 28 by default (required for fork+exec runtimes); only the AAB is rewritten for Play. WebView-only app types can optionally raise the standalone APK's targetSdk from the APK export section; see Build APK.
  • A pre-upload advisory and warning are shown before exporting.

Released under the Unlicense.