4 ms·

> While native has had roughly seven years lead Nope, it has not. Remember, web apps were first on iPhone, before native third party apps. And that's not to me

> While native has had roughly seven years lead Nope, it has not. Remember, web apps were first on iPhone, before native third party apps. And that's not to mention "common" web. Also, the roots of HTML5 go back to 2004 when whatwg was formed. > when it comes to providing quality online experience, > web apps can beat native easily. You have no idea what you are talking about. Anyone speaking this: please, find a time and get familiar with native SDKs. You absolutely have no clue how far far far behind web tech for apps is. Just do not forget that being capable to do something does not imply that this capability if pleasant to work with, performant enough, or at all useable. I lost my hope that web-tech-for-mobile will ever go past "which mvc framework to use" stage.

IpxqwidxG 13y ago
Trust me you can provide consumers all of this... 1. Pleasant to work with, 2. Performant enough, 3. Butter smooth usability ... with HTML5 and decent browser support (and significant effort of front-end developers no doubt) without having to download an app on your mobile. Native SDKs are important, I agree with you, but future isn't in them.
- Iftheshoefits 13y ago
  It really depends on what you want to do. If all you're interested in is presenting a static(-ish) web page with some "extra" interaction, then sure. If you want to do anything that harnesses the hardware or computing capability of the device, or anything more complicated the most basic HTML-based UI, then native apps are the way to go. This is independent of whether we're talking about mobile or desktop.
  - IpxqwidxG 13y ago
    I really hope WebGL is adopted for the computation intensive apps, but yes you're right for most consumer needs basic static(-ish) HTML5 format would be sufficient.
    - Iftheshoefits 13y ago
      Access to various hardware devices like the camera, speakers, sensors and the like are "basic" on mobile devices but for which there isn't any real way to access from HTML5 in a way that is useful or complete. It could be done, but then one runs into the performance/efficiency (in both development and end-user experience) issue again.

IpxqwidxG 13y ago

Trust me you can provide consumers all of this... 1. Pleasant to work with, 2. Performant enough, 3. Butter smooth usability ... with HTML5 and decent browser support (and significant effort of front-end developers no doubt) without having to download an app on your mobile. Native SDKs are important, I agree with you, but future isn't in them.

Iftheshoefits 13y ago
It really depends on what you want to do. If all you're interested in is presenting a static(-ish) web page with some "extra" interaction, then sure. If you want to do anything that harnesses the hardware or computing capability of the device, or anything more complicated the most basic HTML-based UI, then native apps are the way to go. This is independent of whether we're talking about mobile or desktop.
- IpxqwidxG 13y ago
  I really hope WebGL is adopted for the computation intensive apps, but yes you're right for most consumer needs basic static(-ish) HTML5 format would be sufficient.
  - Iftheshoefits 13y ago
    Access to various hardware devices like the camera, speakers, sensors and the like are "basic" on mobile devices but for which there isn't any real way to access from HTML5 in a way that is useful or complete. It could be done, but then one runs into the performance/efficiency (in both development and end-user experience) issue again.