March 22, 2026
From bot farms to bug hunts
Teaching Claude to QA a mobile app
Solo dev’s AI tests his app: Android is easy, iOS is agony — commenters clash on “hack vs. use tools”
TLDR: A solo dev taught an AI to test his app, breezing through Android but wrestling with iOS. Commenters split between cheering a clever hack, warning about automation mishaps, and asking why he didn’t just use existing tools like Appium — a lively debate that matters to anyone shipping mobile apps fast.
A lone builder taught an AI helper to test his community app across web, Android, and iOS — and the internet instantly turned into the peanut gallery. The jaw-dropper: Android took 90 minutes, while iOS ate six hours. Cue the meme storm: “Android = easy mode, iOS = boss fight.” Even funnier, the dev tried asking the AI for a Grateful Dead lyric and got blocked because “dead” tripped a filter. You can’t make this up.
The method itself is scrappy: because the mobile app is basically a website in a wrapper, he tapped into the Android browser controls to drive screens, take screenshots, and let the AI file bug reports. That’s when the comments split.
One camp sees bot farm vibes, with users picturing racks of naked phone guts clicking away. Another camp screams “reinventing the wheel!”, pointing to existing tools like Appium and WebdriverIO — even dropping an official Ionic reference example link. Then there’s the automation caution squad, warning that unattended runs can “commit in the wrong place” and turn into 9 a.m. oopsies.
So is he a hacker hero or skipping the boring best practices? The crowd can’t agree — but they’re all watching to see if the AI can actually be the QA intern of his dreams.
Key Points
- •A solo developer built Zabriskie as a cross-platform app using Capacitor to run a single React codebase on web, iOS, and Android.
- •A server-driven UI (layouts as JSON) enables rapid updates without waiting for App Store reviews.
- •Web testing is covered by 150+ Playwright E2E tests, but mobile automation required a new approach because Playwright, XCTest, and Espresso can’t fully interact with WebView content.
- •On Android, automation leveraged adb reverse and forwarding the WebView’s CDP socket; through CDP, the system injected a JWT, navigated pages, and captured screenshots, sweeping 25 screens in ~90 seconds.
- •iOS automation took significantly longer (over six hours), underscoring a tougher tooling landscape compared to Android; an initial attempt to have Claude fetch song lyrics was blocked by content filtering.