Note that responsible native apps *have* a way of creating an "in app browser" that doesn't subvert user choice or break the web: https://developer.chrome.com/multidevice/android/customtabs … Any browser can implement the protocol & default browser will be used. FB can enable this with their next update.https://twitter.com/slightlylate/status/1167548118876901376 …
-
Show this thread
-
This Tweet is unavailable.
-
Replying to @sayrer
The client is OSS & under developer control: https://github.com/GoogleChrome/custom-tabs-client … What browsers collect when you invoke them is what browsers collect when you invoke them.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @sayrer
WebView API is here: https://developer.android.com/reference/android/webkit/WebView … Metrics opt-out is but a google search away:https://developer.android.com/guide/webapps/managing-webview#metrics …
2 replies 0 retweets 0 likes
But I think this misses the point: if FB wants to undermine user choice, they should damn well pony up and make a real browser. That could be webview based or they could do the legit thing and ship their own engine. Whatevs. But hiding behind "webivew vs. CCT" for IAB is BS.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.