One codebase, real store app
The iOS 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.
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 Kiro app on a public HTTPS URL (main.yourappid.amplifyapp.com or yourproject.netlify.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 :-)
Kiro to App Store: 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 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.
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.
App Store review: the rules that matter for Kiro apps
Apple reviews behavior, not tooling. Nobody is rejected for using Kiro; 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 Kiro 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 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 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 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 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 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 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.