...whereas CCT puts your browsing back in your hands. With CCT, your choices matter, and bowsers can compete on security/privacy/tracking/etc.
-
Show this thread
-
There's a further issue, though. WebViews aren't meant to be full implementations of the web platform. They're sort of halflings: some core stuff is built-in, but anything that reaches outside of the renderer -- APIs that do something other than CSS/HTML/JS -- is often busted.
1 reply 1 retweet 6 likesShow this thread -
This makes WebView based in-app "browsers" totally broken from the perspective of the web platform. They are boat-anchors for progress on the web, even when they're built form exactly the same source code.
2 replies 1 retweet 11 likesShow this thread -
But as much as *I* care about that, it's something of a minor point in the grand scheme. The big issue here is privacy. And WebViews are even worse than just letting the app itself sniff and rewrite all the pages you see... ...remember those out-of-date WebViews?
2 replies 0 retweets 4 likesShow this thread -
Attacks against WebViews aren't just attacks against the pages, they're attacks against *the host app*. Everything you trusted it with.
1 reply 0 retweets 6 likesShow this thread -
Now, again, OS vendors are doing a ton to try to fix webviews...but the model is just busted. The attack surface area isn't just the web platform, it's every API the host app bolts on or intercepts. Disaster in the making.
1 reply 0 retweets 6 likesShow this thread -
WebViews for non-app content are a choice that apps make. Other, better, more respectful and secure choices are available to them. Apps that insist on not taking you out to your browser when you tap on links, but also do not take advantage of CCT/SafariViewController are *bad*.
1 reply 3 retweets 8 likesShow this thread -
Cannot stress this enough: the only reason this happens is because apps are jealous of your time. They build these upside-down "browsers" because they don't want you to go to your real default browser. They want to keep you in-app. They *worked* to break this.
2 replies 3 retweets 20 likesShow this thread -
Replying to @slightlylate
I think you and I are not far apart in how we'd like this to work in an ideal world, but you know that you are grossly oversimplifying the choices and forces at work here. Google Chrome is not a value-neutral, idealized privacy wonderland.
2 replies 0 retweets 0 likes -
Replying to @hillbrad @slightlylate
If it’s an idealized privacy wonderland you two are looking for, may I suggest Safari?
1 reply 0 retweets 2 likes
Y'all port to non-niche OSes (or let us *actually* port to iOS), and I suppose that would enable meaningful browser choice for most users. A web that's only for the rich isn't a web worth wanting.
-
-
All really good points, loving the debate. I know it's incredibly difficult but it would be pretty amazing if you found points to criticize/improve with your respective employers. It's a little too easy to criticize competitors :)
1 reply 0 retweets 1 like - 2 more replies
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.