On Android, iOS native html development and cross-platform development of the pros and cons
(2015-05-19 13:03:59)
Reproduced label: it |
Recently I was asked this of Internet products & skill, like cooking is common sense to why salt such problems, although every time patiently explain why they are to each other, but really a bit tired and not feel love, so today this problem to do a comprehensive analysis and summary of this to illustrate the various aspects of operational efficiency, development efficiency, application updates and other issues:
1. operating efficiency:
Native code based on the underlying operating current environment, and is above the ambient html a Web analytical vessel, this difference in structure, resulting in efficiency is unlikely to exceed html native code application is constructed.
Although the hardware is now so rapid development of applications in the form of APP almost without regard to the efficiency of this issue, but I think we'll see a few basic hand travel is based on large-scale development html to build.
2. The development efficiency
If you are doing a single platform, features a simple and less demanding on the details of the case, in fact, the difference will not be much development efficiency.
If the details of the requirements is relatively high, a native of efficiency will be relatively better, which is derived from each platform has its default form of interaction, native is no need to take this into account, the system has to help you solve this problem, but the html No, the developer will need to deal with, ignore these will downgrade the quality of products.
If the function is more complex, such as the need to use the camera, gravity and acceleration sensor, Bluetooth communications, the native efficiency will be higher, because if html need to use these features, you need to do the corresponding native interfaces, which resulted in additional workload.
If you are doing multiple platforms, features a simple and less demanding details of the case, html efficiency in the development will have a certain advantage, which is derived from the results of a set of html that can run on different platforms.
If you are doing multiple platforms, but the high details of the requirements, or more complex functions, the native will be more efficient. Because the details of the requirements of high, even with html do need to do adaptation for various platforms, so multiple platforms and development work is no difference compared to html and need to interact with the functional interface issues to consider additional issues Therefore the development efficiency will definitely be much lower.
In addition, many people may now have made a lot of cross-platform tools html, we can address some of the underlying problems on different platforms, but if the quality of products that require high, then these tools are actually fussing live, you still have to adaptation to different platforms, unless the expense of product quality. The use of third-party tools will bring additional problems: my application is not only resistant according to the quality of the platform itself, but also according to the quality of resistance to third-party tools, which resulted in the product at greater risk.
So, if it is multi-platform, it features a simple case of product quality and for less demanding, html development efficiency has some advantages, or native development efficiency will be higher.
3. Application update problems
Html advantage is that the user immediately after the release of the update, but need to reinstall native, this html have certain advantages, but the case is now automatic update feature has been very popular, the advantage is not particularly evident.
in conclusion:
Do not use basic html to consider doing APP product, unless you do not ask for product quality, and hope thereby reducing development costs.
Prior to this conclusion Facebook has publicly acknowledged: APP use html to do is develop a failed decision.
In addition:
Html for cross-platform tools available in the market, and I think these things are almost too much sense not exist. Third-party tools resulting risk is not that the Internet is a product development, everyone can use, and competition is relatively intense. Do not you will pay in order to save the cost of a developer away the expense of product quality, so that products in the competitive disadvantage it? Even in the early days!
Of course, cross-platform development tools in one area is very good: the game. (Note: It is not cross-platform tools html)
Development cost of the game is the application of APP than the average much higher, so to save development costs that would be the effect on the more obvious, and the game has its own interactive form, not something to do too much and platform-specific relationship .
另外，游戏由于其对执行效率的要求会比较高，所以在执行效率上处于劣势的html就成了累赘，现在很多主流的游戏跨平台开发工具最后都是编译为各自平台的底层代码，或者运行在虚拟机上的二进制文件，如果使用html来实现，这是自己给自己找麻烦。