Launched this week
QApilot's CoWork
3x Mobile Automation. Same QE Team.
636 followers
3x Mobile Automation. Same QE Team.
636 followers
CoWork turns existing test cases into executable mobile automation with AI planning, human-approved replanning, and real-device execution on iOS, Android, and Flutter.
Interactive
Payment Required
Launch Team / Built With
Humalike
Is agent behaviour humanlike? Or it feels more like an executioner? Congrats on the launch!
QApilot's CoWork
@mcarmonas That's an interesting question. I’d say it’s intentionally a mix. CoWork behaves humanlike in how it understands intent, reads app context, and adapts when the flow changes. But it executes with the discipline of an automation system.
So it’s not just a blind executioner, and it’s not trying to “pretend” to be human either. When it’s confident, it moves. When it needs judgment or input, it asks.
Thank you!
Oxlo.ai
Congrats on the launch guys!!
Nice idea! Is the generated automation framework-agnostic, or does it target a specific testing framework?
QApilot's CoWork
@barath_kanna_bk Hello Bharat. Thank you! On a fundamental level, all the automation is an Appium Script. However, Appium notoriously falls short for quite a few use cases, especially on Flutter. We also built a middleware on top of Appium to handle the limitations. So, in essence, it's a combination of Appium and QApilot middleware.
Oxlo.ai
@charan_tej_kammara Makes sense.
Appium alone has its limitations, so building a middleware layer is a smart approach.
QApilot's CoWork
@barath_kanna_bk Precisely. Thanks for sharing your thoughts.
Wow. Nice one. Do it have the same operational function for web? How variety of the test cases this cover?
QApilot's CoWork
@mark_ph_m Hello Mark. Thank you. We've built QApilot's CoWork specifically for mobile application testing. It is capable of testing web views within mobile apps. That is the extent of our focus.
How would this compare to doing UI automation testing with a tool like Selenium or CypressJS
QApilot's CoWork
looks cool! can it work on my local device?
QApilot's CoWork
I really like that this project still treats humans as a fundamental part of the QA process.
QA is extremely delicate. AI can be useful for speed and execution, but it still tends to get confused, assume things, or hallucinate its way through uncertainty.
So the human-approved replanning part makes a lot of sense to me. I’d much rather have the system pause and ask when something changes than confidently continue with a broken or misleading test.
Curious how you think about trust over time: how do QA teams review what the AI changed, and how do they decide when an approved adaptation should become part of the test suite?
QApilot's CoWork
Hey builders 👋
I am one of the makers behind CoWork!
We built CoWork - an AI agent that drives real mobile apps step by step, planning each action, reading the screen, and adapting when things go off-script.
We kept hitting the same wall: mobile automation breaks the moment a layout shifts. So we wanted something that actually sees and reasons about the screen instead of leaning on brittle scripts.
We'd love your feedback and support. Drop your thoughts/questions in the comments below and one of us will reply!