MisterBigglesworth
Expert Member
Hey,
So I need to create an App for iPhone and iPad for work. We might move to Android later...but first phase is for iOS. It will be nothing resource intensive, some articles etc...mostly content updates. Someone said we should look at using the web framework instead of the native dev option. As it was explained, Apple will charge a huge fee to register the App on iTunes for download, should I go the native route.
Using the Web framework...I can create it in HTML5 and via an API it will seamlessly run as an App on the iPhone and iPad. So how does this work...as I assume I still need to get it listed for download on iTunes?
I was told the web HTML5 route is better because if we decide to accommodate other OS's, we dont have to code a version for all different OS's. The HTML5 route is better because all we need to do is make sure it caters for most screen sizes as its OS independent...
The last option is to go the Mobi route....but that means users would have to remember the URL and to me thats not great user experience.
Anyone been in the same boat and can offer advice etc?
So I need to create an App for iPhone and iPad for work. We might move to Android later...but first phase is for iOS. It will be nothing resource intensive, some articles etc...mostly content updates. Someone said we should look at using the web framework instead of the native dev option. As it was explained, Apple will charge a huge fee to register the App on iTunes for download, should I go the native route.
Using the Web framework...I can create it in HTML5 and via an API it will seamlessly run as an App on the iPhone and iPad. So how does this work...as I assume I still need to get it listed for download on iTunes?
I was told the web HTML5 route is better because if we decide to accommodate other OS's, we dont have to code a version for all different OS's. The HTML5 route is better because all we need to do is make sure it caters for most screen sizes as its OS independent...
The last option is to go the Mobi route....but that means users would have to remember the URL and to me thats not great user experience.
Anyone been in the same boat and can offer advice etc?