APP use to write a lot of H5, but APP is linked url remote mode, resulting in a poor user experience of APP, because when you use the remote url H5, H5 page to open the speed of decisions by the network, not by phone performance decision, if the user opens the APP where there is no network, the situation open late APP interface, a blank white page appears even cause users have been waiting for.
In fact, the use of APP H5, should not use the remote H5 url, but should use the file: // method to open a local path local H5 page, instead of using http: // remote path opened H5 page, so open APP speed can be compared with the original, because it will not be associated with the opening speed network speed, the speed can be as open with the native sec. And after the interface opens, when loading data using ajax asynchronous loading, let the screen prompts the user to wait, without the use of synchronous load, which is the key to improve the H5 experience. Such APP interface speed just open the phone's performance-related, not related with the speed of the network.
Why do I say that with the development of H5 APP APP experience can be better than it? Because it comes from the CSS standards mature and proven technology framework js Ui possible because a flashy interface, using css very simple to implement, and even download to the very unusual css styles, if you use the native himself to write the same UI realize it can be very troublesome. Therefore, many companies use the local rendering interface H5 made out of interface, but very nice, but because using the wrong remote URL pattern but affect the user experience.
Local H5 H5 hot update mode + + ajax support cross-domain, the best solution is the use of H5. Why do cross-domain? Because when we open the local H5 using a file: // method to open a local path, so when if we use http or https access to external api is the need for cross-domain support. Fortunately, Andrews and ios webview of UIwebview components can be set up to support cross-domain. But if the package yourself APP, to achieve all of these, but also compatible with all phones, the threshold is relatively high, even more than developing native APP threshold is higher. Thus, to the user experience or require the use of specialized tools package to package, or do not own to pack H5 app.
What tools are packaged it? Hbuilder can be used to package, but hbuilder not automatically update the heat. Here I recommend a very good tool for online package local H5, I have used, very easy to use.
https://www.yunedit.com
This tool can be packaged local H5 mode app, but also in the background H5 hot update the code, but also to support cross-domain access ajax, there yeui js framework calls the native function.
Under summary, in fact, with H5 development experience is not good, or because the level of problem programmers, engineers APP pack level of the problem, leading to a front-end regardless of H5 engineers to write code that no matter how good, because network problems are finally making APP experience is poor. Therefore, the use of specialized tools or packaged packaged packaged platform, is still very necessary.