Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

Claude Code to the app stores

What to test before you submit: a testing strategy for Claude Code web apps in a native shell

Before a submission you do not need a large test suite. You need proof that the flows a reviewer will try work on a phone-sized screen, with a bad connection and from a fresh install. Claude Code can write and run most of these tests, and a person with a real device covers the rest.

Free 15-minute call with our team, or call +49 761 519 751 50 (24/7, English + German)

  • Approval guarantee – or money back within 14 days
  • No coding needed
  • One-time payment, free updates
  • 24/7 human support
  • Made in Germany since 2014 · ISO 27001

Four things worth testing

Mobile viewport flows

Sign-up, the main feature and settings at phone width: nothing overflows, no button sits off screen, no step depends on hover.

Auth flows

Register, sign in, sign out, reset the password, delete the account. Check that the session survives a reload, because users expect an app to keep them signed in.

Offline and error behavior

Requests that fail or time out must end in a message with a retry, never in an endless spinner or a blank page.

The reviewer's path

Fresh state, the demo account from the review notes, every tab once, the purchase screen, account deletion. If only one test exists, it should be this one.

How the agent writes and runs them

Ask Claude Code for end-to-end tests with a browser automation framework that can emulate phones, preferably the one your project already uses. The tests start from the command line, and that is the point: the agent runs them, reads the failures, fixes the cause and runs them again, without you relaying error messages.

Three rules keep the suite useful. Keep it short: a handful of flows, not every screen. Use dedicated test accounts and seed data, so a test never depends on what happened yesterday. And make the agent explain a failing test before it changes one, because a test that was edited until it passed proves nothing. If you want the agent to drive a browser interactively as well, the MCP page covers that connection.

What a browser test proves, and what only a device shows

AreaBrowser testReal device
LayoutOverflow and hidden controls at phone widthsNotch, home indicator, keyboard covering inputs
LoginEmail login and session persistenceGoogle sign-in inside the WebView, the Sign in with Apple sheet
OfflineYour own error states with the network blockedThe native offline screen in airplane mode
PushThe opt-in screen and its logicThe permission prompt and an actual notification
PurchasesPaywall and entitlement checksA sandbox purchase and a restore

The device pass a person does

  1. Install the way users will

    Use TestFlight and the internal testing track, not a build pushed over a cable. The beta testing guide explains both.

  2. Walk the reviewer's path from a fresh install

    Delete the app first. Sign in with the demo account exactly as written in your review notes.

  3. Break the connection

    Airplane mode at launch and in the middle of a flow. Then switch it off and check that the app recovers; details are in the offline guide.

  4. Leave and come back

    Send the app to the background, open a link to your domain, return after a while. You should still be signed in and on a sensible screen.

  5. Repeat on a second form factor

    A small phone and, if the app supports it, a tablet. Write down what you tested, so the team knows what the release was checked against.

A prompt for the reviewer path test

Prompt for Claude Code
Write one end-to-end test called reviewer-path with the browser test framework this project uses (propose one if there is none). Emulate a current iPhone and a mid-size Android phone.

The test starts with empty storage, signs in with the demo account from docs/store-review.md, opens every item of the main navigation once, opens the paywall if there is one, opens settings and checks that the privacy policy link and the delete account action are reachable. It fails on any console error, any failed request and any screen that scrolls horizontally.

Run it. For each failure, explain the cause before you change anything, and never weaken an assertion to make the test pass.

Frequently asked questions

Which test framework should Claude Code use?

The one your project already has. If there is none, pick a browser automation framework with phone emulation that runs from the command line, so the agent can start it itself.

Is a simulator enough, or do I need a real phone?

Simulators and emulators are fine for layout. Notifications, purchases, biometric prompts and the on-screen keyboard need at least one pass on a real device before you submit.

Should these tests run on every deploy?

Yes, the short suite should. After launch every deploy reaches the installed apps at once, so the reviewer path test doubles as a release gate.

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 page

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 demo

Full 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 WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Talk it through with our team

Free 15-minute call: your app, your tools, your next step

Rather start right away? See plans and pricing or hand it over with Full Service.