Sergey U

co-founder – Agentic QA automation for mobile apps

[Sergey U @ustnvs]

Stop manually testing your app before every release

We built agentic QA that just works:
- No code, no locators, no SDK.
- Supports iOS and Android, any framework (Native, React Native, Flutter).
- Works with local and cloud real devices.

Install the Mac app, plug in your phone, watch agents do the work

Wanna try? Comment "INTERESTED" and I'll send you free early access

[Sergey U @ustnvs]

I keep seeing the same thing in Flutter teams: pre-release testing becomes the bottleneck.

Flutter apps are testable, but the usual automation path is still harder than it should be because the UI is rendered differently from native apps. That's what makes pre-release testing slower and more manual than most teams want.

That's the problem we wanted to solve with our visual agent. It doesn't care about the element tree - it looks at the screenshot and acts on what it sees. That means there's no need to add accessibility IDs or other test-specific setup. You just describe what you want in plain English, and it does the rest.

[Sergey U @ustnvs]

Noticed a pattern: new agentic mobile QA tools are launching simulator-only.

Surprised me - every team we've talked to building noqa says they need real devices. Not because simulators are useless, but the scary pre-release stuff doesn't show up there. IAPs behave differently. Real hardware performance differs.

Building noqa, we had to choose: simulators only, or real devices too?

We went with both. Simulators for fast dev feedback. Real devices before release, when you need to know things actually work.

[Sergey U @ustnvs]

@thymikee whoa 2x faster - what's the secret sauce?

I'm building agentic QA for mobile apps with similar speed focus. We cache screens and steps, so reruns take 1–2s per action. There’s still a pause at the end (LLM verification) but the repeated steps are where the speedup really shows.

[Sergey U @ustnvs]

Shipping a broken paywall is the most expensive bug in mobile

The scariest bug you can ship isn't a crash. It's a broken purchase flow that nobody notices for days - while revenue bleeds out quietly, ad campaigns keep spending, and algorithms train themselves on data from users who were trying to buy but couldn't.

Most teams handle it the same way - manual testing before every release. One paywall is manageable, but they multiply - web funnels, subscription tiers, separate flows for different segments. It quietly becomes one of the bigger parts of the regression cycle.

We built noqa to automate exactly this. An agent that runs through purchase flows on its own - paywalls, system dialogs, subscription confirmations. You describe the goal in plain English, it does the rest.

The kind of thing that lets you ship on Friday without checking Slack all weekend.

Here's what it looks like in practice ↓

[Sergey U @ustnvs]

@vashchylau Our tool doesn’t generate autotests, it tests fully visual and just do actions from your text instructions. So you don’t need to write code or use testing frameworks at all.

[Sergey U @ustnvs]

Stop manually testing your app before every release

We built agentic QA that just works:
- No code, no locators, no SDK.
- Supports iOS and Android, any framework (Native, React Native, Flutter).
- Works with local and cloud real devices.

TRY IT FOR FREE

[Sergey U @ustnvs]

@unltdinvestor Its desktop app on Tauri

[Sergey U @ustnvs]

Explore more at https://t.co/kia7o45zvE

[Sergey U @ustnvs]

I built a QA tool that runs tests on real devices for any mobile framework.

No code, no locators, no SDK.

Install the Mac app, plug in your phone, watch agents do the work

[Sergey U @ustnvs]

We’re building https://t.co/kia7o45zvE specifically to address the last bottleneck in mobile app development: testing. Now you can run agents to test your app on real devices.

https://t.co/ngjB0TIZPy

[Romain Huet @romainhuet]

I really love building iPhone apps in Codex.

Codex can design the screens, write the Swift code with GPT-5.5, run the app in Simulator without opening Xcode, and even click around with computer use to test it!

[Sergey U @ustnvs]

What do you use to test your mobile app?

- Manual testing
- XCUITest
- Appium
- Something else?

[Sergey U @ustnvs]

@mecvk Sent the link in DM

[Sergey U @ustnvs]

Stop manually testing your app before every release

We built agentic QA that just works:
- No code, no locators, no SDK.
- Supports iOS and Android, any framework (Native, React Native, Flutter).
- Works with local and cloud real devices.

Install the Mac app, plug in your phone, watch agents do the work

Wanna try? Comment "INTERESTED" and I'll send you free early access

[Sergey U @ustnvs]

@kevinkern Looks good! By the way, I built the tool for testing apps on real devices without code. If you are intersted, I can share free early access

[Sergey U @ustnvs]

@Hartdrawss Thanks! It's free to try https://t.co/w3Ai7riDl8

[Sergey U @ustnvs]

@paulg I believe exactly the opposite.

Engagement matters, but mainly at the starting stage-so you don't abandon ship before the money starts flowing.

[Sergey U @ustnvs]

Build your app.
Test it.
Ship with confidence.
Iterate fast.
Let the data guide you.
Go dominate your market.

[Sergey U @ustnvs]

@sama Extracting UI element coordinates from screenshots to launch agents for visual testing of applications and websites. Right now only Gemini works good.

[Sergey U @ustnvs]

@billainsahu @yashhq_22 Thanks! We have a free 7-day trial, feel free to try it or ask me any questions about the product

[Sergey U @ustnvs]

@vladsiu Congrats! Let's connect

I'm building https://t.co/kia7o451G6 agentic QA for mobile apps to do less manual boring work on every release

[Sergey U @ustnvs]

@akramcodez I use Claude + Copilot Business, which still allows running Opus 4.6 with pay-per-request instead of per-token pricing