QApilot is an AI-native, autonomous testing platform purpose-built for mobile applications, helping teams create, execute, and maintain tests with far less manual effort.
It combines intelligent agents, context-aware automation, and mobile-first infrastructure to deliver faster test coverage, resilient automation, and greater release confidence.
We launched CoWork, a mobile app testing solution, on PH a while back and got a lot of useful feedback. Some of the most interesting comments came from developers who wanted to test their mobile apps before the merge, not after.
So we built QApilot MCP, that lets Claude, Cursor or Codex drive a real Android device. It launches Saturday.
We launched QApilot's CoWork on Product Hunt last week. We got amazing feedback, sharp questions, and an immense validation from the community that we are solving a real problem. A big thanks to the community for placing us at #2 product of the day.
Explore QApilot's CoWork here - https://qapilot.io/product/cowork. Happy to give a product walkthrough and offer free-trial for mobile app testing teams.
Reviewers say QApilot is most useful for mobile teams that want fast coverage without writing and maintaining lots of scripts. Users repeatedly praise CoWork for turning existing manual, Excel, natural-language, or BDD test cases into runnable device tests, while others like Crawler for quick happy-path exploration and Dual Device Testing for cross-app flows. A common theme is that it adapts to minor UI changes and asks for human approval when intent could drift, rather than masking failures. The main criticism is limited visibility, debugging detail, and fine-grained control.
We had a manual QA team running most of our regression through Excel-based test cases the problem was test steps in one place, execution in someone's head. CoWork mode was the thing that actually helped: it let us feed in our existing test cases instead of starting automation from scratch, so we weren't throwing away months of manual QA knowledge to get to automation. That "automate what you already have" angle is rare most tools assume you're starting fresh.
What needs improvement
Honestly, most of my hands-on time has been in CoWork, so I can't speak in detail to the Crawler, Record & Play, or dual device testing modes yet they're on the platform and worth checking out, but I'd rather not review what I haven't used. One thing I'd genuinely like improved: better visibility/documentation for teams like ours who are only using one mode, so it's clearer what the other modes would add before we invest time exploring them.
vs Alternatives
We looked at Appium (too much setup and maintenance overhead for a small team) and BrowserStack's own automation tooling (good device coverage, but not built around converting existing manual test cases). QApilot's CoWork approach to migrating from Excel-based cases was the deciding factor over both.
the "fails honestly instead of faking a pass" philosophy is what stands out. the maker explained in the launch comments that when the UI changes, CoWork replans against the current app state but anchors to the original intent of the step rather than the old UI path - if a new path could change what the test is actually validating, it stops and asks for approval instead of silently continuing. that distinction between adapting to harmless UI change versus letting a test drift into validating the wrong thing is exactly the failure mode that makes most mobile automation untrustworthy after a few releases.
What needs improvement
someone asked in the comments what percentage of failures actually need manual intervention versus recovering on their own in production, since that's what determines the real maintenance cost over time. the maker's honest answer was that they're tracking it internally but don't want to quote a broad number yet because it varies by app and flow. that's a fair answer for a 2-month-old product, but it's also exactly the number a team evaluating this for a sprint workflow needs before committing, so publishing even a rough range would help a lot.
TestMu AI markets itself as a full-stack agentic QE platform, which sounded like it covers more ground on paper. but QApilot's CoWork is scoped specifically to the mobile execution problem - turning test cases you already wrote into something that runs on a real device and knows when to stop and ask instead of guessing. for a QA team that already has test cases but low execution coverage, a narrower tool that's honest about its limits felt like a safer bet than a broader agentic platform still proving itself.
I liked most about QApilot is how quickly I could get into testing without spending a lot of time preparing everything first. I could give it the app and start checking real user flows pretty quickly. It was especially useful for catching issues across different screens and making sure the main journeys were working as expected.
What needs improvement
I’d like more options to fine-tune the tests before they run, especially around choosing specific screens or flows to focus on. More detailed failure reports would also make it easier to understand and reproduce issues.
vs Alternatives
I looked at traditional mobile automation approaches where I’d have to prepare test cases and scripts before getting started. That setup can take quite a bit of time, especially when I just want to check the main flows. QApilot felt more straightforward for that kind of testing.