Damru
Use cases
Damru is built for lawful web scraping, mobile automation/QA testing, anti-bot / fingerprinting research, responsive testing, and AI agent automation — all on real Android.
Each use case below follows the same shape: a definition of what it means, who it is for, a concrete example, and where to learn more. Every one assumes you have authorization for the sites involved.
Web scraping & data collection
Programmatically collecting publicly available data from websites you are authorized to access, including mobile-rendered and bot-protected pages where desktop headless browsers get blocked.
Who it's for: Data engineers, researchers, and analysts gathering datasets at scale.
Example: Collecting mobile-only listing data from a marketplace you have permission to crawl, where a desktop headless browser would be flagged.
Automation & QA testing
Driving a real Android Chrome browser to test how a mobile web experience actually renders and behaves, rather than a desktop browser pretending to be mobile.
Who it's for: QA engineers and front-end teams shipping mobile web.
Example: Running an end-to-end checkout flow on genuine Android Chrome to catch a layout bug that never appears on desktop emulation.
Anti-bot & fingerprinting research
Studying how device, GPU, and network signals are detected, and how an OS-level spoofing approach differs from JavaScript patching.
Who it's for: Security researchers and anti-fraud teams.
Example: Comparing how a real Android fingerprint and a patched desktop fingerprint score against the same public detection suite.
Mobile QA & responsive testing
Validating responsive layouts, touch interactions, and device-specific rendering across many real Android device profiles instead of a single resized desktop window.
Who it's for: Mobile QA, design-system, and accessibility teams.
Example: Checking that a responsive component renders correctly on a Pixel 8 Pro, a Galaxy A54, and a Redmi Note across different screen densities.
AI agent automation
Giving an AI agent a real Android browser to operate, so the agent acts through a genuine mobile environment rather than an easily flagged desktop headless one.
Who it's for: Teams building autonomous agents and LLM-driven workflows.
Example: Letting an agent complete a multi-step task on a mobile site through a real Android Chrome instance it can also watch live.
Which use cases are legitimate?
Damru supports lawful scraping within terms, QA and responsive testing, fingerprinting research, and permitted AI-agent automation — it is not intended for multi-accounting, fraud, or bypassing protections.
This table maps each use case to whether it is a legitimate, supported use, a concrete example, and a guide.
| Use case | Legitimate? | Example | Guide |
|---|---|---|---|
| Web scraping within terms | Yes, when authorized | Crawling a site you have permission to access | Learn more → |
| Mobile QA & responsive testing | Yes | Testing your own app on real Android profiles | Learn more → |
| Anti-bot & fingerprinting research | Yes | Studying detection on public test suites | Learn more → |
| AI agent automation | Yes, on permitted sites | An agent operating a mobile site you control or may use | Learn more → |
| Multi-accounting / fraud / bypassing protections | No | Not a supported or intended use | Learn more → |
FAQ
What is Damru used for?
Damru is built for lawful web scraping within a site's terms, mobile automation and QA testing, anti-bot and fingerprinting research, mobile responsive testing, and giving AI agents a real Android browser. It is not a multi-accounting or fraud tool.
Is using Damru legal?
Damru itself is a legitimate open-source automation framework. Whether a particular task is permitted depends on the target site's Terms of Service and applicable law — you are responsible for complying with both.
Can Damru be used for QA on real devices?
Yes. Because it drives genuine Android Chrome across 155 real device profiles, it is well suited to mobile QA and responsive testing that a resized desktop window cannot reproduce.
You are responsible for complying with each site's Terms of Service and applicable law. See legal & ethical use.