Sure! The short version is that I don&#x27;t know.<p>We were looking for instances of insecure WebView usage, so from a security perspective small piece vs. entire app doesn&#x27;t matter too much (and is difficult to measure, especially when looking at 1.1M apps).<p>However, some of the other numbers from our analysis can be useful to draw a picture of WebView usage.<p>We statically looked for uses of WebView, and 85% of the 1.1M apps used a WebView.<p>Of those 998,286 apps:<p>- 97% enable JavaScript (which is off by default)<p>- 36% use the JavaScript Bridge Interface (which is a fairly good indicator of heavy WebView usage)<p>- 94% implement a shouldOverrideUrlLoading method of the WebView (another good indicator that the developer is using the WebView for something non-trivial)<p>- 27% implement an onReceivedSslError method of the WebView (indication that the developer is using the WebView for something non-trivial). (Sadly, 29% of the apps that implement onReceivedSslError intentionally IGNORE all SSL errors.)<p>So I guess the takeaway is that 85% is an upper bound, the real number of WebView-only apps is absolutely lower, however it&#x27;s clear that WebViews are significantly used in mobile apps.