PWA2APP Documentation
FR Back to the site Start for free

Quick start

This journey takes you from sign-up to a test APK you can install on an Android phone. Allow for the time of the analysis and the first build, which varies with your site.

1. Create your account

  1. Sign up with your e-mail address, then confirm it with the link you receive.
  2. Enable two-factor authentication (TOTP app or passkey): it is recommended.

2. Create an application

  1. In Applications, create an application with its name and the REMOTE mode.
  2. Add the source: your PWA's https address.

3. Run the analysis

  1. Start the analysis and wait for its result. It needs an active analysis worker.
  2. Read the report: a BLOCKER finding must be fixed before going further.

Risks detected according to the technical rules currently configured. Publication remains subject to Apple's and Google's review, and their rules evolve.

4. Configure

  1. General and Android: enter the package name (e.g. com.mycompany.myapp).
  2. Appearance: colors, orientation and, if needed, the app icon (square PNG, JPEG or WebP of at least 512 px).
  3. Bridge and plugins: enable the native features your PWA needs.

5. Build and download

  1. In Versions, create a version (e.g. 1.0.0).
  2. In Builds, start a build with the Debug variant and the APK output. A build worker must be active.
  3. When the status is "Succeeded", open the build and download the APK from the Artifacts tab.
  4. Install the APK on an Android phone (allow unknown sources if needed).

About Google Play Protect warnings

When a Debug APK downloaded outside Google Play is installed for the first time, Play Protect may say it has not seen this app or developer before. This is a low-reputation signal (an “uncommon app” warning), not a malware verdict. It does not guarantee that the APK is safe either.

Before installing, check that the APK came from your PWA2APP build and that its app name and package match your project. If Play Protect offers to send the app for scanning, wait for the result; do not install a file from an unknown source.

To share a test build with others, use a signed RELEASE build and, where possible, Google Play’s internal testing track.

What next?

  • For a production version, verify your PWA's domain then sign with an Android key: see the Android signing guide.
  • If a build fails, see the guide on fixing a failed build.