Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

Native feature

Version check and force update for vibe-coded apps

Web changes ship instantly, native changes do not. Per-builder guides for a version rule in your backend, a gate that fails open and store links that open the right app.

From $109 one-time per platform, or let our team do it all from $698.

  • Approval guarantee – or money back within 14 days
  • No coding needed
  • One-time payment, free updates
  • 24/7 human support
  • Made in Germany since 2014 · ISO 27001

When an old app version actually hurts

Web deploys reach every installed version on the next page load. Only changes to the native shell leave users behind, and these are the three that matter:

A web feature needs a newer shell

You switch on in-app purchases, biometric login or a new push provider in version 1.3. Users on 1.2 see the button, but the URL scheme behind it does nothing in their build. Hide or replace the feature for older versions.

The old build loads a URL you are retiring

The start URL is compiled into the app. Moving from a builder subdomain to your own domain, or to a new host, leaves old installs on the old address. Keep it redirecting, and use the version check to move people to the new build.

A breaking change in backend or login

You change auth providers, OAuth redirect domains or link handling, and only the new build has the matching native settings (login helper, Universal Links, URL lists). An update screen is kinder than a login that silently fails.

How the WebViewGold version check works

The native side only reports the version; the rule lives in your backend.

  1. Expose the version to your web app

    Set autoInjectVariable to true in Config.swift and AUTO_INJECT_VARIABLES to true in Config.java. WebViewGold then provides versionNumber (the version users see, such as 1.4.0) and bundleNumber (the build number) as JavaScript variables. Without auto-injection, navigate to getappversion:// once and read the same variables.

  2. Publish a version rule from your backend

    Store the minimum supported version and the latest version per platform in your backend: a small table, a JSON file or a remote config entry. Changing the rule then needs no store release, ideally not even a deploy.

  3. Compare numerically, not as text

    As strings, "1.10.0" sorts before "1.9.0". Split on the dots and compare each part as a number, or compare build numbers if you keep them plain increasing integers.

  4. Nudge or block

    Below the latest version: a dismissible banner. Below the minimum: a full-screen "Update required" page with one button to the store listing. In a normal browser, or when the version is unknown, show nothing.

  5. Open the store app, not a store web page

    Link to https://apps.apple.com/app/idYOUR_APPLE_ID and https://play.google.com/store/apps/details?id=your.package.name, and add apps.apple.com and play.google.com to the hosts that always leave the app (safariwhitelist on iOS, BROWSER_WHITELIST on Android), so the system opens the App Store or Play Store instead of a web page inside the WebView.

Frequently asked questions

Does WebViewGold force updates on its own?

No. WebViewGold tells your web app which version is installed (getappversion:// or the auto-injected versionNumber and bundleNumber variables). The decision and the update screen live in your web app, so you can change the rule at any time without a store release.

Do I need forced updates if my web app updates instantly?

Usually not. Most changes reach every user on the next page load. A version check matters for native changes: new native features, a new start URL or domain, changed link handling or login settings. Many apps only ever need the soft banner.

Do Apple and Google allow an update screen?

Neither store forbids asking users to update, and many large apps do it. Make sure the build under review is never blocked, explain honestly why the update is needed and link only to your own store listing.

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.

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 page

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 demo

Full 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 WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Ready to ship your app?

App Store & Google Play approval guarantee – or your money back within 14 days

Rather hand it over? Full Service: we configure, build and deliver within 72 hours, from $698 per platform. 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.