uni-app actively embraces the community, creating an open, compatible plugin system.

  • uni-app插件市场,https://ext.dcloud.net.cn,是uni-app官方插件生态集中地。有数千款插件,支持前端组件、js sdk、页面模板、项目模板、原生插件等多种类型。在生态建设上远远领先于竞品。请注意尽量在官方市场寻找插件,npm等三方市场没有uni-app兼容性描述,很容易下载到无法跨平台的、仅适配web的插件。

  • Compatible with WeChat Mini Program JS SDK

小程序生态内容可直接引入uni-app,并且在App侧通用。以前的跨平台开发框架普遍缺少三方SDK,由于大量SDK厂商均原厂维护小程序SDK,使得uni-app成为跨平台开发框架里生态最丰富的平台参考

  • Compatible with WeChat Mini Program custom components

The applet custom component is a ui component. The uni-app can be compatible with the WeChat applet custom component in App, H5, WeChat applet, and QQ applet at the same time. [Reference](https://uniapp.dcloud.io /frame?id=%E5%B0%8F%E7%A8%8B%E5%BA%8F%E7%BB%84%E4%BB%B6%E6%94%AF%E6%8C%81)

  • Compatible with NPM package management system

uni-app支持npm包,但注意npm下载的插件很可能不是全端的,大多npm插件仅适配了web。需要全端插件还是要去uni-app插件市场https://ext.dcloud.net.cn去找。

  • Compatible with weex plugin ecosystem

uni-app has built-in weex, and weex native plugins or ui libraries can be used. Note that the ecology of weex is not as rich as that of uni-app. In general, it is recommended to use the plugin market of uni-app.

  • Compatible with common web libraries

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

uni-app的App端虽然和小程序是相同的架构,逻辑层也运行在独立jscore而不是浏览器里,但App端和小程序还是有区别的:

  • 一方面可通过web-view组件加载本地HTML,引入web相关库;
  • 另一方面可通过renderjs实现在渲染层执行js,此时完整echartthreejs等web库均可使用。 (But for full-end use, it is still recommended to reduce the dependence on the dom library. In the plugin market of uni-app, you can find a full-end compatible library instead)
  • App端支持各种调用原生能力的方式
  1. 支持 原生混合开发
  2. Support [plus JSAPI] (http://www.html5plus.org/doc/h5p.html) more capable than applet
  3. 支持 Native.js 直接调用原生api
  4. 支持 uts插件
  5. Support Native Language Plugin
  • App supports dual rendering engines The logic layer of uni-app is in independent jscore, and the rendering layer is optional for webview rendering and weex engine rendering.
  1. 使用webview渲染则整个架构与小程序相同,此时页面后缀为vue文件。
  2. 使用weex引擎(经过改造)原生渲染,则整个架构与快应用相同,此时页面后缀为nvue文件。使用webview渲染时,还可以指定由系统webview渲染还是由x5引擎渲染。
On This Page