Should You Develop Your App Using HTML5 or Native Code

Should You Develop Your App Using HTML5 or Native Code

So, what should you use to build your mobile apps, HTML5 or native code? That’s the debate that is raging these days. In some cases the answer is very clear and in others it’s not so much. HTML5 doesn’t depend on an App Store for distribution and many web developers can leverage their existing skills to create mobile friendly apps, but even Facebook, with all the coding muscle you’d think they must have made the recent choice to convert their mobile app from using HTML5 to native code.

Here are a few great discussion on the topic:

What’s your opinion as a mobile app developer or as someone who uses mobile apps?

Charles McKeever
Corona Geek

Charles McKeever

Charles McKeever is a life long computer geek who enjoys exploring technologies to understand how they work, how they can be smashed together, and how they can be used to fuel entrepreneurial endeavors.

  • Hector Sanchez
    Posted at 13:27h, 30 August

    I also had this dilemma earlier in the year, when I was starting to learn Corona, and I even stopped studying Corona for a while to learn some HTML5/JavaScript app platforms, but at the end, I convinced myself that the way to go are Native Apps.

    The key here I think is the AppStore and Apple’s review system that cleans it from crapps. This ecosystem brings confidence to end customers, the confidence that they are getting a good quality app, an app that will perform well on their devices and on the other side, Apple brings to the table millions of pre-qualified customers with their credit card numbers. This enables app developers to get paid well, as it has been proved by the over $5 billion dollars already paid to developers.

    It is true, that you might build a similar app with HTML5 and JavaScript, but you have to find a market to sell it to, so without a market there is no money. Apple already has the market, a huge one and a super qualified one. That allows developers to focus on building quality apps, and not worry about marketing their product, collecting money etc. I will gladly pay Apple 30% for the access to such a big qualified market.

    Kindle Fire’s Appstore understands this and they are doing a similar job with that.

    • charlesmckeever
      Posted at 12:18h, 31 August

      Excellent observation Hector. HTML5 apps that just aggregate content are getting rejected by Apple because they say you can create a mobile version of your website that does the same thing. These same apps can be published in the Google Play store, but as you point out, there is a lot of noise in that ecosystem, which makes it hard to get noticed.

      So, really there are three issues here; 1) which technology gives you the performance and ability to do what you want to accomplish, and 2) which types of apps are most appropriate for publishing in the app stores, and 3) how do you reach a broader market if you don’t leverage an existing app store audience.

      Right now, HTML5 apps are highly dependent on the speed of your device’s internet connection, so the footprint of the app would have to be small and cached locally for download and fast loading. Native apps don’t have this issue, but they are highly tied to app store distribution.

      Maybe the answer has more to do with who you are trying to reach and what do you want to accomplish, rather than just should you use technology A or B.

      What do you think?

      • Hector Sanchez
        Posted at 10:16h, 01 September

        Yes I agree, I think the answer has to do with who you are trying to reach rather than picking a technology. As Gary Halbert once said “Go where the starving crowd is”, so at this time the starving crowd is in the AppStores, so that’s where I’m targeting my apps. Apple already did the effort of gathering the starving crowd in a confined pond, rather than you having to hunt them in the sea, so we as developers need to provide the right “food” for them

Post A Comment