Hybrid Android applications have certain functions that are going to be coded using HTML5, and other functions that will be programmed natively in Java. The dichotomy of HTML5 versus native apps raises questions as to which parts of an application should be developed using browser-based technologies and which features should be developed using native code. TheServerSide turned to Gargenta for answers.
"For things that are run-of-the-mill," said Gargenta, such as forms or features that you might see on a traditional webpage, there's a good chance Web-based technologies will work. "If there's nothing fancy about the feature you are implementing, you can knock it off using HTML5."
On the other hand, integrating maps or taking and manipulating pictures are the types of activities that can benefit from a native mobile approach. "Those things are best done natively because you can take the power of the mobile device and work with the camera, work with the sensors and create a great user experience," Gargenta said.
Programming Android by Zigurd Mednieks
The Definitive Guide to HTML5 by Adam Freeman
Cracking the Coding Interview: 150 Questions and Solutions by G.L McDowell
The Google Resume: Landing a Job at IBM, Apple, Microsoft or Facebook by G.L McDowell