Skip to content
Developer toolsNew techTop 28% of today's analysed ideas

AI-agent QA automation for real iPhones

Build a hosted QA-and-automation layer on top of this MCP iPhone-control server: developers describe test flows or repetitive tasks in natural language, and an AI agent executes them on a real iPhone (no jailbreak, no emulator drift) and returns a report or recording. Target indie iOS developers and small QA teams who cannot afford Appium/BrowserStack-style device farms but need real-device regression testing or app-store screenshot/demo automation.

Original post

What to build

A hosted QA automation service built on the poki MCP server: indie iOS developers describe test flows in plain English (e.g. 'sign up, add item to cart, checkout'), and an agent runs them on a real, non-jailbroken iPhone, returning a pass/fail report plus a screen recording.

poki proves AI agents can already drive a real iPhone with no jailbreak; wrapping that in a hosted, natural-language QA layer turns a dev tool into a product indie iOS teams can pay for instead of building themselves.

Demand

Indie iOS developers and small QA teams who can't justify BrowserStack or Appium device-farm pricing want cheap real-device regression testing, and poki's traction shows builders are already experimenting with AI-driven device control.

  • GitHub (JosssphZhou/poki)Product launch

    1270 stars on a Swift repo for a local MCP server/agent that lets AI agents operate a real iPhone with no jailbreak and no extra hardware; listed as top/high engagement on GitHub trending.

Stack

  • poki MCP server
  • Claude Agent SDK or OpenAI function calling
  • Fastify or Supabase Edge Functions for the backend
  • Postgres/Supabase for run history
  • S3-compatible storage for screen recordings
  • Stripe for billing

Solo + AI difficulty

Easy: the hard device-control problem is already solved by poki, so MVP is mostly a job queue, a prompt-to-action translator, and a report UI; doable in 3-4 weeks. Hard: provisioning and securing a fleet of real physical iPhones per customer, and keeping agent actions reliable enough for CI use; scaling past a handful of devices likely takes 2-3 months.

Entry threshold
The wrapper software is a weekend build for a solo developer with AI, but turning it into a multi-tenant SaaS requires owning or renting physical iPhones to host, which adds real hardware cost and operational overhead beyond pure code.
Window
6-12 months

Where to find first users

  • r/iOSProgramming
  • Indie Hackers
  • Product Hunt launch
  • iOS developer Discord/Slack communities

Competitors

Counter-signals & risks

  • Local-only MCP server architecture may not scale easily into a hosted multi-tenant QA service without significant re-engineering for device farm orchestration, security, and isolation.

  • Apple's terms of service or anti-automation protections could restrict or disrupt non-jailbreak device control methods at scale, especially in a commercial hosted offering.

  • Established players (BrowserStack, Appium, Sauce Labs, Apple's own XCTest/XCUITest) could rapidly add similar natural-language AI-agent automation features, eroding the differentiation of a new entrant.

Original title: JosssphZhou/poki: Let AI agents operate a real iPhone. Local MCP server and agent, no jailbreak, no extra hardware.

  • Developer tools#4

    MCP Connector Library for AI Coding Agents

    Build a ready-made MCP (Model Context Protocol) server or toolkit that connects Claude, Cursor, and Codex to popular third-party APIs and services, enabling AI coding agents to automate integrations without manual glue code. Package it as a hosted service or CLI tool targeting solo developers and small teams who use AI-first IDEs. Monetize via subscription access to a growing library of pre-built MCP connectors.

    Demand
    7/10
    est.
    Buildability
    7/10
    est.
    Competition
    7/10
    est.
    via Product Hunt
    22 competitors
  • Developer tools#7

    Plan State Persistence Layer for Claude Code Re-Runs

    Build a lightweight plan persistence and idempotency layer for Claude Code that tracks executed plan steps, stores state between runs, and prevents duplicate actions on re-runs. Target solo developers and small teams using Claude Code for multi-step agentic workflows who lose progress when sessions restart or plans re-execute from scratch.

    Demand
    6/10
    est.
    Buildability
    8/10
    est.
    Competition
    8/10
    est.
    via Product Hunt
    11 competitor
  • Developer tools#8

    Developer Context Save and Restore Tool as Micro-SaaS

    Build a lightweight SaaS or CLI-plus-web-app called something like Park that lets developers save and restore full work context — open files, terminal state, branch, notes, clipboard snippets — across multiple repos and machines. Sell it as a subscription to solo developers and small teams who constantly context-switch and lose their train of thought. Integrate with VS Code and JetBrains as a plugin for frictionless adoption.

    Demand
    1/10
    measured
    Buildability
    7/10
    est.
    Competition
    6/10
    est.
    via Hacker News
    33 competitors
AI-agent QA automation for real iPhones — Nichr