I’m writing and want to introduce to all about new mobile application development technology which calling Native application and web application in HTML5 right Now. Hope you will get right information here.
First, let me clarify the definition: 
Mobile Web Apps: Web applications are not real applications, but is actually the site, in many ways, looks and feels native applications, but not as such. They are operated by a browser, usually written in HTML5. Users access first, because they have access to a page: navigate to a specific URL, the page should be the option “install” on your home screen by creating a bookmark.
Native Apps : Native applications through an application store (eg Google Play or Apple App Store) installation. Living in a native application on the device and can be accessed through an icon on the home screen of the device. They are designed for the platform, you can take full advantage of all features of the device – you can use the camera, GPS, accelerometer, compass, contact lists, and so on.
I like someone finally made clear that if the development of one or the other problem. I think the technical problems (access to I / O device performance, ease of use, etc.), mainly related to the article, which is good.
But I think that other issues must be considered. In particular, taking into account comments received from some of the arguments that Tim Berners – Lee recently gave WWW2011, Hyderabad, India.
I would choose the phone option for several reasons:
- The data are processed remain on the site, rather than preserved in some applications.
- The pages would be accessible and indexed by standard search engines.
- The development would be (almost) independent of the platform.
- Also the development of domain-specific languages and code generators would be much easier.
- From a business perspective, as well as a few cases of success, most of the native application to exploit known to increase the number of downloads mark. For the rest of the world, the e-model pair and connect resources are the best to collect reasonable traffic.
As for the possible downsides, I think most of them can be easily solved:
- graphic consistent with the platform of choice can get a reasonably easy.
- integration with the input / output devices and sensors can be granted on the browser level API and should not require ad hoc coding.
WebRatio also made a number of industrial installations of mobile web applications. See, for example, the site B & B for the iPad.
By: Hi-Tech ITO