This perspective is super confusing. Do you think that apps, as a general matter, should not send links to user's default browser?
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
Replying to @sayrer
So that's a concern about the behavior of In-App-Browser UI and the attribution therein, not about intents out to the user's *actual* browser?
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
Replying to @sayrer
That's not true *at all* FB has multiple options here that will get us to a situation where they are not *simultaneously* undermining the web platform & user choice. They could pick just one! Or zero!
1 reply 0 retweets 0 likes -
Replying to @slightlylate @sayrer
Remember the counterfactual: unless you break it, tapping on a link in Android *takes the user to their browser*. That runs zero of these risks. Alternatively, if FB wanted to continue to undermine user choice but not break the web, they could fix their godforsaken IAB's impl
2 replies 0 retweets 0 likes -
Replying to @slightlylate @sayrer
...and there are multiple ways of achieveing that. They could, for instance, embed a web engine of their own design (or take another one off the shelf). Or they could do the work to hook up the various APIs they've left unimplemented in their "browser".
1 reply 0 retweets 0 likes
All of that is strictly better than status-quo. FB has picked the worst of all these: they neither invest enough in their "browsr" to not break the web, nor participate as good citizens in the system to avoid undermining user choice.
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.