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 -
This Tweet is unavailable.
-
Replying to @sayrer
No, you're *invoking the user's browser to navigate on their behalf*. The honest thing would just be to intent out, but FB doesn't do that...so here we are.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @sayrer
Here's a way to think about this line: WebView: "I'm loading content into my app" Intent to browser: "I'm telling another app to load content" CCT: "I'm telling another app to load content, but keeping the user in my activity stack"
2 replies 1 retweet 0 likes -
This Tweet is unavailable.
This is...confused. FB broke the system contract by undermining link clicks and the choices users are *already making* about them. You can't start from the broken WebView-IAB-attribution-confusion counterfactual. FB broke it, they bought it.
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.