re: Official Android App Development Thread

quote:

---

would you argue its easier to develop and test against HTML rendering & support in IE7, IE8, IE9, IE10, IE11, Firefox, Chrome, Windows XP, 7, 8, 8.1, Mac OS, Safari, Firefox for Mac, Chrome for Mac...

..or simply open your IDE and set output to android?

i'm not saying the integration with the web is going away..i'm just saying that developing a true APP as opposed to designing a website in HTML5 that works on mobile devices is WAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY easier.

---

I disagree, a native app requires a lot more development since you are using different languages and platforms. An HTML5 based app requires far less time and resources to deploy since it is cross platform (not saying there won't be problems, just think it would be less than porting or redevelopment). I am not arguing in favor of either method, just mentioning that the direction of technology is towards the web based application on the device.

quote:

---

I disagree, a native app requires a lot more development since you are using different languages and platforms. An HTML5 based app requires far less time and resources to deploy since it is cross platform (not saying there won't be problems, just think it would be less than porting or redevelopment). I am not arguing in favor of either method, just mentioning that the direction of technology is towards the web based application on the device.

---

i don't necessarily disagree outright, but a native app written specifically for android or iOS will be more robust, have better control over the internal resources/sensors, etc. and likely use less battery.

as i've understood html5, it continues to evolve and access to all available sensors and api plugins (like google maps for instance)could be an issue.

because you can add a webpart to any android app, wouldn't it be more logical to design an app and use strategically use html5/webpart only where it makes sense?

also, i *hated* the idea of apps originally thinking a website could be designed easier/better for delivery to mobile devices. however i've reluctantly come to the realization there's a mystique or impression that apps are a better product than a website bookmark...that they are more full-featured. whether thats true or not is another question.

It seems 99% of apps on android are coded in java so that seems the logical place to go due to the overwhelming amount of information and developer support.

sites like app inventor essentially provide graphical tools for what is text-based syntax in java and looking up something like this 'app inventor to java' youtube video, it gives you a really good sense of how similar the two are.

in other words; learn to build a reasonably robust app using 'app inventor' and the process of translating what you've done into java becomes chicken falling off the bone.

Convert App Inventor to Java..you already know how!