Claude Code
The WebViewGold projects are ordinary Xcode and Android Studio projects, and their configuration is a pair of readable files. That means Claude Code can set your URL, app name, features and permission texts for you, as long as you draw a clear line around signing. This guide draws that line and shows the prompts.
From $109 one-time per platform, or let our team do it all from $698.
WebViewGold for iOS is configured in Config.swift; WebViewGold for Android in Config.java. Each is a list of documented constants: the URL, user agent, feature switches, colors and texts. Next to them sit the files Apple and Google read: Info.plist (iOS permission texts, display name, URL schemes) and AndroidManifest.xml (Android permissions, intent filters for App Links). The iOS setup documentation and the Android setup documentation describe every option, and the same text is in llms-full.txt for the agent.
Open Claude Code inside the unzipped WebViewGold folder (or add it to your workspace next to the web project) and let it read the configuration files before you ask for changes. It will then recognize the option names instead of guessing.
One prompt per step keeps diffs reviewable.
iOS: host ("app.example.com") and webviewurl (the full URL). Android: HOST and HOME_URL. Use the production domain; the URL is compiled into the binary.
iOS: Product Name in the build settings and Bundle Display Name in Info.plist; the bundle ID in Signing & Capabilities for the app target and every extension target (the OneSignal extension must use the main bundle ID as prefix). Android: app_name in strings.xml and the package name (default com.webviewgold.myappname) renamed through Android Studio. Choose identifiers once; see why they cannot change later.
useragent_iphone and useragent_ipad in Config.swift, USER_AGENT in Config.java: a normal mobile user agent string plus the token your web app detects (for example WebViewGoldApp).
Push (kPushEnabled + oneSignalID; PUSH_ENABLED + IDs in build.gradle), prompt timing (askforpushpermissionatfirstrun; requirePush), Social Login Helper triggers, RevenueCat keys, pulltorefresh, autoInjectVariable / AUTO_INJECT_VARIABLES, deep links (ShowExternalLink; IS_DEEP_LINKING_ENABLED).
Info.plist: customize the usage descriptions your app needs (camera, photos, location, Face ID) and delete the ones it does not, but keep the Privacy - Tracking Usage Description key, which the project requires. AndroidManifest.xml and Config.java: set requireLocation, requireCamera, requireStorage, requireRecordAudio to false for unused APIs and remove the matching manifest entries.
Replace the icon image set and the splash image; Claude Code can generate the sizes with a script from one 1024 px source. Details in the icon and splash guide.
This folder contains the WebViewGold iOS project (Config.swift, Info.plist) or Android project (Config.java, AndroidManifest.xml, strings.xml). Read the configuration files first and keep every option you do not touch exactly as it is. Apply these settings: - Web app URL: https://app.example.com (host app.example.com) - App name: Example App - Custom user agent: the default mobile user agent of the platform followed by a space and the token WebViewGoldApp - Push: OneSignal enabled with App ID [paste], do not ask for permission on first run (we call registerpush:// from the web app) - Social Login Helper: Google triggers for https://accounts.google.com - RevenueCat: API key [paste], project ID [paste] - Pull to refresh on; auto-inject JavaScript variables on - Deep links to our domain enabled - Permissions: the app uses camera (QR scanning and photo uploads) and photo library. It does NOT use location, microphone, contacts, calendar or Bluetooth: remove those usage descriptions on iOS and set the corresponding require flags to false on Android together with the manifest entries. Keep the tracking usage description key on iOS. - Write short, honest permission texts in the voice of the app. Do not change: anything under signing, provisioning, team IDs, certificates, keystore or signing configs in build.gradle, the Xcode project name, the purchase code field, dependency versions, or any file in the Pods or build folders. Do not change the bundle ID or package name; I will do that in the IDE. Show me a diff summary grouped by file and list every setting you were unsure about.
Great work! Never coded anything but managed to work with this. Easy and fast! Also with great help from the creators!
Open the project in Xcode, let it resolve packages, select a simulator and run. Check the URL loads, the splash shows, rotation and safe areas behave. Then archive and upload to TestFlight; TestFlight on a real iPhone is where push and Face ID get tested.
Sync Gradle, run on an emulator, then build a signed App Bundle with your keystore. Ask Claude Code to run a debug build from the command line via the Gradle wrapper and to fix compile errors it introduced, but do not let it touch the release signing.
The Cloud Builder takes the same settings as a form, handles bundle identifiers and signing, and uploads to App Store Connect and the Play Console. Use it if you do not own a Mac or do not want to maintain Xcode and Android Studio.
Read the diff of Config.swift and Config.java line by line once. It is short, and it is the one place where a wrong boolean (push off, cache cleared on every start) silently costs you users.
| Setting | Why it matters | Recommended |
|---|---|---|
deletecache / CLEAR_CACHE_ON_STARTUP | True logs users out on every launch by clearing cookies | false |
askforpushpermissionatfirstrun / requirePush | True shows the system prompt before the user knows the app | false, call registerpush:// later |
uselocalhtmlfolder / USE_LOCAL_HTML_FOLDER | True loads the bundled HTML instead of your URL | false unless you ship an offline bundle |
openallexternalurlsinsafaribydefault | Decides whether other domains open in the system browser | true for marketing and social links, keep your own domains inside |
| Usage descriptions left in Info.plist | Reviewers question permissions the app never uses (2.5.4) | Delete unused ones, keep the tracking key |
It edits files and can run command-line builds; the IDE steps (signing, archive, upload) remain yours. Ask it to write the exact click path for your version if you are unsure.
Paste the compiler error into the same session. Typical causes are a missing quote or a boolean written as a string. The agent fixes its own syntax quickly; if the error is in signing, revert the change and do it in the IDE.
Yes, many teams keep ios/ and android/ folders next to the web project. Add build folders and keystore files to .gitignore, and never commit the keystore or passwords.
Your web app updates by deploying. For a new WebViewGold version, download the new project, let Claude Code copy your settings into the new Config.swift and Config.java, and rebuild.
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
$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$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$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.
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.
