Myth debunking: WebViews suck, everything should be native

Re:Myth debunking: WebViews suck, everything should be native by datashovel on Sunday June 12, 2016 @10:54AM (#11888344)

Just a side note, somewhat related. I'm very interested to see where this argument (webview vs native) ends up. Say in 10 years. It seems to me that every time there's a "proprietary" vs "open" argument, for a short while the proprietary side wins the battles, but long term it seems the "open" side of the argument always wins the war.

[ Parent | on HN ]

Re:Myth debunking: WebViews suck, everything should be native by joeyspn on Sunday June 12, 2016 @12:04PM (#11888689)

All the UX Research we've done with our customers shows that 100% of them CAN'T differentiate Native mobile apps from 2015/2016 Hybrid apps.

I'd say 2015 represented the turning point and from now it will only get better with things like web workers (UI decoupling), WASM, and upcoming HTML5 APIs.

[ Parent | on HN ]

Re:Myth debunking: WebViews suck, everything should be native by ryanwaggoner on Sunday June 12, 2016 @02:16PM (#11889418)

Yeah, I don't believe this. You're clearly not an unbiased observer here, which is fine, but I'm skeptical of your "research".

[ Parent | on HN ]

Re:Myth debunking: WebViews suck, everything should be native by joeyspn on Sunday June 12, 2016 @02:29PM (#11889504)

It's ok to be skeptical. I don't trust everything I read in forums. So I invite you to ask to your customers what works for them and what doesn't.

[ Parent | on HN ]

Re:Myth debunking: WebViews suck, everything should be native by jack9 on Sunday June 12, 2016 @04:26PM (#11890073)

In 2010 we said "wait and see, but use native for now unless you really can do with an interactive webpage". Not much has changed.

[ Parent | on HN ]