3 ms·

It's funny, I can't see a world where native isn't better. The performance is still affected even for simple apps and even if the CPU can handle that degradati

by dwild 13y ago

It's funny, I can't see a world where native isn't better. The performance is still affected even for simple apps and even if the CPU can handle that degradation, the battery won't. If the application does something, it will take more CPU time and this is bad in ANY way. Why wasting theses CPU cycles? Only because you are "more productive"? Second argument, security. Inject JAVA into a live app, not impossible, but hard. Inject HTML, easily done... When will we start to see XSS on our applications? HTML5 is literally an eval on every single text field... Third argument, HTML5 is fantastic? Then use it, nothing stop you. There's multiple way to do it currently, the JS api on Android is complete, you can do anything you want. If the platform doesn't support HTML5, then you can start an open-source project or even a commercial project that will allow it. If we start from the HTML5, you won't be able to go native from that point, you directly block possibilities only because you prefer HTML5. Facebook tried the HTML5 for their apps, the performance was awful and it wasn't a complex app at all.

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 ago
  The 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?

by dwild 13y ago

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 ago
The 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?