uni-app actively embraces the community and creates an open and compatible plugin system.

uni-appActively embrace the community and create an open and compatible plugin system.

  • The uni-app plug-in market has thousands of plug-ins, supporting various types such as front-end components, js sdk, page templates, project templates, and native plug-ins. It is far ahead of competing products in terms of ecological construction.

  • Compatible with WeChat Mini Program JS SDK

Rich mini-program ecological content can be imported directly uni-app, and is common on the App side. Previous cross-platform development frameworks generally lacked third-party SDKs. Since a large number of SDK manufacturers maintain the Mini Program SDK, it has uni-appbecome the most ecologically rich platform reference in the cross-platform development framework.

  • Compatible with WeChat Mini Program custom components

The Mini Program custom component is a kind of UI component. In uni-app, App, H5, WeChat Mini Program, and QQ Mini Program can be compatible with WeChat Mini Program custom components at the same time. Refer to

  • Compatible with NPM package management system

  • Compatible with weex plugin ecology

uni-app is built-in weex, weexand the native plug-in or ui library can be used. Note weexthat the ecology is not as uni-apprich as it is, and it is generally recommended to use uni-appthe plug-in market.

  • Compatible with common web libraries

uni-appThe H5 side supports all browser APIs. But as we all know, because the js of the applet does not run in the browser, the API of HTML and DOM is not supported in the applet.

uni-appAlthough the App side and the Mini Program have the same architecture, and the logic layer runs independently jscoreinstead of the browser, there are still differences between the App side and the Mini Program:

  • On the one hand, HTML can be loaded through the web-view component, and web-related libraries can be introduced;
  • On the other hand, renderjs can be used to execute js in the rendering layer. At this time, complete echartand threejsother web libraries can be used. (However, for full-end use, it is still recommended to reduce the dependence on the dom library, and you uni-appcan find a full-end compatible library to replace it in the plug-in market)
  • The app side supports various ways of invoking native capabilities
  1. Support native hybrid development
  2. Supports plus JSAPI with more capabilities than applets
  3. Support  Native.js  to directly call native api
  4. Support  uts plugin
  5. Support for  native language plugins
  • App side supports dual rendering engine  uni-applogic layer in independent jscore, and the rendering layer can choose webview rendering and weex engine rendering.
  1. Using webview to render, the whole structure is the same as that of the applet, and the page suffix is ​​vue file at this time.
  2. If the weex engine (modified) is used for rendering, the entire structure is the same as that of the quick app, and the page suffix is ​​nvue file. When using webview to render, you can specify whether to render by the system webview or by the x5 engine.

Guess you like

Origin blog.csdn.net/std7879/article/details/127896755