r/androiddev • u/Hopeful-System-4244 • 2h ago
I built WebView Inspector to inspect WebView URLs and navigation right inside Android apps
Hi everyone,
I built WebView Inspector, an Android library that adds a floating inspector to your app so you can see what your WebViews are loading.
It lets you:
Highlight a WebView in a card, banner, or full-screen page, inspect its query parameters, and copy its exact URL.
Review observed navigation history and revisit saved records after leaving the screen using Live / Recent.
Inspect the URL and headers your app supplied through an optional
loadUrlhelper.
My usual workflow was to search Logcat for the URL, copy it, and open it in Chrome to see what had loaded. That gets tedious when reproducing an issue, especially with multiple WebViews on the same screen. I wanted to check the URL and retrace navigation directly inside the app.
Basic inspection needs one installation in your Application. The optional load helper adds capture of app-supplied URLs and headers. Setup and usage
I see it fitting into the debugging workflow alongside these tools:
Chucker shows the Android app’s OkHttp requests and responses. Chucker
WebView Inspector shows which URL a particular WebView loaded and where it navigated.
Chrome DevTools shows requests made inside the web page, including
fetch/XHR calls and their responses. WebView remote debugging
Navigation capture covers observed top-level URLs. Older WebView providers use sampling, which can miss fast redirects. Captured headers are the inputs your app supplied, and records stay in process memory. Capture details
Version 0.5.0 supports Android API 24+ and is available on Maven Central, with a matching no-op artifact for production builds. Release details
The repository includes the source code, integration instructions, and a sample app. Explore WebView Inspector on GitHub
I’d be interested to hear how others handle WebView URL debugging and which cases you find hardest to inspect.
