0 reply: native programs will not be eliminated at half past one due to a series of reasons such as execution efficiency and browser security sandbox. I personally think that in the future, HTML5 and nativewill be differentiated based on different application purposes. For example, applications that focus on information, content, and networks may be placed in the browser using HTML5. For some local applications, Native is preferred for execution efficiency or system-related applications. Even HTML5 can be used for front-end display of some Native applications. The two must coexist, complement each other, and even nest each other. HTML5 is the latest version of HTML, which is used for Web pages. What a webpage can do, but the effect is richer.
HTML5 is the future, mostly because it only uses HTML5 and javascript, and does not want to learn android and objective c.
In the future, most applications will develop like this:
1. Rely on the original web code to change to an html5 mobile version, supporting most mobile phones;
2. Develop an ios version to provide special support for ios; or outsource it.
3. Develop an android version to adapt to different android phones; or outsource
Depending on the situation, some companies will give priority to ios, some will give priority to html5, and some will give priority to android. Recently, wp7 has heard that it is good, and maybe it is also an option to consider.
Browsers are really important on PCs. They are even the most important programs at present.
From the era of web, the use of browsers to replace local applications is endless. Moreover, on PCs, browsers have indeed killed quite a few programs (such as music and video ). however, there is still no alternative for more programs, and most applications should not be replaced due to traffic and security issues.
There are many reasons why browsers on mobile phones have to be important to PC browsers.
1. The mobile browser cannot be fully compatible with the PC browser. As a result, the function of the mobile browser cannot be the same as that of the PC, and many things cannot be done (see various browser games ).
2. mobile phone users pay more attention to traffic, efficiency (battery), and do the same. Using custom apps saves traffic and improves efficiency than browsers, the speed will be much faster (see various news website Apps ).
3. Apps can give developers more permissions so that they can get more user data and so on to implement more functions that the browser cannot do.
To those who want to select HTML5:
1. Do not have expectations for cross-platform platforms. HTML5 is a nightmare in Split odd Android platforms;
2. Choosing HTML5 is an important distribution channel that gives up the native App Store of iOS and concentrates the vast majority of user sources. Unless you are a natural traffic platform such as search engines and Weibo, you have to weigh whether it is worthwhile to give up.
3. (for iOS platform only) whether the user experience supported by UIWebView is restricted by visual/interactive design.
4. If App packaging tools such as PhoneGap are used, you should carefully investigate the capability boundaries of the App (experiment rather than simply reading the document), such as the support for single web view.
5. Optimization of long pages, large materials (such as large images), interaction, and re-rendering (such as shadows), especially memory optimization.
6. Constantly optimize the user experience of "Imitation native", such as pre-loading and button interaction experience details.
7. If you have to be compatible with lower-version iOS or lower-configuration models (such as earlier Touch versions), it is more difficult to understand that UIWebview is a must-have feature.
8. If you can, the UI should be as simple as possible (it does not mean that it is not easy to use ).
The above is a rough description based on experience (in fact, mostly lessons. Memory capacity is limited.
I don't mean I don't support HTML5. I just want to tell people who want to pick a path that has not been traveled by too many people. There are always many pitfalls to overcome.
In addition, everything is not absolute. In addition to pure web or pure native, there is also a hybrid (web * native) path that can be taken. In the past three years, HTML5 will not occupy the mobile market, and it is unknown whether it can occupy the mobile market in five years. Recently, someone asked me to answer the question about the vitality of silverlight and html5.
I think the two are not suitable for comparison. First, html5 is more of a markup language, while silverlight is an integrated development tool.
Html5 is used to write the common parts of many plug-ins as standards and hand them over to the browser for implementation. Compared with silverlight, html5 is developed based on a mature. net Framework. Its design is still very immature, and it is not just about to happen. Plug-ins cannot be completely canceled.
Second, it uses js as the development language and is more process-oriented. It is not suitable for developing large-scale client system software.
I think html5 is suitable for mobile applications and silverlight is suitable for large bS + CS architectures.
If you only use HTML to write an application, why not simply use the browser as a system ?? A lot of years ago, some people said: PC only needs one browser, and all clients can be uninstalled. What is the current situation? It is not possible in the short term, but the native hybrid architecture for packaging HTML content is very suitable for some applications. It has already become popular in the field from minicomputers to PCs to bsstructures to mobile applications, I think there is no need to tangle with this issue. If I tell you that HTML 8 is the future, are you not waiting for HTML 8? I remember it was a pleasure to rewrite a vb Application into a power builder bsstructure. However, when I advocated bs structure in front of my boss, I was not so indifferent, because he used to work on minicomputers.
