Recently, many users have left messages asking some basic questions, such as: What is the better development method for App? I feel this way and hope to make a summary through this article.
To determine the results first, whether to use native or hybrid development methods, you need to first understand the business plan, and then formulate R&D technology selection and R&D plans based on the actual needs of the business.
Why can we only discuss one matter at a time? This has to start with the advantages and disadvantages of the technical architecture.
Basic science
First, let’s popularize the definitions of native development and hybrid development.
Native development refers to using the native language and tools of a specific platform (such as iOS, Android, etc.) to write applications and run them directly on that platform. The interface and user experience of native applications are usually very smooth and responsive, but native development requires mastering platform-specific languages and tools, and developing independent applications for different platforms.
Hybrid development means developers use common web technologies (such as HTML, CSS, and JavaScript) to write applications and embed the applications into native containers through WebView components. Hybrid applications enable cross-platform development and can use many common development tools, frameworks, and libraries to speed up development time. However, due to the need to access hardware resources and functions indirectly through WebView, hybrid applications may perform worse than native applications and are not as good as native applications in terms of performance and user experience.
Why are the streets so full of mixed developments now?
This also has to talk about the business development of the Internet.
Humans are social animals. The core keyword of this sentence is "animal". Being an animal means having the need to "like the new and dislike the old". In other words, in the era of prosperous Internet, business scenarios must follow the needs of users. Update iteration, that is to say, in terms of efficiency and quality, the originally balanced balance has tilted.
The mainstream model of hybrid development is a development model that combines native and HTML5 technologies (mainstream, but not the only one, the more popular one now is mini-program technology). The native code part uses WebView plug-ins or other frameworks to provide HTML5 with each other. A container. The main business implementation and interface display of the program are implemented using H5-related Web technologies. For example, current JD.com, Taobao, Toutiao, etc. all use hybrid development models.
Gradually, in 2017, WeChat launched the Mini Program open platform and devoted great efforts to the construction of the Mini Program ecosystem. Gradually, the development of the mixed model of "App + Mini Program" was gradually promoted. The advantages of the App hybrid development model of "App + Mini Program" can be summarized as:
-
The experience far exceeds that of H5 (supports local caching, Webview, and has rich components and support libraries);
-
Can obtain more system permissions and complete richer product designs;
-
DOM leakage can be avoided (the commonly used window objects and document objects are not used);
-
Packet size is effectively reduced, saving traffic and storage
Relying on the development of mini program technology standards, mini program container technology has gradually become the "standard" for hybrid development. Some of the more well-known mini program container technology products on the market include: WeChat, Alipay, Baidu, Douyin mini programs, etc. They are all designed to improve the technical base of large social platforms’ own mini program ecology and can provide third parties for privatized deployment. The products include:FinClip, mPaaS and other products. It is understood that FinClip’s self-developed mini program container technology can enable corporate apps to quickly run mini programs, and their SDK can also Embed in functional device terminals other than App (such as running on Linux, Windows, MacOS, Kirin and other operating systems).
Technical value and business value of hybrid development
Technical Value In addition to the benefits listed above, the "hot update" and "cross-platform" capabilities are also deeply loved by developers.
In terms of business value, the rapid introduction of third-party ecology is a core value of mini program technology as a combination of hybrid development.
Since the WeChat mini program was officially launched in 2017, it has quickly become an important ecosystem in China’s mobile Internet industry. As of the end of 2021, the number of monthly active users of WeChat mini programs has exceeded 120 million, covering application scenarios in various industries such as e-commerce, finance, medical care, education, tourism, and travel. The WeChat mini program ecosystem is also constantly improving, providing developers with a wealth of development tools, templates, open source components and other resources.
If we say that in Internet 1.0, each platform reinvented the wheel; in Internet 2.0, the creation of templated front-end pages greatly reduced the redundant development work of R&D; in Internet 3.0, ecology is king, and whoever can introduce enough ecology in the shortest time will be the winner. It can quickly deepen its moat and focus on the research and development and business deepening of its core technologies.
Of course, in the end, when we choose various development models, we still have to choose based on our own actual applications. For example, when developing tool-type apps, native development is generally chosen because it requires a good operating experience and fast response speed; for example, for developer malls and O2O apps, it is more suitable to develop apps in a mixed mode; mini-program technology is suitable for ecological introduction; HTML5 The development is generally used for mobile web development.