Documentation
Everything about taking your web app from a URL to the Play Store.
How it works
Mexbui analyses your deployed web app, generates a real Android project around it, and compiles that project with the official Android toolchain (Gradle + Android SDK) on a clean cloud build machine.
The output is a genuine signed APK for direct installation and an AAB for Google Play — the same artefacts you would get from Android Studio.
Configuration reference
App name is what appears under the launcher icon. Package ID is the permanent identity of your app on Google Play and can never change after your first upload.
Version name is human readable (1.0.4). Version code is an integer that must increase for every Play upload. Orientation, fullscreen and the offline screen control runtime behaviour.
Google Sign-In
If your web app already uses Google Sign-In, nothing on your website changes. The generated Android app opens authentication URLs in a Chrome Custom Tab, which is the flow Google requires, and deep-links the user back into the app when it completes.
Register the app package ID and the SHA-1 fingerprint of your signing key in your Google Cloud console so Google trusts the app.
Publishing to Google Play
Create an app in the Google Play Console, upload the AAB to a testing or production track, complete the store listing and content declarations, then submit for review.
Keep your signing keystore backed up. Google Play permanently ties your listing to the key used for the first upload.
Something missing? Ask us.