5 ms·

I'll admit the demo was impressive but there's still noticeable lag in animations. So far the only web app that I've seen come even close to native is Hacker We

by navs 14y ago

I'll admit the demo was impressive but there's still noticeable lag in animations. So far the only web app that I've seen come even close to native is Hacker Web: http://hackerwebapp.com/ http://hackerwebapp.com/ I don't know about the rest of HN but I'm become somewhat tired of the HTML5 vs Native chatter. I think we can all agree that native performs better. Nuff said. Maybe we can revisit this in a year's time.

mistercow 14y ago
>I think we can all agree that native performs better. Nuff said. No, not enough said. Performance isn't everything.
Lazare 14y ago
Well, here's not-at-all-hypothetical example: We're a really, really small shop, developing a webapp. We would love a mobile app before we launch, but nobody here has ever developed a native app before - our experience is strictly related to web development targeting desktop browsers. We could probably throw together an HTML5 app for Android and iOS (phonegap, etc) pretty fast. Or I guess we could try and outsource development of native apps for Android and iOS, except we're not sure of cost, or risks, or how to find a developer, or whether the result would be up to our standards (our core selling point, is basically, "this webapp is like the others you've seen, but with a UI that'll blow you away"), so a slow HTML5 app is bad, but so is a clunky and ugly native app developed by someone who doesn't have the same obsession with attention to detail that we do. So...we've got a choice to make, and "native performs better" isn't enough. How much better? And what do you give up to get native? Does Sencha (or whatever) get you close enough for our purposes? How much harder is a good HTML5 app to develop compared to a cude wrapper around an existing site? These tradeoffs are not obvious, and for people currently evaluating options, I think they're interesting.
- navs 14y ago
  I get where you're coming from. As a web developer I'm all for the web in general. I suppose my frustration stems from how an evaluation of a new web framework leads to a frustrating back and forth on native vs. web. It's a hot topic. I'm currently working on my first iOS app (yes I know I'm late to the game) using Trigger.io: https://trigger.io/ https://trigger.io/ Still working my way through the documentation but so far it's amazing. Consider having a look. EDIT: Hello from Auckland :)

by navs 14y ago

mistercow 14y ago

>I think we can all agree that native performs better. Nuff said. No, not enough said. Performance isn't everything.

Lazare 14y ago

Well, here's not-at-all-hypothetical example: We're a really, really small shop, developing a webapp. We would love a mobile app before we launch, but nobody here has ever developed a native app before - our experience is strictly related to web development targeting desktop browsers. We could probably throw together an HTML5 app for Android and iOS (phonegap, etc) pretty fast. Or I guess we could try and outsource development of native apps for Android and iOS, except we're not sure of cost, or risks, or how to find a developer, or whether the result would be up to our standards (our core selling point, is basically, "this webapp is like the others you've seen, but with a UI that'll blow you away"), so a slow HTML5 app is bad, but so is a clunky and ugly native app developed by someone who doesn't have the same obsession with attention to detail that we do. So...we've got a choice to make, and "native performs better" isn't enough. How much better? And what do you give up to get native? Does Sencha (or whatever) get you close enough for our purposes? How much harder is a good HTML5 app to develop compared to a cude wrapper around an existing site? These tradeoffs are not obvious, and for people currently evaluating options, I think they're interesting.

navs 14y ago
I get where you're coming from. As a web developer I'm all for the web in general. I suppose my frustration stems from how an evaluation of a new web framework leads to a frustrating back and forth on native vs. web. It's a hot topic. I'm currently working on my first iOS app (yes I know I'm late to the game) using Trigger.io: https://trigger.io/ https://trigger.io/ Still working my way through the documentation but so far it's amazing. Consider having a look. EDIT: Hello from Auckland :)