Re:Your App Is Not Better than an Open Protocol
by engendered on Thursday February 19, 2015 @11:10AM
(#9074763)
And they're still native. Most users find it a much better experience, and the general experience with the wrapped browser Facebook app was horrendous. I'm not quite sure what your point is.
http://techcrunch.com/2012/12/13/facebook-android-faster/
After Facebook went native, LinkedIn did some "why we went with HTML5" thing...and then not long after they went native.
You mentioned in another comment that you need to see a list that has troubles on your Nexus 4. I find it difficult to believe you use the web much on the device with such a claim -- I regularly use a Nexus 4, 5, 7 (2013), and I regularly encounter horrendous websites where the site is so grotesquely overloaded that scroll requests are acted on literally a second+ later.
I love the web. I endlessly evangelize the web. But it has serious, profound problems that its biggest champions had to completely work around or avoid altogether.
Re:Your App Is Not Better than an Open Protocol
by CmonDev on Thursday February 19, 2015 @11:32AM
(#9074901)
As an added bonus you get a real choice of languages and frameworks once you depart from "open" web that practically only runs on JS, HTML, CSS. Transpilation is a hack.
Re:Your App Is Not Better than an Open Protocol
by TazeTSchnitzel on Thursday February 19, 2015 @12:12PM
(#9075217)
Transpilation isn't a hack, all compilation is "transpilation".
Re:Your App Is Not Better than an Open Protocol
by CmonDev on Thursday February 19, 2015 @12:28PM
(#9075348)
Not if some people are choosing to build apps and libraries in assembly. Websites using manually written JavaScript and HTML should be disabled to run on modern browsers.
I heard the same "argument" when Facebook went from HTML to native. Personally, I never attribute to expertise what adequately can be explained by stupidity.