Native, HTML5, mixed Hybird

• Three modes of app development: native, HTML5, hybrid Hybird
  • Native APP: That is, the native development, Native code programming, after compiling in 2 or byte code in the form of running on the OS, directly call the OS device API;
  • Web apps, which are programmed with web technologies such as HTML+JS+CSS, code runs in a browser and invokes the device API via a browser (depending on the HTML5 future support capabilities):
  • The Hybrid APP is hybrid development. Some of the code is programmed with Web technology, some of which are assumed by some native container (such as the Phongap plug-in, the BAE plugin), and are designed to perform this part of the current phase of HTML5 not fully supporting the device API and network API. The common technique is WEBVIEW+HTML5
  • React Native is a technology that Facebook has introduced in the Java language to write ios,android, as well as in the background. With react Native is the true meaning of the full stack, a project from start to finish can be done by one person
  • Advantages of React Native:
    • It can be real-time hot update (like a Web page, changed a font, ready to go online)
    • Relative Hybird app or WebApp:
      • Without webview, get rid of WebView's annoying interactions and performance issues
      • There is a strong extensibility, this is because the native side provides the basic control, JS can be used freely combined
      • Can directly use the native native "awesome" animation (in the FB Group app, the panel slide out with a little jelly bounce, panel based on a point to expand the animation everywhere, this animation with native code to do a piece of cake, but it is difficult to do with the Web).
    • Relative to the native app:
      • You can update the app directly by updating the remote JS, but this is fast becoming the standard of the large native app ...
    • Disadvantage
      • Extensibility is still far less than the web, and it's far less straightforward to write native code (this nonsense explains it)
      • From native to the web, to do a lot of concept conversion, will inevitably cause both sides to compromise. The end of the web to use a set of CSS version of the castration, native to be laborious to convert this castrated version to native native expression (such as iOS constraint\origin\center, etc.), both sides will be uncomfortable

Native, HTML5, mixed Hybird