2 ms·

You have two types of webviews... "Webviews to the appmakers server", and "Webviews for the wider web". Webviews to the appmakers server need to be authorize

You have two types of webviews... "Webviews to the appmakers server", and "Webviews for the wider web". Webviews to the appmakers server need to be authorized by some manifest file on the server whitelisting the app identifier. Webviews for the wider web don't allow the app to know what's going on inside the webview, nor interact with it. So these are safe to type passwords into etc.

deleted 3y ago
[deleted]
rezonant 3y ago
So this would have no effect, because you can simply embed Chromium in your app instead of using the system-provided WebView. Because Android is very fragmented and there are still a significant amount of devices out there running less than Android M when the web view was made an upgradeable package, there is, at least for now, a very legitimate reason to ship your own browser implementation within an app that is primarily implemented using web tech: The Web View implementation shipped with M and earlier is not sufficient to run such an application.