Assuming you're talking about Android here (given on iOS everything is just WebKit)... Do note that I have nothing against System Webview implementations. I th

Assuming you're talking about Android here (given on iOS everything is just WebKit)... Do note that I have nothing against System Webview implementations. I think they're a great solution to avoid the current Electron hellscape we're seeing play out on the desktop, where every single bespoke application is running an entire copy of Chromium under the hood. The idea of just having a single copy of a browser running in the OS as a sort of backbone for in-app HTML pages/external links without launching the entire browser is a very reasonable approach, especially given phones have historically been much less powerful devices than desktops. The problem I have is the lack of user choice; you have no control as a user what your System WebView is. Google used to offer that choice, but then quietly let vendors slam the door shut (unless you go the custom ROM route or root, which is beyond the skills of a regular user), and the default they offer (afaict) means most vendors do that, with vendors assuming most users won't care about it, so why would it matter. In fact this is also why I really dislike the Firefox approach of making it something the developer chooses to switch out, not the user - it's just bringing the Electron problem to mobile. The user should be the one making that choice, not the developer. It really shouldn't be difficult to ask the user to pick from a list of browsers and then to actually respect that list. If a user says "I want to make Firefox my browser", then Firefox should also be the System WebView. Not to quietly put them back into Chrome (and therefore subject to Googles data collection practices) just because they clicked a link in an application.