2 ms·
By many reports Facebook's native app is still pretty flawed so maybe they just suck. Your battery argument only holds if the 'html overhead' is a major part o
by andybak 13y ago
By many reports Facebook's native app is still pretty flawed so maybe they just suck.
Your battery argument only holds if the 'html overhead' is a major part of power usage and there is no evidence it will be (screen on time, radio usage etc., native calls will probably dwarf drawing the UI).
Your security argument also strikes me as weak. 'Wrapped' HTML apps presumably benefit much the same security infrastructure as native apps. Once your app is vulnerable to injection it's pretty much game over no matter what your choice of language.
- dwild 13y agoThe Facebook app is perfectly fine, I have no problem with it. I have plenty of games that eat more battery than anything on my phone. Except that like I said in HTML every single text you show is literally an eval call. There's still ton of XSS on website, it's a common security threat, the same will be possible on an HTML5 application (they will even have access to your phone functionality).
- andybak 13y ago> I have plenty of games that eat more battery than anything on my phone. I'll agree with you wrt games in HTML/CSS. They are likely to be much less efficient than in native code. > Except that like I said in HTML every single text you show is literally an eval call. I don't follow. How come?