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

Release quality

QA for agent-built apps: what the agent can test and what needs a person with a phone

A coding agent will write tests, run them and report green. That covers logic. It does not cover whether the login survives a real iPhone, whether the keyboard hides the submit button or whether the app shows a white page in a tunnel. Store reviewers will run into exactly those things, so test them first.

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

Two kinds of testing, two kinds of tester

Split QA by who can do it reliably. Everything that can be written as "given this input, expect that output" belongs to the agent: it is fast, it does not get bored, and it can run the suite after every change. Everything that depends on a device, a network, an operating system dialog or human judgment belongs to a person.

The mistake to avoid is counting the first kind as proof of the second. A passing test suite says the code does what the tests say. It says nothing about what a reviewer sees after tapping the icon.

What agents test well

Unit and API tests

Business rules, validation, calculations, permission checks on endpoints. Ask for tests with every change and read the assertions: a test that cannot fail proves nothing.

Browser flows

End-to-end tests in a headless browser at a phone-sized viewport: sign-up, login, the main task, logout.

Data rules

Scripts that try to read or change another user's records and expect to be refused.

What needs a person and a real device

  • Login inside the app. Google login, Sign in with Apple, magic links and password reset emails behave differently in a WebView than in a desktop browser.
  • Keyboard and safe areas. Inputs covered by the keyboard, buttons under the home indicator, content behind the notch.
  • Bad networks. Airplane mode at launch, a lost connection in the middle of a form, a return from the background after a long pause.
  • System dialogs. Permission prompts for notifications, camera or location, including what happens when the user says no.
  • Push notifications. Arrival on a locked phone, and the screen that opens on tap.
  • Purchases. A sandbox purchase, a cancelled purchase and a restore.
  • The first impression. Does it feel like an app or like a website in a frame? That judgment is what Guideline 4.2 comes down to.

A device test pass before you submit

Use a test build from TestFlight or a Google Play testing track, not the browser.

  1. Install fresh

    Delete any old build, install the test build and open it on mobile data. Watch the first seconds: a splash screen should cover the wait, never a blank page.

  2. Walk the reviewer's path

    Create a new account, complete the main task once, log out, then log in with the demo account the reviewers will get. Write that path into the review notes.

  3. Break the network

    Switch on airplane mode, open the app, tap around, switch it off again. You should see an offline screen and a clean recovery, never a browser error.

  4. Say no to everything

    Decline every permission prompt and check that the app still works and explains what is missing.

  5. Delete the account

    Use the in-app deletion and confirm that the login no longer works afterwards.

  6. Repeat on the other platform

    Run the same pass on Android, using the system back button, and on a small and a large screen. Write down every finding as a task for the agent.

Frequently asked questions

Is the simulator or emulator enough for testing?

It is fine for layout work, but not as the final check. Push notifications, biometric login, the camera, purchases and real network conditions should be tested on a physical device.

How many devices do I need?

One current iPhone and one Android phone are the minimum. Add a small-screen phone, and a tablet if your app supports tablets.

Does the Google Play closed test replace my own QA?

No. The closed test with 12 testers for 14 days is a requirement for new personal developer accounts. Use it to collect feedback, but run your own test pass first so testers do not hit obvious bugs.

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.