One codebase, real store app
The Android app loads your published Kiro URL inside a native WebView. There is no second project to maintain and no code export.
Why wrapping beats rebuilding for Kiro apps
Kiro plans one product per spec, and a native rewrite would split every requirement into three implementations that drift apart. WebViewGold wraps the Amplify Hosting (or Netlify or Vercel) deployment instead, so Cognito auth, AppSync data and Lambda functions keep serving the app unchanged and every spec you finish reaches installed apps with the next push. Native capabilities become ordinary tasks in the spec: enable the feature in WebViewGold and call it through the JavaScript bridge.
Keep shipping from Kiro
Push to the production branch, Amplify redeploys 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 Kiro app on a public HTTPS URL (main.yourappid.amplifyapp.com or yourproject.netlify.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
My iOS WebView is finally approved. Thanks!!
Kiro to Google Play: the walkthrough
Eight steps, no coding. Most people finish the native part in under an hour.
Publish your Kiro app to a production URL
Connect the repository to AWS Amplify Hosting (Kiro's Amplify power walks the agent through it), or deploy with the Netlify power or Vercel. Every push to the connected branch redeploys. Insert the production URL or your domain into WebViewGold. Amplify pull request previews, Amplify sandboxes and localhost are for testing. Point WebViewGold at the production branch. Custom domain: Add the domain in the Amplify console's custom domain settings (Route 53 domains are set up for you) or in your host's domain settings, then set the DNS records. 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.
Kiro-specific checks before you submit
These are the points that come up most often with Kiro projects (Any web stack; Kiro projects are often React or Next.js on AWS Amplify Gen 2 (Cognito, AppSync, DynamoDB) or with Supabase).
- Write the store rules into the spec as acceptance criteria, for example "WHEN a signed-in user confirms Delete account THE SYSTEM SHALL delete their data and their Cognito user". Account deletion, the privacy page and the 320px layout then become tasks instead of afterthoughts.
- Add a steering file such as .kiro/steering/native-app.md (inclusion: always) stating that the app runs inside the WebViewGold wrapper, so new specs avoid "Download our app" banners, hover-only menus and browser-only APIs.
- The Cognito hosted sign-in page with Google federation redirects to accounts.google.com, which Google blocks in embedded WebViews; add that prefix to WebViewGold's Social Login Helper triggers.
- In-app account deletion must remove the Cognito user (deleteUser in Amplify Auth) and the user's records; Apple (Guideline 5.1.1(v)) and Google Play both check it.
Let Kiro do the store-readiness work
Paste this into Kiro and let it apply the changes reviewers look for. Review the result, then publish.
Prompt for Kiro (spec mode)
Create a new spec named store-readiness. This web app will be published as native iOS and Android apps that load its production URL inside the WebViewGold WebView wrapper. Requirements (EARS): 1. WHEN the app is shown on a screen from 320px to 1024px wide THE SYSTEM SHALL not scroll horizontally, SHALL use tap targets of at least 44px and SHALL pad fixed headers and footers with safe-area insets. 2. THE SYSTEM SHALL link /privacy and /terms pages from the footer. 3. WHEN a signed-in user confirms Delete account in settings THE SYSTEM SHALL delete their data and their auth (Cognito) user. 4. THE SYSTEM SHALL NOT show "Download our app" banners or external promotional links in the main navigation. 5. WHEN a request fails THE SYSTEM SHALL show an error message with a retry action. 6. THE SYSTEM SHALL set the page title to the app name (max 30 characters). Design: list the files you will change and any Amplify backend changes. Tasks: one task per requirement. Also create .kiro/steering/native-app.md with inclusion: always that records these rules and points to https://www.webviewgold.com/llms-full.txt for native features. Stop after the spec so I can review it before you implement.
Google Play review: the rules that matter for Kiro apps
Google reviews behavior, not tooling. Nobody is rejected for using Kiro; 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 Kiro 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 Kiro project to approved app
Say you built a maintenance request portal for a small property manager with Kiro: tenants report a problem with photos, staff assign it and tenants follow the status. The spec covers Cognito sign-in with Apple and Google, an Amplify Data model for requests, S3 storage for photos and an acceptance criterion for account deletion. You connect the repository to Amplify Hosting, add requests.yourdomain.com and wrap it with WebViewGold, where the native camera handles the photo upload and OneSignal push tells tenants when a technician is on the way. The demo tenant in the review notes has one open and one closed request. Both stores approve the app, and every finished spec reaches it with the next push to the production branch.
Your first week after launch
- Turn each piece of feedback into a small spec or a quick vibe session, then push to the production branch; Amplify redeploys and the apps follow.
- Keep .kiro/steering/native-app.md current with the WebViewGold bridge calls you use, so new specs do not undo them.
- Watch Amplify build minutes and DynamoDB usage in launch week; store users often open an app several times a day.
- Send a push only when a request changes status; tenants keep notifications on when every message matters.
- Ask for a rating with rateapp:// after a request is closed as solved.
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 Kiro-built app in the App Store and on Google Play?
Deploy it to a public HTTPS URL (Amplify Hosting, Netlify, Vercel or your own server), insert the URL into WebViewGold for iOS and Android, build with Xcode and Android Studio or the Cloud Builder, and submit both apps.
Do I need AWS to publish a Kiro app?
No. Amplify Hosting is a natural fit for Kiro projects, but WebViewGold only needs a public HTTPS URL. Netlify, Vercel, Cloudflare Pages or your own server work exactly the same way.
Can a Kiro spec cover the App Store requirements?
Yes, and it is a good habit: put layout, privacy page, account deletion and error states into the requirements so Kiro builds and tests them like any other feature. Native features such as push or biometric login are then enabled in WebViewGold and called through its JavaScript bridge.
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 I use Sign in with Apple with Amazon Cognito?
Yes. Cognito user pools support Apple as an identity provider: create a Services ID and a Sign in with Apple key in the Apple Developer portal, add Apple to the external providers in your Amplify auth definition and show the button next to Google. Inside the app, WebViewGold detects the Apple sign-in page and handles it without configuration, and Google sign-in runs through the Social Login Helper.
Should the store app load Amplify Hosting or a different host?
Either works, because WebViewGold only needs a public HTTPS URL. Amplify Hosting is convenient for Gen 2 projects because the frontend and the backend deploy together per branch. Whatever you choose, point the app at the production branch on your own domain, so switching hosts later is a DNS change and not a new app build.
Do I have to resubmit the app every time I change something in Kiro?
No. The app loads your published URL, so content and feature changes you publish in Kiro 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.