For hybrid apps, mobile web QA, device-specific bugs and remote Chromium debugging.
The page works in the desktop browser and breaks inside the app’s WebView, and the only signal you get is a screenshot from QA.
Attach to the WebView on the device and read the real DOM, console and network of the page that is misbehaving.
Half the bug reports are iPhone-only, and Safari Web Inspector requires a Mac nobody on the team has.
Inspect the iPhone from the Windows machine you already work on. No second computer in the budget.
A defect reproduces on one handset and one OS version, and logs alone never explain why.
Plug that exact handset in and inspect the failing page live, on the device where it actually fails.
A layout or an API behaves differently across iOS versions, Android versions and vendor browsers.
Keep several devices connected and step through the same page on each one from a single window.
Everything is fast on a developer laptop and sluggish on the mid-range phone your users actually own.
Profile on the device itself, so the numbers you optimise against are the numbers your users get.
The Chromium instance you need to debug is on a box across the room with no keyboard attached.
Add it as a custom device by IP address and port, and inspect it from your desk.
Connect iPhone and iPad through the WebKit remote debugging protocol and inspect from Windows, macOS or Linux.
No proxy, certificate or SDK. Connect, trust the device and enable the platform debugging switch.
iOS uses WebKit Web Inspector. Android and Chromium use Chrome DevTools, served locally.
Whichever one it is, the setup is the same: one cable and one platform toggle.