1. Describe the fix
Open the Code tab, pick the repository and branch, and describe the problem like a bug report: which screen, which device, what you expected. The prompt below is a good pattern, and dictating it works fine.
Why this works so well for WebViewGold apps
The App Store and Google Play binaries contain the native shell: the URL, the name, the icon, the permissions and the features you switched on. Your screens, texts, flows and bug fixes live in the web app. When you deploy the web app, both store apps show the new version on their next load, with no new build and no review wait. "Fix the app" becomes "fix a website", and a website can be fixed from anywhere.
Claude Code on the web, at claude.ai/code, runs each task in a cloud session: a fresh virtual machine with your GitHub repository cloned into it, where Claude edits files, runs your build and tests, and pushes a branch. The Claude app for iOS and Android reaches the same sessions in its Code tab. Sessions keep running when you lock the phone, and you can pick them up later on any device. You need a paid Claude plan that includes Claude Code and a repository on GitHub.
One-time setup
Do this once at a computer; after that, your phone is enough.
Deploy from Git
Connect the repository to Vercel, Netlify or Cloudflare Pages so the main branch deploys to production and every pull request gets a preview URL. Merging becomes your deploy button, and the cloud session never needs a deploy token.
Connect GitHub to Claude
Open claude.ai/code and authorize the Claude GitHub App for the repository. If you already use the GitHub CLI,
/web-setupin a terminal session of Claude Code is an alternative.Check the cloud environment
The Default environment has Trusted network access: package registries and GitHub are reachable, arbitrary hosts are not. That is enough to install dependencies, build and test. Do not put secrets into its environment variables; everyone who uses the environment can read them.
Install dependencies automatically
Add the SessionStart hook below to
.claude/settings.jsonand the small script next to it, so every cloud session starts withnode_modulesin place. On your own machine the script does nothing.Commit your project context
Cloud sessions read the repository's CLAUDE.md,
.claude/settings.json, commands, skills and subagents. The CLAUDE.md template and the localhost guard hook protect you on the phone exactly as they do at your desk.Install the Claude app
Install the Claude app on your iPhone or Android phone, sign in with the same account and open the Code tab. Your repository should appear when you start a new session.
The SessionStart hook in .claude/settings.json
The PreToolUse block is the localhost guard from the release guide; both hooks live in the same file. $CLAUDE_PROJECT_DIR always points at the repository root.
json
{
"hooks": {
"SessionStart": [
{
"matcher": "startup|resume",
"hooks": [
{
"type": "command",
"command": "bash \"$CLAUDE_PROJECT_DIR\"/scripts/cloud-setup.sh"
}
]
}
],
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/guard-native-config.sh",
"timeout": 30
}
]
}
]
}
}
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 :-)
scripts/cloud-setup.sh
The CLAUDE_CODE_REMOTE check keeps it from running locally, and the node_modules check skips the install when it is already there.
bash
#!/bin/bash
# scripts/cloud-setup.sh
# Runs at the start of every Claude Code session; does nothing on your own machine.
[ "$CLAUDE_CODE_REMOTE" = "true" ] || exit 0
cd "$CLAUDE_PROJECT_DIR" || exit 1
[ -d node_modules ] || npm ciThe loop from your phone
2. Let it work
Claude edits, builds and tests in the cloud VM. Lock the phone if you like; the session keeps running, and you answer its questions when you come back.
3. Review the diff
Open the Changes card and tap the line counts to see the diff. Comment on single lines and send the comments with your next message if something is off.
4. Open the pull request
Let Claude create the pull request. Your host builds a preview deployment, and the store-readiness check in GitHub Actions comments on store risks.
5. Check the preview, merge
Open the preview URL in your phone's browser and try the fixed flow, then merge in the GitHub app or the browser. The merge triggers the production deploy.
6. Confirm in the store app
Close the WebViewGold app completely and reopen it. It loads the new production version, and so do your users' apps on their next launch.
A bug report that works from a phone
Concrete screen, device and expectation, one clear fix direction, the checks to run and a boundary ("nothing under native/"). That is all a cloud session needs.
Type or dictate in the Code tab of the Claude app
Production bug in the iPhone app (a WebViewGold app that loads https://app.example.com): on the checkout screen, the Pay button sits behind the home indicator on iPhone 15 and newer. Expected: the whole button is visible above the home indicator, as it is in Safari. Fix it with env(safe-area-inset-bottom) padding on the fixed checkout bar, keep the desktop layout unchanged, and check whether any other fixed bottom bar has the same problem. Run npm run lint and npm run build. Commit on a new branch and open a pull request with a three-line description I can read on my phone. Do not change anything under native/.
Deploy or store build?
| Change | Ships with a web deploy | Needs a new store build |
|---|---|---|
| Layout fixes, texts, new screens and flows | Yes | No |
| A new button that uses a bridge feature you already switched on, such as the share sheet | Yes | No |
| Switching on a new native feature, push provider or permission | The web part only | Yes: Config.swift, Config.java, Info.plist or AndroidManifest.xml change |
| A new production domain or start URL | No | Yes, the URL is compiled into the app |
| App name, icon, splash screen | No | Yes |
| New in-app purchase products | The web part only | Products in App Store Connect and the Play Console, plus a build if the native config changes |
| A new WebViewGold version | No | Yes |
When you need your own computer after all
Cloud sessions run on Linux virtual machines. They have Node.js, Python, Java and Gradle, but no Xcode and no Android SDK, so they cannot build the native apps. For a native change you have three options. Start Claude Code with claude remote-control on your Mac and drive that local session from the Code tab; the work and the build tools stay on your machine. Hand the build to the Cloud Builder, which builds and uploads both apps from a browser. Or plan it for your next session at the desk.
Two more handoffs are worth knowing. In the Claude app you can tell Claude to watch a pull request and fix CI failures or review comments as they come in; this auto-fix needs the Claude GitHub App on the repository. And back at your computer, claude --teleport pulls a cloud session, branch and conversation included, into your terminal. For the complete picture of what needs a store release, see web vs native changes after launch.
Checklist for a safe deploy from your phone
- The preview deployment works in your phone's browser for the flow you changed.
- Lint, build and the store-readiness check are green on the pull request.
- Nothing under
native/changed; otherwise, plan a store build. - You know where the instant rollback is in your hosting dashboard.
- HTML is served with short cache headers and assets have hashed file names, so the apps fetch the new version on the next launch.
- You open the real app yourself after the deploy.
Pitfalls
- Merging without a preview. The store apps show production immediately. One look at the preview URL on your phone is cheaper than a hotfix.
- Secrets in the cloud environment. Its environment variables are visible to everyone who uses it. A UI fix does not need production secrets, and deploy secrets stay with your hosting provider.
- Blocked network calls. Trusted access allows package registries and GitHub, not your staging API. If tests need it, add your domain with Custom network access.
- Aggressive caching. If your HTML or a service worker caches old bundles, users keep seeing the old version until a reload. Ask Claude once to check the cache headers and the service worker update logic.
- Expired sessions. An idle cloud session eventually releases its VM. Reopening it restores the conversation but not running processes, so ask Claude to rerun the build if needed.
- Shared limits. Cloud sessions count toward your plan's usage like any other Claude Code work, and parallel sessions use it up faster.
Frequently asked questions
Do I need a laptop to ship a fix this way?
Not for web app changes: the Claude app, GitHub and your hosting provider are enough. For changes to the native shell you need a Mac for Xcode, a computer for Android Studio, or the Cloud Builder in a browser.
Which Claude plans include cloud sessions?
At the time of writing, cloud sessions are part of the paid plans that include Claude Code (Pro, Max, Ultra and Team) and of Enterprise seats with Claude Code. Check Anthropic's current plan page, since this changes.
Do users have to update the app from the store to get the fix?
No. The WebViewGold apps load your production URL, so the fix appears on the next launch or reload. Only changes to the native shell need a store update.
Is it allowed to change an approved app without a new review?
Updating content and fixing bugs in your web app is normal for web-based apps. Changing the app's purpose or adding features that break the guidelines is not, and the next native update is reviewed against the current web app.
Can Claude deploy to production directly from the cloud session?
It is better not to. Let Claude open a pull request and let your hosting provider deploy on merge. That keeps deploy credentials out of the session and gives you a review step on your phone.
Does the Android app update the same way?
Yes. Both apps load the same production URL, so one merge updates iOS and Android at the same time.
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.