Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main pageWhat "broken functionality" means to Google
The minimum functionality policy includes a simple expectation: the app installs, opens, loads its content and lets the user do what the listing promises, without crashing, freezing or showing empty screens. Reviewers test on physical devices and on several Android versions. In addition, every upload to a testing track generates a pre-launch report in Play Console, where automated crawlers tap through the app on a set of devices and record crashes, errors, security warnings and accessibility problems.
For a wrapped app the WebView is the whole user interface, so anything that stops the page from rendering looks like a dead app: a preview URL that went to sleep, an http:// image on an https:// page, a certificate problem, a JavaScript bundle that an older System WebView cannot parse, or a bot-protection challenge that never completes.
Symptom, cause, fix
| Symptom | Usual cause | Fix |
|---|---|---|
| White screen after the splash | URL unreachable: Lovable or Bolt preview URL, Replit deployment sleeping, DNS of a new custom domain not propagated | Publish to a production custom domain first; see the custom domain guide. Keep ACTIVATE_PROGRESS_BAR on so loading is visible |
| Page loads, images or API calls missing | Mixed content: http:// resources inside an https:// page, blocked by the WebView | Serve everything over HTTPS; switch cleartext traffic off in the Android project as described in the WebViewGold support center |
| Certificate error or empty page on some devices | Expired, self-signed or incomplete certificate chain | Fix the certificate at your host; set BLOCK_SELF_SIGNED_AND_FAULTY_SSL_CERTS to true so the pre-launch report does not flag an unsafe SSL error handler |
| Crash at launch | Ads enabled without a valid AdMob app ID in strings.xml, or push enabled without the matching google-services.json or OneSignal app ID | Either enter the IDs or set SHOW_BANNER_AD, SHOW_FULL_SCREEN_AD, PUSH_ENABLED or FIREBASE_PUSH_ENABLED to false |
| Back button closes the app | EXIT_APP_BY_BACK_BUTTON_ALWAYS set to true, or a single-page app that never pushes history entries | Set it to false, keep EXIT_APP_BY_BACK_BUTTON_HOMEPAGE with EXIT_APP_DIALOG for a confirmation prompt, and make your router push real history entries |
| User logged out at every start | CLEAR_CACHE_ON_STARTUP true clears cookies and session storage | Set it to false for apps with a login |
| "Browser not supported" or endless challenge page | Bot protection or a user-agent check on your host or in your auth provider | Allow the app's user agent in your protection rules or set a custom USER_AGENT; for Google sign-in see the disallowed_useragent fix |
Use the pre-launch report before Google does
The report is free, runs on every testing-track upload and shows you what the reviewer will see.
Upload to internal testing
Create an internal testing release with your signed bundle. The pre-launch report starts automatically and takes a while to finish.
Read the four tabs
Stability (crashes and ANRs with stack traces), Performance, Accessibility and Security. For a WebView app the stability and security tabs matter most; a crash stack trace that mentions ads, Firebase or OneSignal points straight to a missing ID.
Watch the recordings
The report includes screen recordings of the crawler. A recording that stays on a white screen or a cookie banner tells you what to fix without guessing.
Reproduce on a real device
Install from the internal testing link, test with Wi-Fi, mobile data and airplane mode. Airplane mode must show the native offline screen (enable
FALLBACK_USE_LOCAL_HTML_FOLDER_IF_OFFLINEand ship a small local-html page), not a browser error.Check Logcat for the real error
In Android Studio, run the app on an emulator and filter Logcat for your package name. WebView errors such as blocked mixed content, certificate failures and JavaScript exceptions appear there with the exact URL.
Fix, rebuild, re-upload
Bump the version code and upload again. Wait for a clean report before promoting the release to production.
WebViewGold has allowed us the shortest and most efficient time-to-market ever possible from among all the other app platforms we have ever tried during the past 5 years. I don’t know why I hadn’t discovered you sooner, but I am really, really glad I did. Currently nearing 6000 app downloads on both iOS App Store & Google Play Store without any problem!
Android System WebView: what you cannot control and what you can
WebViewGold renders your site with the Android System WebView, a Chromium component that Google updates through Play independently of the OS. Most devices run a recent version; some older or locked-down devices do not, and a JavaScript bundle that uses very new syntax then fails to parse and leaves a blank page. You cannot update the user's WebView, but you can keep your build target reasonable: ask your builder to transpile for a browserslist that includes a few older Chrome versions, avoid depending on brand-new CSS features for layout, and show a visible error if your app's bootstrap script fails instead of a silent white page. The website setup guide lists the practices that make a site behave well inside the app.
Launch-day stability checklist
- Production URL on a custom domain, HTTPS everywhere, valid certificate chain.
- Every enabled feature has its IDs (AdMob, OneSignal, Firebase); unused features are set to false.
- Splash screen plus loading indicator so a slow first request never looks dead.
- Offline fallback enabled and tested in airplane mode; the Reconnect API wired to a "Try again" button.
- Back button walks back through the web history and asks before exiting on the home page.
- Pre-launch report clean on stability and security; recordings show real content.
- Crashlytics (
TRACKING_EVENT) on with a consent step, so you see production crashes.
Frequently asked questions
The app works on my phone but the pre-launch report shows a white screen. Why?
The crawler runs on different devices, often with a fresh profile and no cookies. Typical reasons are a cookie banner or login wall that the crawler cannot pass, a URL that only works for logged-in users, or mixed content blocked on a stricter configuration. Watch the recording to see which.
Does a warning in the pre-launch report block the release?
Warnings do not block, but security warnings about SSL handling and crashes are the things reviewers look at. Fix them before production.
Should the back button ever close the app?
On the home page, after a confirmation, is the expected behavior on Android. Anywhere else it should navigate back in the web history, which WebViewGold does by default.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Cloud Builder
$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demoFull Service
$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.