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 pageWhat Antigravity is in late 2026
Google released Antigravity in November 2025 and announced Antigravity 2.0 at Google I/O on May 19, 2026. Today it comes in several surfaces that share one agent harness: the Antigravity app (a standalone desktop app with projects, parallel agents, worktrees and scheduled tasks), the Antigravity IDE plus extensions for VS Code, JetBrains IDEs, Visual Studio, Zed, Xcode and Eclipse, and the Antigravity CLI (agy), which replaced Gemini CLI for consumer accounts on June 18, 2026. An SDK is in preview.
Many vibe coders arrive here from other Google tools. Google AI Studio's Build mode now runs on the Antigravity harness and can export a project to local Antigravity development, and Google points Firebase Studio users to Antigravity for code-first work before that product shuts down in March 2027. If you used Gemini CLI, the Gemini CLI guide shows the overlap, and the AI coding agents overview compares the other tools.
What none of these surfaces does is the native part: a signed iOS and Android app with a store listing. That is where WebViewGold comes in. Your Antigravity project stays a web app on a URL; WebViewGold's Xcode and Android Studio projects load that URL and add push, offline handling and the other native features reviewers look for.
A rule file for the WebView context
Antigravity loads rules from AGENTS.md or GEMINI.md in the workspace folder (and its parents up to the repository root), from .agents/rules/*.md, and globally from ~/.gemini/AGENTS.md. Modular rules in .agents/rules/ need YAML frontmatter with a trigger (always_on, model_decision, glob or manual); a file without valid frontmatter is silently discarded, per the rules documentation. Save this as .agents/rules/native-app.md, or paste the body without frontmatter into AGENTS.md so other agents read it too (the AGENTS.md template has a longer version).
markdown
---
trigger: always_on
---
# Shipping context: this web app is also a native app
- https://app.example.com is loaded by WebViewGold iOS and Android apps. A deploy
changes both apps at once; a change in ios/ or android/ needs a new store build.
- Treat a 375 x 812 viewport as the primary screen. Nothing scrolls sideways at
320 px. Fixed headers and tab bars use env(safe-area-inset-top / -bottom).
- Inside the app (navigator.userAgent contains "WebViewGoldApp"): no window.open
popups, no "get the app" banners, no builder badges, no links to store listings.
- Native features are URL schemes such as registerpush:// (iOS push prompt),
getonesignalplayerid://, shareapp:// and bioauth://. Use only schemes documented at
https://www.webviewgold.com/llms-full.txt and keep a browser fallback.
- Review-critical flows must never break: sign-in (Sign in with Apple next to
Google), Delete account in settings plus a public /delete-account page,
/privacy and /terms.
- Only publishable keys in client code. Gemini, Stripe secret, Supabase secret /
service_role and OneSignal App API keys live in server code or functions.
- Never deploy to production on your own. Never touch signing, keystores,
provisioning profiles or the WebViewGold purchase code.
- When you verify UI in the browser, record the flow and list what you could not
test there (push, Face ID, file pickers and haptics need the real app).The workflow, step by step
Use the app for orchestration and review; drop into the IDE or CLI when you want to read diffs line by line.
Open the project in a worktree
In the Antigravity app, click New Project, add your local folder or repository and choose New worktree mode for store work, so the agents' changes stay on their own branch until you merge. Coming from AI Studio, use its export to local Antigravity first.
Add the rule and check it loaded
Commit the rule file above. Before the first real task, ask the agent to summarize the rules it is following; if the WebView context is missing, the frontmatter is the usual suspect. Keep it short: all always-on rules share a 20,000-token budget.
Plan the store pass
Type
/planwith the prompt below. The plan arrives as an artifact: read it, leave inline comments where it guesses (auth provider, where user data lives), and only then click Proceed. Set the project's artifact review policy so the agent pauses for review on this kind of work.Let it build and check in the browser
Use
/browserso the agent clicks through sign-up, settings and account deletion in Chrome and records it. Give it a separate Chrome profile and an allowlist of your own domains, not your everyday profile with admin sessions. The walkthrough artifact with screenshots doubles as raw material for your App Store review notes.Deploy
Firebase projects can use the Firebase plugin and skills or the Firebase MCP server (install it from the MCP Store; it includes a deploy tool), and the Firebase checklist covers auth domains and rules. AI Studio apps usually live on Cloud Run; Vercel and Netlify work as well. Approve deploy commands yourself and attach a custom domain before you build the apps.
Wrap with WebViewGold
Set
hostandwebviewurlin Config.swift,HOSTandHOME_URLin Config.java, add the user agent token (useragent_iphone,useragent_ipad,USER_AGENT) and switch on push. If you would rather not open Xcode at all, our Full Service team configures and builds both apps within 72 hours.Test on devices and submit
Install a TestFlight build and an internal testing build on Google Play; that is where push, permissions and the offline screen get tested. Then submit with the review notes the agent drafted from the walkthrough.
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 :-)
The store-readiness plan prompt
Starts in plan mode. Items 2 and 9 are reports on purpose: they need your decision before any code changes.
Paste into Antigravity (app, IDE or agy)
/plan Prepare this web app for App Store and Google Play review. It will ship as native iOS and Android apps through WebViewGold, which loads our production URL in a WebView. Follow the native-app rule. Write an implementation plan with one section per item. For each, name the files you will change and how you will verify the result: 1. Layout from 320 to 430 px width, safe-area insets on fixed bars, 44 px touch targets, no hover-only controls. 2. Auth inventory: every provider and every popup-based flow. Plan Sign in with Apple where another social login exists. Do not replace the Google flow yet; list the options. 3. Account deletion: settings action, server-side deletion of data and the auth user, sign-out, confirmation screen, public /delete-account page. 4. /privacy and /terms written from what the code really collects, linked from settings and the footer. 5. Loading, empty and error states with retry on every data screen. 6. isNativeApp() helper (user agent token WebViewGoldApp) and app-only removal of banners and badges. 7. One native feature beyond the website: an Enable notifications step after onboarding that calls registerpush:// in the iOS app, and saving onesignalplayerid on the user profile. 8. Secrets report: every key in client code and env files, classified as publishable or secret, with a fix for each secret. 9. Payment inventory only: where digital goods or subscriptions are sold. No changes. Run items in parallel only when they touch different files. When done, produce a walkthrough with browser screenshots at phone width and a list of what must be tested on a real device.
Which Antigravity surface for which job
| Surface | Use it for | Watch out for |
|---|---|---|
| Antigravity app | Parallel agents, worktrees, plan and walkthrough review, scheduled tasks | Two agents editing the same layout files; give each a separate area |
| IDE and extensions | Reading diffs line by line; editing Config.swift and Config.java next to the web code | Signing, archiving and uploading stay manual steps in Xcode or Android Studio |
| Antigravity CLI (agy) | Quick terminal sessions, scripts, review with the keyboard (Ctrl + R opens artifact review) | --dangerously-skip-permissions in a repository that has deploy scripts |
| Browser (/browser) | Click-through tests and recordings of your key flows | Desktop Chrome is not a WKWebView; popups and file pickers behave differently in the app |
| Scheduled tasks | A weekly report-only sweep of the production URL for broken links and console errors | Keep scheduled agents read-only; nobody reviews what they change at 3 a.m. |
Pitfalls
- A review policy that always proceeds. Fine for refactors, risky for auth, payments and data deletion, which are exactly the areas reviewers test.
- Rules that never load: a modular rule without frontmatter or with an unknown trigger is dropped without a warning.
- A Gemini API key from an AI Studio prototype left in the browser bundle. Move the call into a server function; the secrets guide has a scan you can run after every build.
- Merged worktree branches that were never deployed. The app shows whatever is live on the URL, not what is on your main branch.
- Trusting the browser walkthrough as a device test. Push, Face ID, camera uploads and the offline screen only exist in a real build.
- Letting an agent rename the bundle ID or Android package by text replacement. Do it once, in the IDE; see why it cannot change later.
Checklist before you submit
- The native-app rule (or AGENTS.md) is committed and the agent can repeat its key points.
- The plan artifact for the store pass was reviewed and every item is either done or consciously deferred.
- Production URL on your own domain; /privacy and /delete-account load directly.
- The walkthrough covers sign-up, sign-in with Apple, account deletion and an error state.
- A TestFlight build and a Google Play internal testing build were installed on real phones.
- The App Store readiness check and the Play Store readiness check pass for your URL.
Frequently asked questions
Can Antigravity build the iOS and Android apps itself?
It can edit any code, and there is even an Xcode extension, but a store app still needs a native project, signing, an archive and an upload. WebViewGold supplies the native projects; you build them in Xcode and Android Studio or with the Cloud Builder.
Is Antigravity CLI the same as Gemini CLI?
No. Antigravity CLI (agy) is the successor Google moved free, Google AI Pro and Google AI Ultra users to on June 18, 2026. It keeps core ideas such as skills, hooks and subagents, and it reads AGENTS.md as well as GEMINI.md.
Should I use AGENTS.md, GEMINI.md or .agents/rules?
All three work. AGENTS.md is the most portable because Codex, Cline, Kiro and others read it too. Use .agents/rules when you want several small rules with different triggers, and remember the frontmatter.
I came from Firebase Studio. What changes?
Only the editor. Google disabled new Firebase Studio workspaces on June 22, 2026 and shuts the product down on March 22, 2027; Firestore, Authentication and App Hosting keep running. Export the project, open it in Antigravity and keep deploying to the same backend so your URL stays the same.
Can the browser agent test my app inside the WebView?
No. It drives Chrome on your computer, which is close to, but not the same as, the WKWebView and Android WebView in your app. Use it for flows and layout, then test native features on a device.
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.
Cloud 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.