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 you are actually building
A WebViewGold app is a native iOS or Android app whose main screen is a WKWebView (iOS) or Android WebView showing your deployed web app. Your Next.js, Vite, SvelteKit or plain HTML project keeps living on its URL; the native shell adds what a browser tab cannot: push notifications, a splash screen, an offline screen, biometric login, a native share sheet, deep links and an App Store listing. Nothing in your codebase has to be rewritten, which is why this works so well with an agent: Claude Code keeps editing the web app, you keep deploying, and the store apps update themselves.
The work splits into three places. The web project (Claude Code does most of it), the WebViewGold projects (a handful of settings in Config.swift and Config.java), and the store consoles (listings, privacy answers, review notes, which Claude can draft but you submit).
The workflow, step by step
Expect one to two working days for a first submission, most of it waiting on accounts and reviews.
Deploy to a permanent HTTPS URL
Push the repository to GitHub and connect it to Vercel, Netlify or Cloudflare Pages; ask Claude Code to add the deployment config and environment variables for you. Then attach your own domain. A
*.vercel.appURL works technically, but a custom domain avoids a resubmission later, since the URL is compiled into the app.Run a store-readiness pass with Claude Code
Paste the prompt below. The agent audits the mobile layout, adds /privacy and /terms routes, an account-deletion action, error and empty states, and removes website-only elements such as "Download our app" banners. Review the diff, run the app on your phone, deploy.
Add one or two native features
Reviewers apply Guideline 4.2 to web-based apps, so give them something a Safari tab cannot do. Push notifications are the usual choice; the JavaScript bridge guide shows how Claude Code wires them in.
Configure WebViewGold
iOS: open Config.swift and set
hostandwebviewurl; Android: open Config.java and setHOSTandHOME_URL. Set the app name and icon, then switch on the features you use (push service, Social Login Helper triggers, pull-to-refresh). Claude Code can edit these files too; the project configuration guide lists what to let it touch.Build
With a Mac: open the Xcode project, set your Team and bundle ID, archive, upload. Android Studio: rename the package, build a signed App Bundle. Without a Mac or without wanting to install either IDE, the Cloud Builder builds both apps in the browser and uploads them to App Store Connect and the Play Console.
Write the listings
Ask Claude Code for the privacy policy, the App Privacy and Data safety answers, the description, keywords and review notes based on the real codebase, then take screenshots of the actual app. The listing guide has the prompts.
Submit and respond
Apple usually answers within 24 to 48 hours, Google within a few days (up to a week for new accounts). If a rejection comes back, paste it into Claude Code; the rejection guide explains the triage.
The store-readiness prompt
Run it once, read the summary, then deploy. The agent will ask questions where your stack needs decisions (which auth provider, where user data lives).
Paste into Claude Code in your project root
This web app will be published as native iOS and Android apps using WebViewGold, a native wrapper that loads our deployed URL in a WKWebView / Android WebView. Prepare the codebase for App Store and Google Play review. Work through the following, commit after each item, and finish with a summary of what changed and what I still have to do manually. 1. Mobile layout: viewport meta tag present, no horizontal overflow between 320 px and 1024 px, tap targets at least 44 x 44 px, fixed headers and footers padded with env(safe-area-inset-top) and env(safe-area-inset-bottom), no hover-only interactions, no desktop-only navigation. 2. Legal pages: add /privacy and /terms routes with real content based on what the app actually collects (check the auth, analytics and payment code). Link both from the footer and from the settings screen. Do not use Lorem ipsum or placeholders. 3. Account deletion: if users can sign up, add a Delete account action in settings with a confirmation step that deletes the user's data and auth record server-side, signs the user out and shows a confirmation. Add a public /delete-account page explaining the process. 4. Sign in with Apple: if Google, Facebook, GitHub or any other third-party login exists, add Sign in with Apple as an equal option (Apple guideline 4.8). 5. Payments: list every place where a digital product, subscription or credit pack is sold. Do not change it yet; report it so I can decide between in-app purchase and web checkout. 6. States: every data fetch needs a loading state, an empty state and an error state with a retry button. No blank screens, no uncaught promise rejections visible to users. 7. Remove website-only elements when the app runs inside the native wrapper: cookie banners that are not legally required, app-store badges, Download our app banners, builder badges, external promotional links. Prefer detecting the wrapper user agent string we will set in WebViewGold (it contains the token WebViewGoldApp) and hiding those elements. 8. Dead ends: find links that lead to 404 pages, placeholder buttons, and features marked coming soon. Fix or remove them. 9. Set the HTML title to the app name (max 30 characters) and add a meta description. 10. Secrets: confirm that no API key that should be server-side is shipped in the client bundle.
Great way of converting your web app to a native app! Fast turn-around, and a great way to get your apps into the app stores without the need to develop a full native app!
Teach the agent about the app context with CLAUDE.md
Claude Code reads a CLAUDE.md file in the project root at the start of a session. A short section like this keeps every future change store-compatible. The full template goes further.
markdown
## Native app context (WebViewGold)
- This web app is also published as iOS and Android apps. The native apps load
https://app.example.com inside a WebView. Everything we deploy is live in the apps.
- Keep the layout working from 320 px width; respect env(safe-area-inset-*) on fixed bars.
- Never add "Download our app" banners, cookie walls or builder badges.
- Store rules we follow: Apple 4.2 (not just a website), 4.8 (Sign in with Apple when
other social logins exist), 5.1.1 (privacy policy + in-app account deletion),
3.1.1 (digital goods inside the iOS app go through in-app purchase).
- Native features are plain URL schemes handled by the wrapper, documented at
https://www.webviewgold.com/llms-full.txt. Call them only when the user agent contains
"WebViewGoldApp"; in normal browsers fall back to web behavior.Who does what
| Claude Code | You | |
|---|---|---|
| Web app | Layout fixes, legal routes, account deletion, error states, native bridge calls, deploy config | Review diffs, test on a real phone, deploy |
| WebViewGold projects | Edit Config.swift / Config.java values, permission strings, manifest entries (with review) | Signing, certificates, keystore, bundle ID in App Store Connect |
| Store consoles | Draft privacy policy, privacy answers, description, keywords, review notes | Create the apps, upload screenshots, answer questionnaires, submit |
| Review feedback | Triage the rejection text, propose fixes, draft the reply | Decide, resubmit |
Before you press Submit
- The app loads your production domain, not localhost, a preview deployment or a tunnel URL.
- Airplane mode shows the WebViewGold offline screen, not a white page.
- Demo account for reviewers works on the first try and is written into the review notes.
- Privacy policy URL in both consoles opens the deployed /privacy page.
- Push permission is requested after onboarding (registerpush://), not on the very first screen.
- Run the free readiness check on your URL and fix what it flags.
Frequently asked questions
Does Apple care that the app was built with Claude Code?
No. The review looks at behavior, completeness, privacy and payments. Which editor or agent wrote the code is invisible and irrelevant.
Do I need a Mac?
For the manual Xcode route, yes. The WebViewGold Cloud Builder builds and uploads the iOS app from the browser, so the whole workflow also works from Windows or Linux.
Can the same URL power both the iOS and the Android app?
Yes. Both WebViewGold projects point at the same deployed web app. Platform differences are handled through the wrapper settings and, where needed, user agent detection in your code.
What if my web app is still changing daily?
That is fine. Deploys update both apps instantly. Only changes to the native shell (new permissions, a new push service, a new app name) need a new build and a store update.
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.