One codebase, real store app
The Android 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.
Google Play approval guarantee
Google Play 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 Google Play Console developer account ($25 one-time) to submit to the Google Play Store
- Android Studio on Windows, macOS or Linux – or the WebViewGold Cloud Builder in your browser
- WebViewGold for Android ($109 one-time, free updates)
- A privacy policy page, a 1024 × 1024 px icon and 30 to 60 minutes
Great work! Never coded anything but managed to work with this. Easy and fast! Also with great help from the creators!
GitHub Copilot to Google Play: 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 Google Play readiness check on your URL: it flags mixed content, missing viewport tags, builder preview domains and other blockers in seconds.
Get WebViewGold for Android
One-time payment, free updates. You receive the ready-made Android Studio project, or activate the WebViewGold Cloud Builder and skip the IDE entirely.
Insert your URL and brand the app
Open Config.java (or the Cloud Builder form), paste your published URL, set the app name, choose your package name, upload the icon and pick the splash screen. No coding needed.
Switch on native features
Enable push notifications, the offline screen, pull-to-refresh, biometric login, the QR scanner or App Links with single settings. Everything is optional.
Build the signed App Bundle
In Android Studio: Build → Generate Signed Bundle. In the Cloud Builder: click Build and the signed .aab is prepared and uploaded for you.
Create the Play Console listing
Create the app in the Play Console, fill in the store listing, upload icon, feature graphic and screenshots, complete Data safety, content rating and app access.
Test, then submit
New personal accounts run a 14-day closed test with 12 testers first. Then promote the release to production and submit for review. 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.
Google Play review: the rules that matter for GitHub Copilot apps
Google reviews behavior, not tooling. Nobody is rejected for using GitHub Copilot; apps are rejected for the points below.
- Minimum functionality
Spam and minimum functionality policy
Google rejects apps that only wrap a website without the website owner's permission or that offer no real functionality. Wrapping your own product with added native features is fine.
- Data safety
User Data policy
Every app needs a privacy policy URL and a completed Data safety form that lists what the app and its SDKs collect.
- Account deletion
User Data policy
Apps that let users create accounts must offer account deletion inside the app and via a web link you provide in the Play Console.
- Testing requirement
Personal developer accounts
Personal accounts created after November 2023 must run a closed test with at least 12 testers for 14 continuous days before they can request production access.
- Target API level
Target API requirements
New apps must target a recent Android version. WebViewGold updates keep the template current; just build with the latest version.
- Payments
Google Play Billing
Digital goods and subscriptions sold in the app generally must use Google Play Billing (WebViewGold supports RevenueCat). Physical goods and services may use other payment methods.
Native features your GitHub Copilot app gets in the Android app
Every feature is optional and documented step by step in the WebViewGold for Android documentation.
Push notifications
Remote push via OneSignal or Pushwoosh, local scheduled pushes via a JavaScript call.
DocumentationApp Links and deep links
https links to your domain and custom schemes open directly in the app.
DocumentationIn-app purchases
Google Play 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.
DocumentationSplash screen and loading indicator
Minimum and maximum splash duration with fade-out, or a native spinner while loading.
DocumentationBiometric login
Fingerprint / face unlock gate from a JavaScript call.
DocumentationQR and barcode scanner
Native scanner that returns the result to your web app.
DocumentationNative share and haptics
Share intent and haptic feedback from your web app.
DocumentationCustom CSS and JavaScript
Hide website-only elements and inject code when loaded inside the app.
DocumentationFile and camera uploads
Native file picker and camera for your upload forms.
DocumentationPre-flight checklist for Google Play
Tick these off and the review is a formality. The free readiness check verifies the technical half automatically.
- HTTPS everywhere: Android blocks cleartext http:// traffic by default on current versions.
- Responsive layout from 320 px to tablet widths, with predictable back-button behavior (WebViewGold maps the back button to the web history).
- Privacy policy URL ready and the Data safety form answered truthfully.
- Account deletion inside the app plus a web deletion link if users can sign up.
- App access credentials for the reviewer if content is behind a login.
- A unique package name (for example com.yourcompany.yourapp) set before the first upload: it can never change afterwards.
- A 512 × 512 px icon and a 1024 × 500 px feature graphic.
- At least two phone screenshots taken from the real app (tablet screenshots recommended).
- For new personal accounts: 12 testers lined up for the 14-day closed test.
- Signed Android App Bundle (.aab) built from the latest WebViewGold version.
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 Android Studio 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 Android Studio?
Either Android Studio (free, runs on Windows, macOS and Linux) or the WebViewGold Cloud Builder, which builds and uploads the signed App Bundle from your browser.
What is the 12-tester rule?
Google requires personal developer accounts created after November 2023 to run a closed test with at least 12 opted-in testers for 14 continuous days before the first production release. Friends, colleagues or a Discord community are enough; organization accounts are exempt.
What if Google rejects the app?
Google names the policy in question and you can fix and resubmit. WebViewGold comes with a Google Play approval guarantee: if Google 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 Android (free updates) plus the Google Play Console developer account ($25 one-time). 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.