Yeah, we have a very browser-centric perception of that space. In-app browsers are browsers too. One could argue Twitter/Facebook/etc. are modern twists on a browser offering social curation of Web content combined with messaging.
-
-
Replying to @tobie @othermaciej and
My understanding is that in-app browsers are only browsers if browsers don't need to include any privacy. e.g. WKNavigationDelegate seems to allow the surrounding app to capture cookies for any site the user logs into.
1 reply 0 retweets 1 like -
Replying to @jyasskin @othermaciej and
Well, they *are* browsers after all. Of course they do.
1 reply 0 retweets 0 likes -
How's that different than if you install Firefox on your Android? (Or Google Chrome on iOS).
1 reply 0 retweets 0 likes -
Replying to @tobie @othermaciej and
You are trusting any browser you install with your full browsing data, which is why Firefox, Safari, Brave, etc. use privacy arguments to try to convert Chrome's users. How many users realize that their browser decision isn't keeping them safe when they click a link in an app?
1 reply 0 retweets 1 like -
Replying to @jyasskin @othermaciej and
It's not like they really have a choice.
1 reply 0 retweets 1 like -
They don't and that's not OK. But more to the point, giving a choice will not fix the problem in practice. This is a serious design flaw that users shouldn't need to know or care about.
1 reply 0 retweets 2 likes -
Replying to @KenjiBaheux @tobie and
It would be great if more in-app browsers (or even all of them) could be the good kind. Tough problem to take away or restrict existing APIs, but worth it to work on it. In any case, the in-app browsers that are implemented the less good way are still browsers.
1 reply 0 retweets 1 like -
Replying to @othermaciej @KenjiBaheux and
I've been defining browsers as "apps that accept all navigation intents"; that's a bit Android specific (as you can actually replace the default browser there), but it captures the essential difference in responsibility to the user, IMO. These WebView things are franken-browsers.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @othermaciej and
Arriving at a sort of agreed-upon definition would be interesting and would help inform conversations. Maybe a
@w3ctag finding? How can we make progress when there's no agreement between browser engineers as towards what we're working?2 replies 0 retweets 2 likes
Lemmie be super clear: apps that capture clicks to the web and then short both users and developers of privacy, security, and choice (Apple's retrograde policies not withstanding) are *anti-social*. Become a real browser or leave it to the pros.
-
-
Replying to @slightlylate @tobie and
...and on that basis, I'd of course welcome a thoughtful treatment by the
@w3ctag. Calling out the tradeoffs of "in app browsers" and their better/worse permutations is overdue.0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.