Questions,
answered

We package your public website inside a reviewed Android app template, then apply your app name, icon, splash screen, navigation rules and selected native features during a cloud build.

No. The builder is a guided, step-by-step form. You pick the experience; the platform prepares the Android project and runs the build for you.

Public HTTPS websites with a mobile-friendly layout work best. We run a compatibility check first, but you should still test logins, payments and file uploads inside the test APK.

Google Play only accepts apps of websites the publisher owns or is allowed to use. Add a meta tag, a small file or a DNS record to your site, then press Verify. We check again before every build.

An APK is an Android package you can install directly on a phone for testing or private distribution.

An APK installs directly on a phone — use it to test and share. An AAB (Android App Bundle) is the format Google Play requires; it can't be installed directly. Pro and Business plans can build both, signed with your app's own key.

Your configuration is kept, and failed builds don't count toward your daily build limit. Open the build to see what went wrong, fix it and build again.

Every app is now signed with its own permanent key so it can update in place. Builds made before this change used a temporary key, so Android won't update them. Uninstall the old version once; after that, updates install normally.

Content changes on your website appear in the app immediately. Changes to the icon, name or native features need a new build. With the OTA update prompt, installed apps tell people when a new build is ready.

Turn on push notifications, choose Web2Mobile push (no setup) or your own Firebase project, then build your app. Afterwards you can send notifications from the Push section of your app.

Google, Facebook and Apple block sign-in inside apps that show websites. Your app opens those sign-in pages in a secure browser tab instead. Offering email sign-in on your website gives the smoothest experience.

Choose a link scheme like yourbrand:// and links such as yourbrand://shop open that page in your app. To open normal links to your website in the app, upload the assetlinks.json file we generate to your website.

Yes. On Pro or Business, choose AAB as the build output and upload the file in the Google Play Console. Use the key we generate for your app, or upload the keystore you already use on Google Play (app → Signing). We never promise store approval; Google reviews every app.

Yes. Every plan includes monthly builds. You will always see your remaining builds before you start one.

Cancel any time from Billing. Your plan stays active until the end of the paid period.