4 ms·

My comments from the article: > I’ve developed apps both native and not native for all platforms, and html5 apps don’t deliver faster results. Developing in ja

My comments from the article: > I’ve developed apps both native and not native for all platforms, and html5 apps don’t deliver faster results. Developing in javascript is not faster, in fact making a complex app takes about the same time or even more. This is really a matter of opinion. Obviously if you approach an Objective-C developer and ask them to build you a HTML5 app it will probably take more time, but for someone such as myself who doesn't know and doesn't want to learn Objective-C it will be faster to use HTML5 and Javascript. > Learning native technologies takes time, but that is a time well invested in something that you will use over and over again to deliver results. Again, this is really just an opinion rather than fact. If you want to learn and write your app in Java, Objective-C, C# and whatever the Ubuntu phone will use then go ahead. However, I quite happy to write my apps once in HTML5, knowing that there will be some issues, but that I can get it done a lot faster than writing once for each platform. > HTML5 does not look and behave like native app, never This really isn't an argument any more. I agree that to make stuff look like native components (and as pointed out by other commenters to behave) is harder in HTML5, however take a look at apps such as Path or Foursquare. They don't look like native apps at all either. Making things look native isn't necessarily something you should be striving for.

rimantas 14y ago
> I quite happy to write my apps once in HTML5, knowing that > there will be some issues, but that I can get it done a > lot faster than writing once for each platform. The point still stands it really pays of to learn native framework: the sole purpose for it's creation was to be used in web apps. HTML was created to markup the structure of large texts… Source: I am long-time web developer before turning to full-time iOS programmer.
- corresation 14y ago
  HTML was created to markup the structure of large texts… Of all of the potential arguments against HTML n, this is by far the weakest. What HTML was created for is utterly irrelevant in 2013.
mattvot 14y ago
Authors Response: "However, I quite happy to write my apps once in HTML5, knowing that there will be some issues" If those issues ruin the user experience, I wouldn't be happy. Laggin app on a powerful device with very few other things running is such an issue which often happens on HTML5 apps and if you go to a less powerful device it becomes worse. Not sure what you were looking at but Foursquare looks like all other native apps on both iPhone and Android, so your example does not stand. The idea is to build apps that use familiar controls and UI patterns. This helps new users find their way around quickly with almost no learning curve.

rimantas 14y ago

> I quite happy to write my apps once in HTML5, knowing that > there will be some issues, but that I can get it done a > lot faster than writing once for each platform. The point still stands it really pays of to learn native framework: the sole purpose for it's creation was to be used in web apps. HTML was created to markup the structure of large texts… Source: I am long-time web developer before turning to full-time iOS programmer.

corresation 14y ago
HTML was created to markup the structure of large texts… Of all of the potential arguments against HTML n, this is by far the weakest. What HTML was created for is utterly irrelevant in 2013.

mattvot 14y ago

Authors Response: "However, I quite happy to write my apps once in HTML5, knowing that there will be some issues" If those issues ruin the user experience, I wouldn't be happy. Laggin app on a powerful device with very few other things running is such an issue which often happens on HTML5 apps and if you go to a less powerful device it becomes worse. Not sure what you were looking at but Foursquare looks like all other native apps on both iPhone and Android, so your example does not stand. The idea is to build apps that use familiar controls and UI patterns. This helps new users find their way around quickly with almost no learning curve.