The status quo of it 33-HTML5 the spring is the winter of the native app?

The subtitle is the thinking of mobile development technology

Company departments are in the "high-priced" recruit HTML5 developers, and most of the mobile terminal. The atmosphere of public opinion is so high that I have to think about the technology of mobile application development.

Time returned to 2011 years, this year is the beginning of the HTML5 year. The major technical news, forums and other propaganda channels are filled with HTML5, mixed, noisy. A pair of HTML5 who but myself momentum, a very unmanageable. But my feeling is little wool, because that period of HTML5 technology is not mature, standards have not been introduced, so when it is the stage of the momentum, and did not give important attention. At that time, Wei was a happy mobile developer, bracket, native app developer, abandoned WM platform turned to Android for two years.

The benefits of native applications are self-evident, it can maximize the speed and performance of the equipment, and the uniqueness of the system platform to easily display, the hardware of the barrier-free control of the use of more rich applications, it can be said that this is the best choice for mobile application development.

HTML5 as a practice path for RIA (Internet rich client), it can make a very good interface effect, its biggest advantage is cross-platform. It only focuses on the effects of running in each browser without deliberately treating you as Android or iOS.

The advantage of native applications is the disadvantage of H5 and vice versa.

Another small question: is cross-platform so important for mobile applications?
The global smartphone market share in the first quarter of 2015 is:

Android     78.9%iOS         17.9%WP          2.5%BlackBerry  0.4%Other       0.4%

Mainstream four mobile phone operating systems, according to market share, you need to develop at least Android and iOS two systems of the app, for those manufacturers, WP is also to support. By convention, each mobile platform will have its own development team corresponding to it. The cost of raising a team is high, and at the company level, the cost of developing a mobile application for each mobile platform is too high, if there is a solution that adapts to multiple platforms.

Man's quest for cross-platform has never stopped.
Time back to 2015 years, after 4 years of development, H5 finally slowly boarded the stage. Some companies are starting to use H5, the Web front-end technology to develop a balm application, regardless of whether the outcome is a result or failure, H5 a very important step forward, it will move the native application of the cake.

It reminds me of one thing that happened to Apple a few years ago.
Amid is a strong supporter of HTML5 technology, and he also decisively abandoned iOS support for Flash. "No one wants to use flash," he said. "The world has begun to enter the HTML5 era." When Apple strongly supports H5, it's tempting to think that when developers use H5 to develop apps, there will be fewer native apps in Apple's App Store, and Apple's revenue will be reduced (the App store prohibits pure web apps from publishing). It seems as if H5 's development would affect Apple's interests. Amid what the Lord is thinking, it is unknown. However, from the development of these years, H5 has not influenced the application store.

Currently there are two sets of solutions in the industry:
One is the deep-pocketed type. Large companies will launch a native app for the user experience, and as a supplement, they will launch a mobile web version.
The second is the hybrid type. In order to save costs, the company will do its best to do resource reuse. So many simple modules will be H5 and embedded in the native application. This hybrid app has become the mainstream of the current program.

Mobile development technology has emerged in three Kingdoms: Native app, web app, hybrid app.

Introduce Wei Tsai's a meager:
Automotive and Mobile development: The original car is oil-burning, which is called a native car, then the oil-electric hybrid, which is called hybrid car, make one is the current more fire of pure electric vehicles. Mobile development is based on the development of various systems SDK, this is the native app, then HTML5 to push pure web app to cross the platform, because of the pros and cons, there are more hybrid applications, this is the hybrid app. When is pure electric capable of completely replacing a fuel-burning car? When does the web app completely replace the native app? Are native developers really worthless?

Wei Tsai of this meager three question mark End, Wei Tsai himself first to do an answer.
The first one is really hard to say.
The second one I think should never be. Because the world needs to be differentiated, each operating system's existence will have its own characteristics, and these features only the native application can be fully played out. Unless the world's operating system is unified by the web, people only need a browser.
The third answer is negative.
Just as the answer to the title of this article is no, I am on the side of the native application. I think native app developers are still valuable. First, the market outlook for native application development is still bullish. Second, even if you really use the Web app, the team still needs to understand the different operations of the experts exist. Unless the world is ruled by the web.

Reference:
Http://www.missyuan.net/school/web_2012/web_9205.html
Http://www.ibm.com/developerworks/cn/web/lp/html5/develop.html

The status quo of it 33-HTML5 the spring is the winter of the native app?