Yes, Android's WebView can be used to make a browser. No, it is not functional without a *lot* of work:
developer.android.com/reference/andr…
"But why does this matter?" you might ask, looking at your GA logs.
What fraction of your mobile traffic comes from "Android Webview"? For most publishers, most of the time, that is largely FB's "In-App Browser".
On Android, Browsers are things that put intent filters in their manifest for all `http://` and `https://` view actions:
developer.android.com/reference/andr…
That's 20-30% of traffic that doesn't handle Push Notifications or PWA install or WebAuthN or pretty much anything in the Fugu roadmap:
developers.google.com/web/updates/ca…
Could they staff a real browser team? Chose to use CCT or delegate to the user's default (real) browser? Sure. All of that is meeting or 5 away for the folks who go to work every day in Menlo Park.
You didn't push back.
Now the web is broken for most users, and, in particular, first-time-internet users.
What should we do about it? What will *you* do about it?
Hot tip from a browser engineer: FB makes a *wildly successful* browser, and it *sucks*