I would like to take a look at the development prospects of HTML5 in the mobile Internet field. I would like to take a look at the development prospects of HTML5 in the mobile Internet field. Reply content: Hybrid? Efficiency is no longer a problem?
Self-deception: HTML achieves an Android drawer and is stuck out of sight.
The advantage of HTML5 is that it is too costly to make Native interfaces with the same effect. Therefore, you can use Hybrid for content display pages. For pages with complex logical relationships, please be honest and practical in Native development.
React Native?
Still early, Virtual DOM is also weak for pages that require complex updates. This is indeed worth noting. Hot update is a tough headache for Native apps. React Native not only solves cross-platform problems but also hot update problems.
For pure HTML5 apps?
I personally think that H5 can be used for apps that are not very heavy, and the cost for Android and iOS development is too high. Isn't there any other platforms such as public accounts. Http://www.infoq.com/cn/interviews/interview-with-heshijun-talk-javascript-achievements
At pm, react. Just an iOS uitableview is enough for others to imitate the self-cited content blog: Gu Zhenping's column
You can click it to view other blog posts about the HTML5 APP.
Cross-platform APP development is a trend in the future, and more tools will emerge. Native developers will experience a certain decline in both salary and number of people.
The landlord asked about the comparison between H5 and native. HTML5 can be used as Web apps and Hybrid apps. Native apps are used as Native apps.
===== Body ======
Native Development, which is mature at present, is adopted by all major companies. However, the labor cost is high. For the same project, at least three development teams, Android, iOS, and Web, are required.
Web apps are Web-based systems and applications that run on the networks and browsers of high-end mobile phones and use Web technology to develop applications that implement specific functions. Difference from WAP: functional level. WAP focuses on the use of web technologies for presentation on mobile terminals, including text and media files. Web apps focus on using Web technologies to implement App functions.
Hybrid App is developed based on a third-party cross-platform mobile application engine framework. Developed using HTML5 and JS, the underlying functions encapsulated by the engine are called, such as cameras, sensors, and address book. It has the advantages of Native App with good user interaction experience and cross-platform Web App development.
Illustration: cross-platform APP ---- Analysis of Three development modes of Native, Hybrid, and Web APP (Series 1)
If you don't think the depth is enough, I still have a lot of information. I will continue to write.
Developing an APP with HTML5 will also face many choices, such:
Cross-platform APP-analysis on four major platforms: Cordova, APPCan, DCloud, and APICloud (Series 2)
If you select factory D like me, stamp:
HTML5 APP ---- DCloud Product Analysis and introduction
So sorry, I 've provided you with so many links. Let's get involved and check them out. please correct me!
CSDN blog: Gu Zhenping's column
And leave a comment! Thank you!
Above! There are still many ways to go for h5, but it will make the native ui more and more beautiful in the future: overview-Material Design Chinese Version
As people pay more and more attention to experience, services are constantly assimilated. In the future, services will be quickly assimilated without any novel services ), who has a good app ui experience, who will receive more consumers.
While html is moving forward, Native is not stuck.
In general, html is in the same direction as nuclear energy. Once widely used, it will produce breakthrough results. It can only be used locally ~~ Recently, we are working on H5. The advantage is that you only need to write a set of code, and the disadvantage is that it is full of pitfalls. It is still good to be compatible with Android 4.4 +.
Google uses chromium (http://www.chromium.org/
As the underlying Kernel support of the system WebView. In this change, the WebView APIs provided by Android have not changed significantly. In Android 4.4, the WebView APIs are compatible with earlier versions and a small number of APIs are introduced. Here, we will briefly introduce the differences between Chromium-based Webview and Webkit-based webview. The Chromium-based Webview provides a wider range of HTML5, CSS3, and Javascript support. Currently, the latest Android version 5.0 is based on chromium 37, webview supports the vast majority of HTML5 features. Webkit JavaScript causes the use of WebCore Javascript on Android 4.4 to be replaced with V8, which can directly improve JavaScript performance. In addition, Chromium supports remote debugging (Chrome DevTools ). Excellent: one person can develop applications on two platforms without considering the version and design style issues.
Poor: All except the advantages.
Prospect: there is no prospect
