Home  >  Article  >  Web Front-end  >  Development of HTML5

Development of HTML5

怪我咯
怪我咯Original
2017-04-05 15:53:221447browse

At the end of October 2014, W3C (World Wide Web Consortium) officially announced that HTML5 was officially finalized. The technology circle seemed to have discovered a way to break the native APP world dominated by Google and Apple, and published Many articles that preach that HTML5 will truly begin to subvert native (Native) apps have also begun to focus on developing HTML5 and beginning to seize the future of HTML5. So will HTML5 become the next trend? Can the final version of HTML5 really subvert the current hot native apps? Personally, I think there are the following opportunities.

 1. The attitudes of Apple and Google

The iOS and Android systems represented by Apple and Google , occupying more than 95% of the market share of mobile systems, and both Google and Apple are loyal fans of native APPs. What you need to know is that the reason why HTML5 or Web APP has not become the main APP implementation method on the mobile Internet is that the advent of the first-generation iPhone in 2007 almost wiped out Web APPs from the mobile Internet. In addition, native APPs have become increasingly popular among users. Interaction is excellent, there is no room for Web APP to survive.

Fortunately, with Android 4.4 released by Google at the end of 2013, the built-in Webview is no longer the crappy Android WebKit browser, but Chromium. After the release of iPhone 5 in 2012, the performance of HTML5 on iOS has been satisfactory, and Safari’s exclusive JavaScript acceleration engine Nitro is no longer so important. However, after the release of iOS 8, Apple wisely canceled it There are restrictions on third-party programs calling Nitro. Now any browser or application calling UIWebview of iOS can use Nitro acceleration. The attitudes of the two major mobile operating system overlords and browser giants have changed, so that the development of HTML5 on mobile phones is no longer restricted, and this change is irreversible and can only continue to move forward. This change is bound to have far-reaching impacts (quoted from "HTML 5 is finally finalized, and eight years later we will talk about how to change the world again" published by 36Kr on November 3, 2014).

Google and Apple also seem to see the advantages of HTML5 in the future. In addition to making some changes in the browser core, they have also made corresponding changes in the operation of the browser. For example, in the Safari browser , you can add a web page to the home screen, and add a Web application to the home screen to quickly access the web page. Perhaps this is setting the stage for future Web APPs developed based on HTML5.

 2. The technical limitations of HTML5 itself

Although HTML5 is the only cross-platform that can take advantage of mainstream platforms such as PC, Mac, iPhone, iPad, Android, and Windows Phone language. But its own shortcomings are inevitable. The lack of API, the inability to interact well with mobile hardware, the lack of support for mobile-specific push, and the unsmooth interaction...are all the main factors that prevent rapid popularization in the short term and hinder the development of Web APPs. resistance.

 3. Attitude of software developers

From the current point of view, Google and Apple have dominance in the native APP market, so their attitude towards HTML5 has not been It is too clear, there is neither a vigorous development trend nor a complete denial. Based on this, software developers also have different attitudes. One is to continue to retain native APPs and not develop Web APPs; the other is to vigorously develop Web APPs based on HTML5; however, more of them adopt a hybrid development approach. mode, that is, using a native + HTML5 approach for hybrid development, which can use native technology to make up for the shortcomings of HTML5, and also use HTML5 technology to achieve rapid iteration and other functions. At present, most of the platform-based apps or news apps adopt a hybrid development model. However, although the hybrid development model is a major use of HTML5 technology, it is undeniable that it still relies on native APPs to run.

 4. Web APP entrance and operating environment

In the early days of the mobile Internet, with the help of browsers, Web APP had a good operating environment and high-quality entrance. But as Web APP was replaced by native APP, native APP established a system + application store model as the acquisition entrance and operating environment of native APP. However, what are the acquisition entrance and operating environment of Web APP? Since the browser kernels are different between different systems, whether support for HTML5 can affect the use and interaction of Web APP has become the core issue. WeChat seems to have provided a good solution. On January 19, 2015, WeChat opened the WeChat web page development toolkit (WeChat JS-SDK) to developers, which allows users to easily develop based on JS-SDK. WeChat's Web-App, and using the WeChat service account to replace the website address, gradually built a Web APP application store and operating environment.

Although the road ahead of HTML5 is long and full of thorns, it is undeniable that with the finalization of HTML5, Web APP will usher in the best development opportunity in the future. With the improvement of hardware processing capabilities, the original performance problems of HTML5 will It will also be solved, and technological improvements will gradually erase the gap with native APPs. With its cross-platform advantage, it will naturally develop greatly. But as for whether it can completely replace the native APP, in my opinion, it is unlikely, just like the launch of web games has not defeated client games. In the future, Web APP will exist in an environment that is suitable for it, and native APP will also exist in an environment that is suitable for it, just like iOS and Android now, they will coexist.

The above is the detailed content of Development of HTML5. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn