"App" Hybrid? Native? I don't know, you're out!

Hybrid? What is it? I believe that you will often see this word in ordinary life, such as the more Fire hybrid car (hybrid car) if it is for the app? That will be from the classification of the application of the current mainstream applications broadly divided into three categories: Web App, Hybrid app, Native app first, let's see what is Web App, Hybrid app, Native app:

Native App

Traditional native app development model, Android based Java language, underlying call Goolge provides api,ios based on objective C or swift, underlying calls Apple's official API

Advantages:

Directly rely on the operating system, the most interactive, the best performance

The most powerful, especially in interacting with the system, almost all functions can be realized

Disadvantages:

High development costs, no cross-platform, independent development on Android and iOS on different platforms

Higher threshold, the original personnel have a certain threshold of entry, compared to the majority of front-end personnel, less update slow, especially after the release of the store, need to wait until the audit cycle of high maintenance costs

Web App

That is, the mobile site, the page is deployed on the server, and then the user to use the major browser access, not a standalone app, can not be installed and published, similar to the current light application

Advantages:

Low development cost, cross-platform, easy to debug

Low maintenance costs update no need to notify users, no manual upgrade required without installing apps, not consuming phone memory

Disadvantages:

Unable to get system-level notifications, reminders, action, etc.

Low user retention and limited design limitations many experiences are poor

Hybrid App

(Hybrid) hybrid application, embed WebView in the application, access the webpage through WebView, well, what about WebView? WebView is a WebKit engine that exhibits Web page controls: the display and rendering Web interface is directly used in HTML files (Web or APK resource bundle assets) for layout and JavaScript interaction calls

Advantages:

Low cost of development, cross-platform, easy to debug maintenance cost, function can be reused

Improved functionality, performance and experience are more free than web app updates.

Cons: Compared to native, there is still a large loss of performance and is not suitable for highly interactive apps

Tips

How to tell if an application interface is a native or a web interface

1, in the phone/simulator click on the phone in the version number 5, come out developer options

2. Check the display layout boundaries in the developer options and return to the app interface

3, if the app is an HTML interface, the interface will not have a layout boundary display, if there is a native interface

Such as: The first picture is the native interface, the second picture is the HTML interface

"App" Hybrid? Native? I don't know, you're out!