Yes to that!! 
Thanks so much for clarifying. Imitation on the web is at no cost to users vs a $1.99 cover charge for what was always meant to be free.
-
-
My concern is somewhat different (the pay-for version is clearly not going to "win" vs. a free TWA version); it's more the relative insecurity. What the heck is in those 11MiB?
2 replies 0 retweets 3 likes -
Replying to @slightlylate @nomadtechie and
And if we could use the fact that the TWA pairs to the website and show that in Play.... "Paired with http://proxx.app ". Could be super useful for brands. This app is paired with http://Amazon.com ? Oh it is the real one!
2 replies 0 retweets 10 likes -
Replying to @dalmaer @slightlylate and
That doesn't help much, though, because the ones that aren't paired won't say "this isn't paired", so there's nothing there to show people there's a more "official" version. And it's entirely reasonable that someone might take, say, 2048 and publish an app of it; that's allowed.
1 reply 0 retweets 0 likes -
I think all of this is the best possible argument for restricting 3p content (not ads) to CCT.
2 replies 0 retweets 1 like -
Replying to @slightlylate @dalmaer and
You'll have to unpack the acronyms in that a bit :)
1 reply 0 retweets 0 likes -
Replying to @sil @slightlylate and
"3p" = third party CCT = Chrome Custom Tabs (akin to SFSafariViewController on iOS)
1 reply 0 retweets 1 like -
Replying to @dfabu @slightlylate and
Then... I don't understand how this would help with someone taking open source code and bundling it into a native app which is just a webview, at all.
1 reply 0 retweets 0 likes -
It'll help in the cases where someone is just hot-loading with a WebView (which I'd give 50/50 odds here)
1 reply 0 retweets 0 likes -
Replying to @slightlylate @dfabu and
Hang on, you're suggesting that shipping an apk which just loads a URL should be flat-out banned? That's not "third party".
1 reply 0 retweets 0 likes
Nope, I'm saying TWAs provide this and come with attestation (via digital asset links) and for those without DLA attestation, the URL should be shown (as with CCT)
-
-
Replying to @slightlylate @dfabu and
Ah, that seems reasonable. Although I'm not sure how it'd work; I mean, lots of people embed a webview for part but not all of their UI. That might be problematic.
1 reply 0 retweets 0 likes -
Replying to @sil @slightlylate and
They can as long as they control the target URL and can add a signed digital asset link:https://developers.google.com/digital-asset-links/v1/getting-started …
1 reply 0 retweets 3 likes - 1 more reply
New conversation -
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.