uni-ui is DCloud's open-source, cross-platform UI component library for the uni-app and uni-app x frameworks, built for Vue developers who want one set of components that runs on every target platform.

What it is

uni-ui is a component library maintained by DCloud alongside the uni-app ecosystem, published under an MIT licence with roughly 2,000 stars and 660 forks. The repository's README focuses on uni-ui x, the newly designed extension component library DCloud provides specifically for uni-app x, which shipped with HBuilderX 5.08 and is deliberately different from the older uni-ui built for uni-app. Compatibility issues were found in some components on certain platforms in HBuilderX 5.07, and versions earlier than that have not been tested.

The concrete problem it solves is cross-platform UI consistency: a developer writes a component once and gets it working across the many targets uni-app compiles to, instead of maintaining separate implementations. It also solves the customisation trap common to component libraries, where styling is buried in component props, so that styling a component means wrapping ever more props — uni-ui x instead puts all style definitions in class, leaving props to control functional logic only.

Key capabilities

• Component set for uni-app x including uni-badge-view, uni-collapse, uni-drag-cell, uni-fab-button, uni-index-bar, uni-link, uni-nav-bar, uni-number-box, uni-rate, uni-refresh-box, uni-tab and uni-time-format.
• Root-node styling applied through the component's class or style, and child-node styling customised externally through externalClass, so no component source needs editing.
• Theming entirely through CSS variables, with no colors and no text hardcoded anywhere, which also keeps the components free of translation requirements.
• Performance work on DOM hierarchy control, bundle size and execution time, taking advantage of template and style pre-compilation in uni-app x's steam mode while still supporting non-steam mode.
• Code-first rendering instead of binary assets: no font files are shipped, arrows are built from a view with a bottom border and transform rotation, and the uni-tab sunken middle button uses SVG rather than an image, so the UI is legible and editable as code.
• A neutral visual style with no house look imposed, in the same spirit as uni-app's built-in and mini-program components.
• An upgrade mapping table from legacy uni-ui components to their uni-app x equivalents, for example uni-badge to uni-badge-view, uni-fab to uni-fab-button, uni-datetime-picker to the built-in picker with mode=date, and uni-drawer to the built-in page-container.

Who uses it and how

• Vue developers building uni-app x projects in HBuilderX 5.08 or later, where the component compatibility tables apply.
• Teams upgrading an existing uni-app project to uni-app x, using the mapping table to decide which components to swap, which to replace with built-in components such as list, form, loading and swiper, and which to drop because they are simple enough to write directly.
• Developers who need project-specific branding, styling every component through class, externalClass and CSS variables rather than accepting a fixed theme.
• Contributors and users coordinating on component feedback through the uni-ui-x IM community group linked from the README.

Getting started

Individual components are installed from their DCloud plugin pages on ext.dcloud.net.cn (each row of the component table links to its own plugin entry), with documentation hosted at the project homepage https://uniapp.dcloud.io/component/uniui/uni-ui.html.

How it compares

The README does not compare uni-ui against a list of paid products, and no competing component libraries are named in the facts provided. It stands alone in this registry as the DCloud-maintained component layer for uni-app and uni-app x, positioned against uni-app's own built-in components rather than against a third-party library.

When to use it — and when not

A large share of the legacy uni-ui components have no uni-app x equivalent — marked 无 in the mapping table, including uni-card, uni-easyinput, uni-grid, uni-icons, uni-search-bar, uni-tag and uni-transition — so teams migrating should expect to write some UI themselves or use built-in components. The project carries 107 open issues, and compatibility is tied to specific HBuilderX versions, with components documented against 5.08 and earlier versions untested, which matters for anyone pinned to an older toolchain.