One codebase, real store app
The Android app loads your published Dyad URL inside a native WebView. There is no second project to maintain and no code export.
Why wrapping beats rebuilding for Dyad apps
Dyad gives you plain React code on your own machine and leaves hosting to you, so once the project is on Vercel you have exactly what WebViewGold needs: a public HTTPS URL. Dyad's experimental Capacitor upgrade packages the build into native projects you rebuild for every change; WebViewGold loads the live deployment instead, so a Sync to GitHub updates the apps. Supabase auth and data keep running unchanged on the web side.
Keep shipping from Dyad
Sync to GitHub in Dyad, your host rebuilds, and the app shows the new version on the next launch, no store update needed. 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 Dyad app on a public HTTPS URL (yourapp.vercel.app (or the address of the host you deploy to) 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
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 :-)
Dyad to Google Play: the walkthrough
Eight steps, no coding. Most people finish the native part in under an hour.
Publish your Dyad app to a production URL
Dyad does not host apps itself. Connect GitHub in the app details, click Sync to GitHub, then import the repository at Vercel (or another host); you get a public URL like dyad-app-name.vercel.app. Every later Sync to GitHub triggers a new build. The preview next to the Dyad chat runs on your own computer, so nobody else can open it. Deploy first and use the public deployment URL or your custom domain in the app. Custom domain: Add your domain on the hosting side (Vercel: project settings, Domains) and set the DNS records it shows you. 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.
Dyad-specific checks before you submit
These are the points that come up most often with Dyad projects (React + TypeScript + Vite with React Router, Tailwind CSS and shadcn/ui in the default template (a Next.js template is also available), with Supabase or Neon for auth and data).
- Dyad offers an experimental "Upgrade to hybrid mobile app with Capacitor" that opens the project in Xcode and Android Studio. That route packages your build into native projects you rebuild for every change; WebViewGold loads your deployed URL instead, so a Sync to GitHub updates the installed apps.
- The default template is a single-page app with React Router and ships a vercel.json that sends every path to index.html. Keep an equivalent rewrite if you deploy somewhere else, or deep links and reloads inside the app end on a 404 page.
- Supabase asks new users to confirm their email by default. The confirmation link opens the phone's browser unless you set up Universal Links (iOS) and App Links (Android) in WebViewGold, so plan that before review.
- A Dyad app runs client-side by default: keep API keys in Supabase server functions or in your host's environment variables, never in the browser bundle.
- Google login inside the app needs WebViewGold's Social Login Helper, because Google blocks OAuth in embedded WebViews.
- Made with Dyad: The default template puts a "Made with Dyad" link at the bottom of the main page. Ask Dyad to remove the MadeWithDyad component everywhere before you build the app. More on builder badges.
Let Dyad do the store-readiness work
Paste this into Dyad and let it apply the changes reviewers look for. Review the result, then publish.
Prompt to paste into Dyad
Prepare this app for publishing as a native iOS and Android app (it will run inside a native WebView wrapper that loads the deployed URL): 1. Add /privacy and /terms routes in src/App.tsx with placeholder pages I can edit, and link them from the footer and the settings screen. 2. Add a "Delete my account" action in the account settings that calls a Supabase server function to delete the user's rows and auth user, with a confirmation dialog. 3. Remove the MadeWithDyad component from every page. 4. Make every page responsive from 320px to iPad widths, with no horizontal scrolling and tap targets of at least 44px. 5. Show a friendly retry state when a request fails instead of an empty screen. 6. Make sure no API keys are used in client code; move them to Supabase server functions. 7. Set the <title> in index.html to the app name (max 30 characters) and add a meta description.
Google Play review: the rules that matter for Dyad apps
Google reviews behavior, not tooling. Nobody is rejected for using Dyad; 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 Dyad 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 Dyad project to approved app
Say you built a digital loyalty card for a coffee roastery with Dyad: customers sign up, show a personal QR code at the counter and collect a stamp with each coffee. Dyad wrote the React app on your laptop, Supabase stores customers and stamps, and Sync to GitHub deploys it to Vercel under cards.yourroastery.com. In the WebViewGold app, the barista opens the staff page and taps a scan button that calls qrcode://; the customer's code encodes a URL such as /stamp/8f3k, which opens inside the app and adds the stamp. A OneSignal push tells customers when their tenth coffee is free. You remove the Made with Dyad link, both stores approve the app, and your laptop can stay closed: the app keeps running on Vercel and Supabase.
Your first week after launch
- Make changes in Dyad, test them in the local preview, then Sync to GitHub; nothing reaches the app until the Vercel build has finished.
- Add a short section about the WebViewGold bridge calls to AI_RULES.md, so later prompts do not remove the scan button or the push registration.
- Keep your AI provider key in Dyad on your computer; the deployed app only needs the Supabase keys that are meant for the browser.
- Check Vercel and Supabase usage after launch; a free plan that hits its limits looks like a broken app to customers.
- Ask for a rating with rateapp:// right after a customer redeems their first free coffee.
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
Can a Dyad app be published in the App Store and on Google Play?
Yes, once it runs on a public HTTPS URL. Sync the project to GitHub, deploy it on Vercel or another host, enter that URL in WebViewGold and build the iOS and Android apps. The apps load your deployment, so the code stays a normal web project you keep editing in Dyad.
Dyad has a Capacitor upgrade. Why use WebViewGold instead?
The Capacitor upgrade is experimental and leaves you with native projects to configure and rebuild whenever the web code changes. WebViewGold gives you ready Xcode and Android Studio projects with native features as config switches, and because it loads your deployed URL, web changes reach users without a new store build.
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.
Does my computer have to stay on for the Dyad app to work?
No. Dyad only runs while you build. The published app is served by Vercel (or your other host) and uses Supabase or Neon in the cloud, so customers can use it while your laptop is closed. Your computer matters again only when you want to change something and Sync to GitHub.
Which AI model should I use in Dyad for a store app?
Any model that handles React and Supabase well. Apple and Google review the deployed app, not the model that wrote it. More important are a short AI_RULES.md, which keeps Dyad's output consistent across models, and the habit of testing the production URL on a real phone before you submit.
Do I have to resubmit the app every time I change something in Dyad?
No. The app loads your published URL, so content and feature changes you publish in Dyad 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.