cdpfleet / Android & iOS / Android
Phones · Android · early access · hardware
Android browsers on real phones.
Real Android phones — hardware, not emulators — with the browsers people actually use on them. Drive Chrome and Samsung Internet with Playwright's connectOverCDP or Puppeteer, and reach the in-app WebView and Custom Tabs that apps embed.
- 6browsers and in-app engines
- CDPPlaywright · Puppeteer
- 3–4threads per session
Browsers on the phones
| Browser | How you drive it |
|---|---|
| Chrome | Playwright (connectOverCDP), Puppeteer |
| Chrome Custom Tabs | In-app Chrome, as apps open links |
| Samsung Internet | Playwright (connectOverCDP), Puppeteer |
| Opera | Puppeteer |
| Android WebView | The in-app WebView most Android apps embed |
| Firefox | Firefox's remote debugging protocol |
Why hardware
- The page runs on a real phone, in the browser build the phone ships — not a desktop browser with a phone user agent.
- In-app engines too: the WebView that apps embed and Chrome Custom Tabs, next to the Chrome app itself.
- Country presets match the phone's locale, timezone and GPS to your exit IP, so the phone doesn't contradict its own network.
Connecting
Android sessions speak CDP: connect Playwright's connectOverCDP or Puppeteer to the session's endpoint, exactly as with desktop browsers over CDP. A WebView session takes 3 threads, a full browser such as Chrome 4.
Early access
Android sessions are in early access. Join the waitlist and tell us which browsers and countries you need. For layout checks today, device emulation runs on every Chromium-based browser on the fleet.