Supercharged WebView Observability
summary
Hybrid solution injects a controlled JavaScript SDK into each WebView and ships metrics back over the Android JS bridge, capturing Core Web Vitals (LCP, INP, CLS), fetch/XHR timings (monkey‑patched), PerformanceObserver resource metrics, console logs, promise rejections and interaction signals like rage clicks and long tasks. Platform layer clamps SDK version, applies remote config and a kill switch, limits serialized payloads, and auto‑instruments via a Gradle plugin. The approach yields a stitched native+web session and broad telemetry; custom tabs remain unsupported.
AI-written summary · about
chapters (7)
- 0:00WebView observability intro
- 2:09WebView instrumentation challenges
- 6:43Android-only limits
- 7:24JavaScript SDK trade-offs
- 12:39Hybrid solution
- 14:51Security and reliability
- 17:50Q&A
related talks
34mOvercoming JavaScript Unsecurities in WebViews
40mJS performance in mobile web and hybrid apps… because science!
23mA pragmatic approach to WebViews
25mWebView Implementations in the 2020s
37mAchieving Native-like Speed
15mWebViews: fast-tracking features in mobile apps
22mChrome and Android: Past, Present, Future
39mAndroid and the WebView