cdpfleet / Android & iOS
Phones · early access
Android sessions run on real Android hardware; iOS sessions run in an iOS WebView. Either way the page is rendered by the phone's own browser engine — not a desktop browser pretending to be one.
Device emulation — Playwright's device descriptors — runs a desktop engine with a phone-sized viewport, a phone user agent and touch events. It is quick and good for layout tests, but the engine, its features and its fingerprint are still the desktop browser's.
cdpfleet's phone sessions use the phone's own engine: Chrome, Samsung Internet or the WebView on an Android phone, and the iOS WebView on iOS. What the page sees — features, rendering, network behaviour — is what phone users' browsers do.
// Emulation, for comparison: a desktop engine wearing a phone's viewport and user agent.
const context = await browser.newContext({ ...devices['iPhone 15'] });Need emulation only? It works on every Chromium-based browser and WebKit on the fleet today — see mobile device emulation.
Real Android phones — hardware, not emulators — driven over CDP with Playwright's connectOverCDP or Puppeteer.
connectOverCDP), PuppeteerconnectOverCDP), PuppeteerAn iOS WebView, driven through cdpfleet's session API.
outerHTML| Session type | Threads |
|---|---|
| Mobile WebView — Android WebView, iOS WebView | 3 |
| Mobile Chrome — Chrome and other full browsers on Android | 4 |
Phone sessions use the same threads as desktop browsers, weighted by what they occupy, and are metered to the second.
Phone sessions are in early access while the fleet of devices grows. Join the waitlist and say which platform and browsers you need.