IONIC Notes Cure (1)

I haven't studied in depth for a long time before, and I don't feel very good. It is just during the Spring Festival to make up for IONIC.



The following are the theoretical knowledge notes. I told myself to have this concept, but I may update my thoughts.


Now There are currently three ways to develop mobile apps:


    1. Native/Native: Use native SDK to develop apps. Needless to say, the advantage is that when you have enough resources, this is the most ideal way; the

disadvantage is that it needs to be developed separately for different platforms, which is costly and has a long cycle.

    2. Native script/NativeScript: The native API is encapsulated into a JavaScript interface, which is a bit like the front-end nodejs.

Compared with the native method, the NativeScript method has little performance loss (it is said to be only about 10%). The advantage is that the development language uses

JavaScript uniformly, and the disadvantage is that it needs to be developed separately for different platforms.

    3. Hybrid/Hybrid: Use web technology to develop apps, and use cordova/PhoneGap for packaging. The advantage is that it adopts standard web technology development, which avoids the learning of native development systems of different platforms, and is fast and efficient; the disadvantage is that there is a certain loss in performance.




Then Ionic is the third type, the so-called hybrid hybrid, which uses web technology to develop apps, and uses cordova/PhoneGap for packaging.



-------------------------------- -------------------------------------------------- -------

About what a hybrid is:
 
     .... to put it nicely is a mobile application that includes a separate browser instance.

This kind of application is called 'Web-View'.

======================================= =========================================
The following passage is about Web-View Advantages and disadvantages .


   + Cross-platform, can be deployed to multiple platforms with only one development, and the development cost is minimized.
  
   + Web technology sharing! We know that NodeJs plays a key role, because it enables JavaScript to run away from the Web!
   + It is very similar to native applications, and most devices can be accessed (called) normally.
  
   + Simple development, this It is very important, for example, if you are born in J2EE, you can develop IOS using Web-related technologies without knowing Obj-C or -Swft.


   - The application cannot leave the WenView instance, so the performance depends on the browser.

   - Most access ( Calling) and asking (using) the native functions all depend on the plugin (Cordova). That is to say, some native APIs may not have corresponding plugin implementations, so it takes effort to bridge them.

   - There is no native user interface and controls. . . . . . .