One codebase, real store app
The iOS app loads your published GitHub Copilot URL inside a native WebView. There is no second project to maintain and no code export.
Why wrapping beats rebuilding for GitHub Copilot apps
Copilot lives in your repository: issues, pull requests, Actions and whatever host deploys main. WebViewGold fits that loop because the native app loads the URL your main branch deploys to, so merging a Copilot pull request updates the installed app without a store release. A separate Swift and Kotlin project would give the agent two more codebases to keep in sync, while the JavaScript bridge lets Copilot add push, haptics, sharing or biometric login in the code it already knows.
Keep shipping from GitHub Copilot
Merge to main, the deployment runs and the app shows the change on the next launch. Only changes to the native shell itself (icon, new native feature) need a store update.
Native features on top
Push notifications, offline screen, native sharing, biometric login, QR scanner, in-app purchases and deep links are single settings or one-line JavaScript calls.
App Store approval guarantee
Apple App Store approval guarantee – or your money back within 14 days. 96.4% of all WebViewGold apps get approved by the review teams on the first attempt.
What you need
- A published GitHub Copilot app on a public HTTPS URL (username.github.io/repo or yourproject.vercel.app or, better, your own domain)
- An Apple Developer Program ($99 per year) to submit to the Apple App Store
- Xcode on a Mac – or the WebViewGold Cloud Builder in your browser (no Mac needed)
- WebViewGold for iOS ($109 one-time, free updates)
- A privacy policy page, a 1024 × 1024 px icon and 30 to 60 minutes
With a good optimized version of your web app you can have a stunning mobile app within a couple of minutes. Additionally to that the customer service is very nice and very helpful! I can just recommend WebViewGold :-)
GitHub Copilot to App Store: the walkthrough
Eight steps, no coding. Most people finish the native part in under an hour.
Publish your GitHub Copilot app to a production URL
Merge the pull request into your main branch and let your host deploy it: Vercel, Netlify or Azure Static Web Apps build every push, or a GitHub Actions workflow publishes a static build to GitHub Pages. Insert the production URL or your domain into WebViewGold. Codespaces forwarded ports (app.github.dev), pull request preview deployments and localhost are temporary. Use the production deployment of your main branch. Custom domain: Add the domain in the repository's Pages settings (or your host's domain settings), set the DNS records and turn on Enforce HTTPS. See why a custom domain before submission is worth it.
Make it store-ready
Add a privacy policy page, an account deletion option (if users can sign up), and remove builder badges or "download our app" banners. Run the free App Store readiness check on your URL: it flags mixed content, missing viewport tags, builder preview domains and other blockers in seconds.
Get WebViewGold for iOS
One-time payment, free updates. You receive the ready-made Xcode project. If you do not own a Mac, activate the WebViewGold Cloud Builder and do everything in the browser.
Insert your URL and brand the app
Open Config.swift (or the Cloud Builder form) and paste your published URL. Set the app name, upload your icon, pick splash screen and status bar color. No coding needed.
Switch on native features
Enable push notifications, the offline screen, social-login handling, pull-to-refresh, biometric login or the QR scanner with single settings. Everything is optional.
Build and upload
In Xcode: Product → Archive → Distribute to App Store Connect. In the Cloud Builder: click Build, the upload to App Store Connect is done for you.
Create the App Store listing
In App Store Connect add name, subtitle, description, keywords, screenshots, privacy policy URL and the App Privacy answers. Add a demo account in the review notes if needed.
Submit for review
Apple reviews most apps within 24 to 48 hours. Answer reviewer questions in Resolution Center if any come up. Our approval guarantee covers you.
GitHub Copilot-specific checks before you submit
These are the points that come up most often with GitHub Copilot projects (Any web stack in your GitHub repository: Next.js, React + Vite, Astro, Vue, Rails, Django or ASP.NET).
- GitHub Pages serves static files only, and a project site lives under /repo-name/. Set the base path, add a 404.html fallback (or hash routing) for single-page apps, and prefer a custom domain, or deep links and refreshes return 404 inside the app.
- Put the WebViewGold rules into .github/copilot-instructions.md (or AGENTS.md) so agent mode and the cloud agent stop adding "Download our app" banners, desktop-only hover menus or browser-only APIs.
- Check every Copilot pull request at phone width (its preview deployment or a Codespace) before you merge: horizontal overflow at 320px and tiny tap targets are what make a wrapped app feel like a website to reviewers.
- If the app offers Sign in with GitHub, Google or another third-party login, Apple's Guideline 4.8 expects an equivalent privacy-focused option such as Sign in with Apple, which WebViewGold handles automatically; Google and Facebook logins run through the Social Login Helper.
Let GitHub Copilot do the store-readiness work
Paste this into GitHub Copilot and let it apply the changes reviewers look for. Review the result, then publish.
Issue for the Copilot cloud agent (or agent mode)
Title: Prepare the web app for the App Store and Google Play (WebViewGold wrapper) This app will be published as native iOS and Android apps that load the production URL in the WebViewGold WebView wrapper. Do not add Capacitor, React Native or native SDKs; native features come from the WebViewGold JavaScript bridge documented at https://www.webviewgold.com/llms-full.txt. Open one pull request that meets these acceptance criteria: - [ ] Meta viewport tag, no horizontal overflow from 320px to 1024px, 44px tap targets, safe-area-inset padding on fixed headers and footers - [ ] /privacy and /terms pages linked from the footer - [ ] A "Delete account" action in settings that removes the user's data and auth record after confirmation - [ ] No "Download our app" banners or external promotional links in the main navigation - [ ] Error and retry states for failed requests; no placeholder content - [ ] Single-page routes work on refresh and deep links (404 fallback if the site is on GitHub Pages) - [ ] A "Native app wrapper" section with these rules in .github/copilot-instructions.md If you can run the app, add screenshots of the main screens at phone width to the pull request description.
App Store review: the rules that matter for GitHub Copilot apps
Apple reviews behavior, not tooling. Nobody is rejected for using GitHub Copilot; apps are rejected for the points below.
- 4.2
Minimum Functionality
The app must offer more than a repackaged website. Responsive layout, native navigation and at least one native capability (push notifications, offline screen, native sharing, biometric login) make the difference. WebViewGold switches these on with one setting each.
- 2.1
App Completeness
No placeholder content, no dead links, no crashes. If content sits behind a login, provide a demo account in the App Review notes.
- 5.1.1
Privacy
A public privacy policy URL is mandatory. Apps that let users create accounts must also let them delete the account inside the app.
- 4.8
Login Services
If the app uses Google, Facebook or another third-party or social login for the user's account, it must also offer an equivalent login that limits data to name and email, lets users keep their email private and does not track them for advertising. Sign in with Apple is the safe way to meet this. An app that only uses its own email/password login is not affected.
- 3.1.1
In-App Purchase
Digital goods and subscriptions sold inside the app must use Apple's In-App Purchase. Physical goods and real-world services can keep Stripe or PayPal.
- 2.3
Accurate Metadata
Screenshots, description and app name must match what the app does. Do not mention other platforms or "beta" in the listing.
Native features your GitHub Copilot app gets in the iOS app
Every feature is optional and documented step by step in the WebViewGold for iOS documentation.
Push notifications
Remote push via OneSignal or Pushwoosh, local scheduled pushes via a JavaScript call, permission prompt at the moment you choose.
DocumentationSocial Login Helper
Google and Facebook logins work inside the app; Sign in with Apple is handled automatically.
DocumentationUniversal Links
Links from emails (magic links, password resets) open directly in the app.
DocumentationIn-app purchases
App Store subscriptions and one-time purchases via RevenueCat, triggered from your web app.
DocumentationOffline screen and fallback
A native "Try again" screen when the user is offline, or a local HTML fallback.
DocumentationLoading indicator and splash
Keep the launch screen until the web app is loaded, or show a native spinner.
DocumentationBiometric login
Face ID / Touch ID gate from a JavaScript call.
DocumentationQR and barcode scanner
Native scanner that returns the result to your web app.
DocumentationNative share sheet and haptics
Share dialog and haptic feedback from your web app.
DocumentationCustom CSS and JavaScript
Hide website-only elements and inject code when loaded inside the app.
DocumentationPre-flight checklist for App Store
Tick these off and the review is a formality. The free readiness check verifies the technical half automatically.
- HTTPS everywhere: App Transport Security blocks plain http:// content and invalid certificates.
- Responsive layout from 320 px to iPad widths. Apple also opens iPhone apps on an iPad during review.
- Privacy policy URL ready (a page inside your web app is fine).
- Account deletion available in the app if users can sign up.
- Demo login for the reviewer if content is behind authentication.
- No "Download our app" banners, no links to other app stores, no builder badges inside the app.
- A 1024 × 1024 px app icon without transparency and rounded corners (Apple adds the mask).
- Screenshots for the current iPhone sizes (and iPad if supported) taken from the real app.
- App name of 30 characters or fewer, a subtitle and keywords prepared.
- Export compliance answered (an app that only uses HTTPS qualifies for the standard encryption exemption).
Example: from GitHub Copilot project to approved app
Say you built a shift planner for a community food bank in a Next.js repository with Copilot: volunteers see open shifts, sign up with one tap and get a reminder the day before. You write the store-readiness checklist as an issue, assign it to the Copilot cloud agent, review its pull request at phone width and merge. Vercel deploys main to shifts.yourfoodbank.org, which you wrap with WebViewGold, and OneSignal push tells volunteers when an urgent shift opens. Because the login offers Google, the agent adds Sign in with Apple in a second pull request. The demo volunteer in the review notes already has two shifts booked, both stores approve the app, and every merged pull request reaches it on the next launch.
Your first week after launch
- Label store-related issues (for example app-store) and assign them to the Copilot cloud agent; review each pull request at phone width before you merge.
- Protect main with a required status check that builds the app, since a broken merge goes straight to every installed copy.
- Keep .github/copilot-instructions.md in sync with the WebViewGold bridge calls you use, so the agent does not remove them during refactors.
- Read the OneSignal player ID with getonesignalplayerid:// after login and store it with the user, so a push can go to one volunteer instead of everyone.
- Ask for a rating with rateapp:// after a volunteer completes their first shift.
What you get with WebViewGold
A complete native app project, not a subscription. Everything below is included in the license and switched on with a setting.
- Complete Xcode project
- Push notifications
- Offline screen
- App icon & splash screen
- Share sheet & haptics
- Deep & universal links
- In-app purchases
- Free updates, white-label
Frequently asked questions
How do I publish a web app I built with GitHub Copilot in the App Store?
Deploy the main branch to a public HTTPS URL (Vercel, Netlify, Azure Static Web Apps or GitHub Pages), insert that URL into WebViewGold for iOS, build with Xcode or the Cloud Builder and submit through App Store Connect. The same URL powers the Android app.
Can the Copilot cloud agent prepare my app for review?
Yes. Assign it an issue with the store-readiness checklist, review the pull request it opens at phone width and merge. Because the store app loads your deployment, the merged changes reach installed apps without a new store version.
Is GitHub Pages good enough for a store app?
For a static or client-rendered app, yes, with a custom domain, HTTPS enforced and a fallback for single-page routes. If the app needs server code, API routes or secrets, deploy it to Vercel, Netlify or Azure instead.
Do I need a Mac to publish an iOS app?
Not with the WebViewGold Cloud Builder: configuration, build and upload to App Store Connect happen in the browser. If you own a Mac, the Xcode project works out of the box.
How long does Apple review take?
Most submissions are reviewed within 24 to 48 hours. First submissions and apps with logins sometimes get a question from the reviewer; answer it in Resolution Center and the review continues.
What if Apple rejects the app?
Rejections name the guideline and the reason, and you can resubmit as often as needed. WebViewGold comes with an App Store approval guarantee: if Apple rejects the app for a non-content reason, you get your money back within 14 days of purchase.
Can my app use Sign in with GitHub as its only login?
Only if the app is a client for GitHub itself, for example a dashboard for the user's own repositories, because Guideline 4.8 exempts apps where users must sign in to a specific third-party service to reach their content there. For any other product, add Sign in with Apple, or another login that meets the guideline's privacy conditions, next to the GitHub button. Google Play has no such rule, but its App access section still needs credentials that let the reviewer in.
Do I need a custom domain if the app runs on GitHub Pages?
Strongly recommended. A project site lives under username.github.io/repo-name/, so files that must sit at the domain root, such as apple-app-site-association and assetlinks.json for Universal Links and App Links, cannot be served for it, and moving the site later would change the URL inside your app. With your own domain, HTTPS enforced and a 404.html fallback for single-page routes, GitHub Pages is a fine host for a static store app.
Do I have to resubmit the app every time I change something in GitHub Copilot?
No. The app loads your published URL, so content and feature changes you publish in GitHub Copilot are live in the app immediately. A new store version is only needed when the native shell changes, for example a new app icon or an added native feature.
What does it cost in total?
$109 one-time for WebViewGold for iOS (free updates) plus the Apple Developer Program ($99 per year). Optional: the Cloud Builder add-on ($349 per license, one-time) if you want to build in the browser without a Mac, or the Full Service package (from $698 per platform) where our team configures, builds and submits the app for you.
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 pageCloud 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.