📰 Dev.to · Sharmin Sirajudeen

No VC, no team, no timeline. Just curiosity and 6,300 lines of Rust.

Everyone asks why Rust instead of Python. The more interesting question is why not C or C++. Here's what drove that decision — and what I'd do differently.

The evolution from manual ADB commands to AI-driven mobile testing.

AI agents can write perfect code but can't tap a button on a real device. I built an MCP server to bridge that gap — here's how Drengr gives Claude eyes and han

After ten years of writing Android UI tests that broke every sprint, I started building something different. Turns out researchers at Google, Meta, Microsoft, a

I pointed Drengr's autonomous agent at three different apps and let it run for a week. It found a bug I'd missed for months, flagged an accessibility issue, and

Every AI agent project is Python. LangChain, CrewAI, AutoGen — Python everywhere. I went with Rust. Here's the honest reason, and what it cost me.

Cellebrite paid $170M for device virtualization. The next layer — AI-driven actuation on real phones — is the gap Drengr fills.

Google's FunctionGemma dispatches to pre-defined functions. Drengr lets AI agents navigate any screen they've never seen. The architectural difference matters.

What actually happens when you connect an AI agent to a real mobile device — setup to first test.

Why selector-based mobile testing is broken, and what happens when you let AI read the screen instead.

The gap between AI-powered web testing and mobile testing — and why MCP changes everything.