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 pageThe goal, and the two Copilot agents
The goal: your web app passes App Store and Google Play review when WebViewGold loads it in a native WebView, and it stays that way with every future Copilot change. Nothing gets rewritten in Swift or Kotlin. Copilot works on the web code; WebViewGold supplies the native Xcode and Android Studio projects.
Agent mode in VS Code is the Agent option in the Chat view's agent picker, next to Ask and Plan. It edits files across the project, runs terminal commands and iterates on errors while you watch. Use it for the audit and anything that needs your judgment on the spot.
The Copilot cloud agent, called the Copilot coding agent until 2026, works on GitHub. Assign an issue to Copilot and it runs in a GitHub Actions-based environment or a cloud sandbox, then opens a pull request and adds you as a reviewer. Mention @copilot in a pull request comment to ask for changes. It needs a paid Copilot plan, and on Business or Enterprise an admin must enable it first.
If your team mixes Copilot with Claude Code, Codex or Cursor, the AI coding agents hub has the matching guides for each tool.
The instruction file both agents read
Save as .github/copilot-instructions.md. VS Code uses it for Copilot sessions, and on GitHub the cloud agent, code review and Copilot Chat use repository instructions. Copilot also reads AGENTS.md and accepts a single root CLAUDE.md or GEMINI.md, so if your repo already has one, keep the native-app section in one place; the instruction file comparison shows how.
markdown
# Example app: web app plus native iOS and Android apps
## How the native apps work
- WebViewGold loads https://app.example.com in a WKWebView (iOS) and an Android
WebView. Every production deploy is live in both store apps.
- Native detection: isNativeApp() in src/lib/platform.ts (user agent contains
"MyAppNative", configured in WebViewGold). Do not add other user agent checks.
- Native features are URL schemes such as registerpush:// (push permission) or
shareapp://message?=TEXT&url=URL (share sheet). Use only schemes documented in
https://www.webviewgold.com/llms-full.txt and always provide a web fallback.
- Never suggest rewriting the app in React Native, Flutter, Swift or Kotlin.
## Store rules every change must keep
- Real /privacy and /terms pages, linked in the footer and in settings.
- In-app account deletion that removes server-side data and the auth user.
- Sign in with Apple wherever Google or another social login is offered.
- No external checkout links for digital goods inside the iOS app.
- Loading, empty and error states for every request; no dead links or placeholders.
- Works from 320 px width; fixed bars use env(safe-area-inset-*); tap targets >= 44 px.
## Build and verify
- Install: npm ci | Lint: npm run lint | Test: npm test | Build: npm run build
- Every pull request description lists what changed, how it was verified, and
what must be tested on a real iPhone and Android phone.Prepare the cloud agent's environment
The cloud agent can install what it needs, but a setup workflow makes runs faster and more predictable. It must live at .github/workflows/copilot-setup-steps.yml, contain a single job named copilot-setup-steps, and be on the default branch. Runners are Ubuntu x64 or Windows 64-bit; macOS is not supported, which is why the iOS build happens elsewhere.
text
name: "Copilot Setup Steps"
on:
workflow_dispatch:
push:
paths:
- .github/workflows/copilot-setup-steps.yml
jobs:
copilot-setup-steps:
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- name: Check out code
uses: actions/checkout@v5
- name: Set up Node.js
uses: actions/setup-node@v4
with:
node-version: "22"
cache: "npm"
- name: Install dependencies
run: npm ci
My iOS WebView is finally approved. Thanks!!
Agent mode prompt: audit, fix the small things, write the issues
Start in VS Code. The agent audits the repository, fixes the safe things itself and turns the rest into issue-sized tasks you can hand to the cloud agent.
Paste into VS Code Copilot Chat with Agent selected
We are about to publish this web app as native iOS and Android apps as well. WebViewGold loads our production URL in a WKWebView and an Android WebView. Follow .github/copilot-instructions.md. Audit the repository for App Store and Google Play review problems and do three things: 1. Fix directly (small, safe changes only): missing viewport meta tag, obvious horizontal overflow, tap targets under 44 px, inputs under 16 px font size, fixed bars without safe-area padding, broken links, leftover placeholder text. Run lint, tests and build afterwards. 2. Write docs/store-readiness.md listing every remaining problem as an issue-sized task: title, why reviewers care (name the Apple guideline or Google Play policy area), files involved, acceptance criteria, and how to verify. Each task must fit into one pull request. 3. Report without changing: every place that sells digital goods, subscriptions or credits, and every third-party SDK that collects data. I need both for the payment decision and the privacy labels. Do not add dependencies. Do not touch authentication or payment code in this run. End with a short summary and the tasks in the order you recommend.
Store-readiness issues to assign to Copilot
| Issue title | Acceptance criteria | Your review focus |
|---|---|---|
| Real /privacy and /terms pages | Content based on the data the code collects; linked from footer and settings; both load directly | Every SDK and data type is named; no placeholder company name |
| In-app account deletion | Delete account in settings with confirmation; server deletes data, files and auth user; public /delete-account page | Run it with a test user and check the database yourself |
| Sign in with Apple next to Google login | Equal placement and styling; works on the web and in the app | You create the Apple Services ID and keys; never let them land in the repo |
| Mobile layout pass | No horizontal scroll at 320 px; tap targets of 44 px; safe-area padding on fixed bars; 16 px inputs | Open the preview deployment on your phone |
| Loading, empty and error states | Every fetch has all three, with a retry button; a friendly 404 page | Turn off Wi-Fi and click around |
| Hide web-only elements in the app | isNativeApp() helper; store badges, install prompts and builder badges hidden when it returns true | Spoof the user agent in the browser dev tools |
The workflow, step by step
Agent mode for judgment, the cloud agent for well-defined tasks.
Commit the instructions and the setup workflow
Push both files to the default branch. For extra rules on certain paths, add
.github/instructions/mobile-ui.instructions.mdwith anapplyTopattern such as"src/components/**".Audit in agent mode
Run the prompt above in VS Code. Review the small fixes like any diff, run the app on your phone browser, commit.
Turn the task list into issues
Create one GitHub issue per task from docs/store-readiness.md and paste the acceptance criteria into the body. Copilot reads the issue title, description and existing comments.
Assign the issues to Copilot
In each issue's Assignees sidebar, choose Copilot and add instructions if needed. Keep tasks small: each one becomes exactly one pull request on one branch, and GitHub Actions-based sessions stop after 59 minutes.
Review and iterate on the pull requests
Read the diff, request a Copilot code review from the Reviewers menu if you like, and test the preview deployment. To change something, mention @copilot in a comment; it pushes new commits to the same branch.
Deploy and wrap with WebViewGold
Deploy to your production domain. In Config.swift set
host,webviewurl,useragent_iphoneanduseragent_ipad; in Config.java setHOST,HOME_URLandUSER_AGENT. The iOS setup docs list every option.Build and submit
No Mac needed with the Cloud Builder (one-time $349 add-on): it builds both apps in the browser and uploads them to App Store Connect and the Play Console. Let Copilot draft the review notes from the merged code.
Checklist before you submit
- copilot-instructions.md names the same production URL and user agent marker as the WebViewGold config.
- Every store-readiness pull request is merged and included in the production deploy.
- The reviewer demo account works and is written into the review notes.
- Every native feature you mention in the listing (push, share, biometrics) works in the built app.
- The app offers at least one capability a website cannot, so it clears Guideline 4.2.
- The free readiness check passes on your production URL.
Pitfalls with Copilot
- Issues that are too big ("make the app store-ready") lead to sprawling pull requests. One concern per issue.
- Branch protection or rulesets can block Copilot from creating or updating pull requests. An admin can grant Copilot a bypass.
- A GitHub Actions-based session can change only the repository the task started in. If your API lives in another repository, plan for that.
- On GitHub.com, path-specific instruction files apply only to the cloud agent and code review. Put anything Chat must know into the repository-wide file.
- Copilot may add a Stripe Checkout button for a subscription. The instructions forbid it in the iOS app, but review every payment change yourself.
- Secrets in the instructions file or in the setup workflow. Use repository or environment secrets instead.
Frequently asked questions
What is the difference between agent mode and the Copilot cloud agent?
Agent mode runs in your editor while you watch, with your local files and terminal. The cloud agent runs on GitHub in its own environment, works from an issue or prompt and hands back a pull request. Use agent mode for the audit and the cloud agent for well-defined fixes.
Is the Copilot coding agent the same as the cloud agent?
Yes. GitHub now calls it the Copilot cloud agent; older docs and blog posts say coding agent. Assigning issues, pull requests and @copilot comments work the same way.
Does Copilot read AGENTS.md?
Yes. The cloud agent reads AGENTS.md files anywhere in the repository, and the nearest one wins. It also accepts a single root CLAUDE.md or GEMINI.md. VS Code attaches a root AGENTS.md to chat requests by default.
Can Copilot build the iOS app?
Not on GitHub: the cloud agent runs on Ubuntu or Windows runners, and iOS builds need Xcode on macOS. Build with Xcode on a Mac or with the WebViewGold Cloud Builder in the browser.
Which Copilot plan do I need?
The cloud agent needs a paid Copilot plan, and Business and Enterprise admins must enable it. Plan contents and limits change often, so check GitHub's current plan comparison before you start.
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.