I can't emphasize enough that this is a conscious choice, not the result of exogenous forces or happenstance. "In-app browser"s take time, planning, and engineering resources in order to subvert the default system contract -- that tapping on a link takes you to *your* browserhttps://twitter.com/slightlylate/status/1167526033999843328 …
-
-
Replying to @slightlylate
I'm not disagreeing, but interestingly I've heard from a lot of publishers that they want the in-app browsing experience for their own PWAs. Would you say that's an acceptable use-case? Overall I'd say that in some applications, there's an argument around UX/friction.
1 reply 0 retweets 0 likes -
-
Replying to @pbakaus
N/p! Didn't always, but it was a frequent request. Probably a lot more we can do about making it configurable, tho.
5:14 PM - 30 Aug 2019
0 replies
0 retweets
1 like
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.