With the rapid development of Chrome and Safari, and the decline of IE Flash, HTML5 has come to an end and entered the next era - mobile Internet. The cross-platform advantages of HTML5 are further highlighted in the mobile Internet era. HTML5 is the only one that takes all PC, Mac, iPhone、iPad、Android、Windows Phone Cross-platform language for mainstream platforms such as ##. Java and Flash both dreamed of this position, but their dreams ended with iOS . At this time, people began to study the development of cross-platform mobile applications based on HTML5. Many people believed at the time that native applications were just a transition, just like the transition from the C/S structure to the B/S structure. And learning Objective-C and Java is very difficult. Since I know web development, why not try HTML5 .

W3C At this time, the Device API working group was established to extend for HTML5 Camera, GPS and other #API that are unique to mobile phones. However, the trouble is that the early iterations of the mobile Internet were too Soon, the mobile phoneOS is constantly expanding the hardwareAPI, gyroscope, distance sensor, barometer. Every year there are major version updates for mobile phones. As an organization where hundreds of member units make joint decisions, W3C has a very complicated process from proposing a standard draft to reaching a consensus, which cannot keep up with the rapid iteration in the early stages of the mobile Internet.

The emergence of PhoneGap has opened a window for developers. Many people expect PhoneGap to continue to expandAPI to supplement the shortcomings of the browser. Adobe Seeing PhoneGap seems to have seen the hope of revitalizing the status quo, but in Adobe After acquiring PhoneGap, I found that this thing is not commercially viable enough, and open source makes Adobe unable to be like Flash obtained commercial interests in this way, so he donated PhoneGap to Apache and changed its name to Cordova.

Due to various reasons, the positioning of Cordova ultimately did not become a browser enhancement, but moved towards hybrid development. Based on the background at the time, they believed that native was irreplaceable, and the hybrid mode of "native HTML5" made more sense. So now the usage model of Cordova is that "native engineers HTML5 engineers" work together to complete App .

At this timeFacebook joined W3C and took the lead in establishing the Mobile Web working group . Facebook is in the Web circle, and does not have itself on the mobile phoneOS territory, he doesn’t like the native app ecosystem controlled by Apple and Google. Mobile WebThe important goal of this working group is to make web applications developed by HTML5 achieve the experience of native applications. However, things backfired. It didn't matter if it didn't work hard. The result was that it failed despite trying hard. 2012, the news that Facebook gave up on HTML5 flooded the world ITMedia, HTML5 were instantly thrown into limbo.

FacebookWhy gave up HTML5?The core is that based on HTML5, we really couldn’t make good mobileApp. Compare Twritter and other competitors’ native App, Facebook’s HTML5 version really cannot satisfy users. For example, regarding the Push function, there is still a huge gap between the HTML5 push experience and the native push experience, let alone HTML5 There are many problems such as white screen when switching the application page, pull-down refresh/ The side sliding menu is not smooth, etc. Watching native engineers easily implement functions such as shake, QR code, voice input, and sharing to Moments made HTML5 engineers feel like they were on the wrong team.

Even if Facebook doesn’t like to be controlled, we can’t risk being abandoned by users. And Facebook has not mastered the key point - the mobile browser core. If browsers don't keep up, a bunch of draft standards will be in vain.

What is the performance of the browser on the mobile phone??Look firstGoogle,Chrome Although the performance is high, the browser on Android is not Chrome, but WebKit A crappy modificationAndroidbrowser;Look at Apple again, Other browser engines are not allowed to be listed on the App Store on iOS, and other applications using the Safari engine are not allowed Unable to call Apple's own JavaScriptacceleration engineNitro. The result is that Apple and Google not only do not actively implement HTML5 on mobileAppThe required specifications instead impose various restrictions on HTML5.

Whether it was the lack of hardware capabilities at the time or the deliberate restrictions of mobile phone OS manufacturers, the result is: in the early days of the mobile Internet, the world must be dominated by the native application ecosystem, iOSandAndroidFirst of all, after their territory is stabilized, the industry will upgrade to the next stage.

No matter Facebook or PhoneGap, you won’t be able to get a share of the mobile Internet in the early days, but if you persist, opportunities will often appear. And this yearHTML5 games are on the forefront. How to seize the dividends of H5 games in the spotlight? It depends on your own operating conditions. Nobita Game, H5 game interface.