So far in 2011 mobile web and native applications have been popular, each offering their own strengths and reasons for use, but what does the future hold for each? Will the popularity of HTML5 kill the native app or will the smoother and more streamlined interface of a native app keep them at the top of the food chain? As applications become increasingly popular for a variety of purposes, here are some things to consider in the mobile web versus native app argument:

HTML5: According to a recent study by ABI Research, more than 2.1 billion mobile devices will have HTML5 browsers by 2016, making a strong case for the future being with web apps written in HTML5. Web apps written in HTML5 allow for cross platform capabilities. Additionally, HTML5 also has a geolocation API that enables mobile web apps to access the device’s GPS which will provide valuable data to the applications while also letting users stream audio and video without plug ins. Another benefit of using an HTML5 based web app is that is has the ability to cache data on a mobile device to make greater use of the device’s built-in processing power that will not only speed performance, but also make it easier for the web developers to build apps that offer better responsiveness on par with native mobile apps. To date, HTML5 optimized apps such as TweetDeck and Scribd have been very successful.

4G: Thanks to 4G wireless becoming the norm on most smartphones, the internet lag is decreasing. And depending on your wireless carrier and data plan, the data speeds you will experience with 4G will be faster than many DSL and cable modem wired connections. But what does that mean for apps? Both mobile and web apps will be able to exploit the speed and capacity of the 4G networks. But web apps currently suffer more from slower connections than native apps since they requires a return trip to the web server to do most interactivity. With 4G, mobile web apps will be able to retrieve content from the network faster and more reliably than in the past, almost matching the performance of native apps.

Dual and Quad Core Processors: Although both native applications and web mobile applications will see gains due to improved processors, mobile web apps will gain the most due to the processing necessary to render HTML in a browser. A native app has a defined UI that is part of the application; in contrast, a mobile web app sends the UI from the server in the form of HTML. Improved processors will shrink the gap in responsiveness.

W3C Standards: It took quite a few years for all of the desktop browsers to finally have strong adherence to the W3C standards. For years Netscape and Internet Explorer always had some serious differences, making it necessary to test your web apps on both.  But as the browsers matured, the adherence to the W3C standard has become much more significant. In the same way, Android and iPhone both use the same technology to render HTML on their browsers.  But Blackberry and the Windows Phone didn’t.  Now with the BlackBerry 6.0 and 7.0 and with Windows Mango, all of the 4 major phones will have a strong adherence to the standard.  Why is this relevant?  Having to test on multiple browsers or creating different versions of a web app for specific browsers significantly increases the total cost of ownership of the app.

Whether or not you decide to go mobile web app or native app will ultimately come down to your audience and cost. If your app requires a complex UI or some very specific on-device functionality, a native app may be a better route; if you are looking to develop a quality cross-platform application that still needs to perform well then a mobile web app is the better choice. However, what is certain is that the future of mobile web apps is looking bright, and the popularity and power of HTML5 could definitely give mobile apps serious competition. Only having to create one version of each app will save costs and leave additional dollars for marketing and promotion.

AUTHOR: Patrick Emmons is an accomplished technical architect with more than 15 years of programming and web development experience and is a Microsoft Certified Solutions Developer (MCSD). As co-founder of Adage Technologies, Patrick has been instrumental in building a cohesive and well tuned development staff. Pat's focus on taking the best of software development methodologies, recruiting, and employee training and applying them to web application development has created a solid foundation for Adage's continued success.

Read more from Patrick Emmons (RSS)

• Website

Related posts:

1. Mobile Apps Vs. HTML5: What does the future hold?
2. Unplugged – the first ever conference focussed on developing native apps for iOS, Android, webOS, and more using HTML5
3. Netbiscuits collaborates with Samsung for more bada mobile apps
4. Confirmed: Android Apps to Work on BlackBerry PlayBook Tablet
5. Mobile Developer Magazine looking forward to the future of QNX