Teaching Claude to QA a Mobile App: Android in 90 Min, iOS in 6 Hours
Christopher Meiklejohn just published a detailed account of teaching Claude to automate QA for Zabriskie, his solo-built community app. The story reveals a stark truth about mobile development in 2026: Android took 90 minutes. iOS took over 6 hours.
The gap isn't about complexity. It's about tooling philosophy. Android gives you a WebSocket and says "do whatever you want." iOS gives you a locked door and a note that says "please use Xcode."
The Problem: Capacitor's Testing No-Man's-Land
Meiklejohn built Zabriskie alone — no team, no investors. He used Capacitor to wrap his React web app in native shells for iOS and Android. One codebase, three platforms.
But Capacitor creates a testing gap:
- Playwright can't reach inside — it's not a browser tab, it's a native app
- Native frameworks can't interact — XCTest and Espresso see HTML inside a WebView, not native UI elements
You're too native for web tools and too web for native tools. Every screen had to be manually tested. Until Claude got involved.
Android: The Chrome DevTools Protocol Breakthrough
The key insight: Capacitor apps run inside an Android WebView, and WebViews expose a Chrome DevTools Protocol socket. Find it, forward it, and you have full programmatic control:
With CDP, authentication is one WebSocket message — inject a JWT into localStorage and navigate to the feed. Navigation is another message. No coordinate guessing, no UI interaction, no fighting with keyboards or dialogs.
The result: A Python script that sweeps all 25 screens in 90 seconds, takes screenshots, analyzes them for issues, and files bug reports to the production forum — all before anyone's had coffee.
iOS: The Fortress of Compounding Restrictions
Meiklejohn figured iOS would be straightforward. Same app, same screens, the Simulator is right there on the Mac. What followed was "one of the most absurd debugging sessions I've had."
You Can't Type an Email Address
The login form has type="email" on the input. AppleScript's keystroke "@" sends Shift+2, which the Simulator interprets as a keyboard shortcut. Every attempt to type @ switched the form to Sign Up, navigated to Forgot Password, or opened a context menu.
The fix: modify the backend to accept username OR email, change the form to type="text", and create a test user named "qatest". A backend modification to work around a keyboard limitation.
You Can't Dismiss Native Dialogs
Upon login, iOS shows a "Would Like to Send You Notifications" dialog rendered by UIKit, not the WebView. Native iOS dialogs cannot be dismissed by any form of macOS-synthesized input.
Meiklejohn tried everything: AppleScript clicks, cliclick at every coordinate, Python Quartz events, accessibility tree queries, simctl commands. The dialog sat there, immovable.
The fix: write directly to the Simulator's TCC.db — the privacy permissions database — inserting a pre-approval for notifications, then restarting SpringBoard. Timing matters: it has to happen before installing the app.
The Fundamental Gap
Apple's WKWebView doesn't expose Chrome DevTools Protocol. Safari Web Inspector uses a proprietary binary protocol that only Safari speaks. There's no bridge for automation tools.
Android authentication:
ws.send('{"method":"Runtime.evaluate","params":{"expression":"localStorage.setItem(\'token\',\'xxx\')"}}')
iOS authentication:
Uninstall app, write to TCC database, restart SpringBoard, reinstall app, launch, wait 5 seconds, tap Sign In at specific coordinates, wait, tap Email field, type "qatest" via AppleScript, press Tab, type password, press Return, wait, hope.
The Lessons
Meiklejohn's post is packed with practical takeaways for anyone building mobile apps:
- CDP over taps. Don't fight coordinate systems if you can use the browser's own debugging protocol. Android gives you this for free. iOS doesn't.
- Measure, don't guess. The accessibility API that finally made iOS navigation work is the same principle as checking logs before forming theories. Ask the system where buttons are.
- Stay in the worktree. Isolation only works if you respect boundaries. The moment you step outside "just for a quick look," you're one command away from committing unrelated files.
- Run tests before you push. Three rounds of push-and-pray before doing what should have been step one.
What This Means for Indie Hackers
Both platforms now have working QA skills. Every morning, the Android emulator and iOS Simulator boot up, sweep 25 screens each, analyze screenshots, and file bug reports for anything that looks wrong.
For solo builders, this is the future: AI agents that handle the tedious work of QA, letting you focus on building. But the path to that future is much smoother on Android than iOS.
"Apple, if you're reading this: please expose CDP or WebDriver for Simulator WebViews. The developer tools are great when a human is using them. They're nearly useless when an AI is trying to."