Drizz is an AI-powered mobile test automation platform built around intent-based testing. Simply describe what you want to test in plain English, Drizz executes it on a real device using Vision AI and automatically authors a reusable test case. No scripting, no flaky selectors, no manual maintenance. It adapts to dynamic UIs, integrates with your CI/CD pipeline, and gives your team reliable end-to-end coverage without the overhead.
When you write a test intent for iOS, does Drizz reuse that same intent to run on Android too, or do you author separately per platform? Curious whether the vision layer handles the UI differences automatically or if there’s still some per-platform config involved.
intent-based testing is the right abstraction here. one question: if the UI shifts but the intent doesn't (new onboarding screen, reordered step), does it auto-reconcile or do you redo the test? that's where most vision-ai tools fall apart for us.
Do you expose test results as structured data? I want to pipe results into our data warehouse for trend analysis. Like test pass rates over time, most-failing flows, etc.
The no flacy slectors promise is honestly the most compelling part here mobile UI tests are notoriously painful to maintain at scale. Really curious to see how Drizz performs on fast-moving apps with frequent UI changes and complex flows.
This is basically what mobile QA has been missing for years moving from brittle selectors to intent is a big shift. The real test will be CI reliability over time, but if it holds up, it could seriously reduce maintenance overhead for teams shipping fast.
We just closed our seed round and mobile is our first platform. Haven't set up testing yet. Is it too early to start with Drizz or should we wait until we have more features built?
I prototype in SwiftUI and sometimes my prototypes become the actual production code. Having tests would be great but I don't have time to write Appium scripts. Could I literally test my prototype with Drizz before handing it to the dev team?
I'm on the customer support team, not engineering. When users report bugs, I can never reproduce them. Could I use Drizz to set up reproduction steps?
this is a great app. and also I want to test it out in my computer to know how it works. anyway, where's the link for me to download this app?
This looks like a game changing for the mobile app testing. it's been a pain to update the test cases everytime some changes happens to the ui. Writing intent and the let the drizz take over test generation and execution is amazing use of AI. Can I modify and save the test case steps after they are generated from intent ? for example, I want to change only one specific steps form entire test steps will it allow and remeber next time whenever I write the same intent ?
We have regulatory requirements around audit trails. Every test execution needs to be traceable back to who ran it, when, what version of the app, and what passed or failed. Do you store execution history and is it exportable?
Noob vibe-developer here, currently testing the most annoying part of the building process lol. Excited to try this out!
I also liked that it runs on real devices because that’s where most testing issues actually show up 😅.
Congrats to the whole Drizz team on the launch 🚀!
Tried Drizz last month after a friend recommended it. Worked surprisingly well on our app — the onboarding tutorial inside the product could use a polish (got a bit lost on step 3) but once you're past that it's smooth.
The team is super responsive on Slack. That counts for a lot this early.
I'm building a couples app on iOS, and my whole testing setup right now is XCUITest on simulator + manual checking, archived to TestFlight by hand. Probably the exact cohort that'd never write Appium tests but might genuinely try this. The question I'd love your take on: with Vision AI driving execution, how do you keep tests deterministic across CI runs? Selectors fail predictably...locator doesn't exist, you fix it. A vision model can fail by misreading a screen state on one run and reading it correctly the next, which feels harder to debug. And there's a scary version of "self-healing" where the AI silently re-interprets what success means. What's the rerun / confidence story, and where do you draw that line?
Congrats on the launch!
"Testing was a tax, not a tool" is a great line, and the 12px button story is painfully relatable. As a fellow builder in the automation space, I love that you went vision-first. Brittle XPaths have wasted more of my life than I'd like to admit.
Congrats on the launch, Yash, rooting for the whole team 🚀
“Mobile tests that write, run, and fix themselves”
Drizz launched on Product Hunt on May 19th, 2026 and earned 322 upvotes and 55 comments, earning #2 Product of the Day. Drizz is an AI-powered mobile test automation platform built around intent-based testing. Simply describe what you want to test in plain English, Drizz executes it on a real device using Vision AI and automatically authors a reusable test case. No scripting, no flaky selectors, no manual maintenance. It adapts to dynamic UIs, integrates with your CI/CD pipeline, and gives your team reliable end-to-end coverage without the overhead.
Drizz was featured in Developer Tools (512.6k followers), Artificial Intelligence (468.8k followers) and No-Code (5.7k followers) on Product Hunt. Together, these topics include over 167.2k products, making this a competitive space to launch in.
Who hunted Drizz?
Drizz was hunted by Rohan Chaubey. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Drizz stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Rohan Chaubey
When you write a test intent for iOS, does Drizz reuse that same intent to run on Android too, or do you author separately per platform? Curious whether the vision layer handles the UI differences automatically or if there’s still some per-platform config involved.