News for hackers. Stuff that matters.
Re:The Chrome Distortion: how Chrome negatively alters our e... by kuschku on Saturday March 26, 2016 @02:40PM (#11366826)
> Chrome is doing nothing secret and magic on Android.

> having random third-parties replace the WebView in my app is a profoundly bad idea

You haven’t heard of Chrome Custom Tabs, have you?

Re:The Chrome Distortion: how Chrome negatively alters our e... by SomeCallMeTim on Sunday March 27, 2016 @01:19PM (#11370656)
No, actually. Thanks for letting me know about that.

Regardless, my point stands: If I'm writing an app and I use a WebView or a Chrome Custom Tab, I'm going to want to know, for certain, that someone isn't switching out the underlying rendering engine.

Re:The Chrome Distortion: how Chrome negatively alters our e... by kuschku on Sunday March 27, 2016 @03:55PM (#11371258)
Well, but that’s the entire point of Chrome Custom Tabs. There are even Presto and Gecko based implementations of it.
Re:The Chrome Distortion: how Chrome negatively alters our e... by SomeCallMeTim on Monday March 28, 2016 @12:18AM (#11372707)
The "point" of Chrome Custom Tabs seems to be performance and better integration with the system browser.

I see that it's done via Intent, so it could potentially be swapped out, so you're right.

So then WebView is more of what I'm talking about, for when you want tight integration, or creating something like a Cordova app (though you can bundle a Cordova app with Crosswalk to sidestep WebView differences entirely); looks like Chrome Custom Tabs is more for when you want a good web experience, not a good embedded app experience.