One codebase, real store app
The Android app loads your published Create URL inside a native WebView. There is no second project to maintain and no code export.
Create → Google Play
Your Create app already runs in the browser. WebViewGold wraps the published URL in a native Android app shell, adds push notifications and other native features, and comes with a Google Play approval guarantee. You keep building in Create; every publish updates the app instantly.
The Android app loads your published Create URL inside a native WebView. There is no second project to maintain and no code export.
Publish again and the app updates instantly. Only changes to the native shell itself (icon, new native feature) need a store update.
Push notifications, offline screen, native sharing, biometric login, QR scanner, in-app purchases and deep links are single settings or one-line JavaScript calls.
Google Play Store approval guarantee – or your money back within 14 days. 96.4% of all WebViewGold apps get approved by the review teams on the first attempt.
Seven steps, no coding. Most people finish the native part in under an hour.
Use Publish inside Create to put the current version on a public created.app address. Publish again whenever you want changes to go live. The editor preview is not a public URL. Publish first and use the published address in the app. Custom domain: Add your own domain in the project settings and set the DNS records as instructed. See why a custom domain before submission is worth it.
Add a privacy policy page, an account deletion option (if users can sign up), and remove builder badges or "download our app" banners. Run the free Play Store readiness check on your URL: it flags mixed content, missing viewport tags, builder preview domains and other blockers in seconds.
One-time payment, free updates. You receive the ready-made Android Studio project, or activate the WebViewGold Cloud Builder and skip the IDE entirely.
Open Config.java (or the Cloud Builder form), paste your published URL, set the app name, choose your package name, upload the icon and pick the splash screen. No coding needed.
Enable push notifications, the offline screen, pull-to-refresh, biometric login, the QR scanner or App Links with single settings. Everything is optional.
In Android Studio: Build → Generate Signed Bundle. In the Cloud Builder: click Build and the signed .aab is prepared and uploaded for you.
Create the app in the Play Console, fill in the store listing, upload icon, feature graphic and screenshots, complete Data safety, content rating and app access.
New personal accounts run a 14-day closed test with 12 testers first. Then promote the release to production and submit for review. Our approval guarantee covers you.
These are the points that come up most often with Create projects (React front ends generated by Create with built-in database, auth and integrations).
Paste this into Create and let it apply the changes reviewers look for. Review the result, then publish.
Prepare this app for publishing as a native iOS and Android app (it will run inside a native WebView wrapper): add /privacy and /terms pages linked from the footer; add a "Delete my account" action in settings with confirmation; make every screen responsive from 320px to tablet widths without horizontal scrolling and with 44px tap targets; remove any "Made with Create" badge, external promotional links and "Download our app" banners; show a retry message when data fails to load; set the title to the app name (max 30 characters).
Google reviews behavior, not tooling. Nobody is rejected for using Create; apps are rejected for the points below.
Google rejects apps that only wrap a website without the website owner's permission or that offer no real functionality. Wrapping your own product with added native features is fine.
Every app needs a privacy policy URL and a completed Data safety form that lists what the app and its SDKs collect.
Apps that let users create accounts must offer account deletion inside the app and via a web link you provide in the Play Console.
Personal accounts created after November 2023 must run a closed test with at least 12 testers for 14 continuous days before they can request production access.
New apps must target a recent Android version. WebViewGold updates keep the template current; just build with the latest version.
Digital goods and subscriptions sold in the app generally must use Google Play Billing (WebViewGold supports RevenueCat). Physical goods and services may use other payment methods.
Every feature is optional and documented step by step in the WebViewGold for Android documentation.
Remote push via OneSignal or Pushwoosh, local scheduled pushes via a JavaScript call.
Documentationhttps links to your domain and custom schemes open directly in the app.
DocumentationGoogle Play subscriptions and one-time purchases via RevenueCat, triggered from your web app.
DocumentationA native "Try again" screen when the user is offline, or a local HTML fallback.
DocumentationMinimum and maximum splash duration with fade-out, or a native spinner while loading.
DocumentationFingerprint / face unlock gate from a JavaScript call.
DocumentationNative scanner that returns the result to your web app.
DocumentationShare intent and haptic feedback from your web app.
DocumentationHide website-only elements and inject code when loaded inside the app.
DocumentationNative file picker and camera for your upload forms.
DocumentationTick these off and the review is a formality. The free readiness check verifies the technical half automatically.
Yes. Publish the app in Create, insert the published URL into WebViewGold and submit the native build. The app keeps loading your Create project, so updates stay instant.
No. WebViewGold works with the published URL; you never export code.
Either Android Studio (free, runs on Windows, macOS and Linux) or the WebViewGold Cloud Builder, which builds and uploads the signed App Bundle from your browser.
Google requires personal developer accounts created after November 2023 to run a closed test with at least 12 opted-in testers for 14 continuous days before the first production release. Friends, colleagues or a Discord community are enough; organization accounts are exempt.
Google names the policy in question and you can fix and resubmit. WebViewGold comes with a Google Play approval guarantee: if Google rejects the app for a non-content reason, you get your money back within 14 days of purchase.
No. The app loads your published URL, so content and feature changes you publish in Create are live in the app immediately. A new store version is only needed when the native shell changes, for example a new app icon or an added native feature.
$109 one-time for WebViewGold for Android (free updates) plus the Google Play Console developer account ($25 one-time). Optional: the Cloud Builder add-on if you want to build in the browser, or the Full Service package where our team configures, builds and submits the app for you.
Google Play Store approval guarantee – or your money back within 14 days
Prefer to hand it over? Full Service: we configure, build and submit for $349. Questions? Chat with us 24/7.
Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.