A lightweight Vue.js UI component library for mobile H5 and multi-platform mini-programs with JD.com design style.
NutUI is a Vue.js UI component library specifically built for mobile web and mini-program development. It offers a collection of over 80 components styled according to JD.com's design guidelines, solving the need for consistent and efficient UI development across H5 and multiple mini-program platforms.
Frontend developers building mobile web applications (H5) and cross-platform mini-programs for platforms like WeChat, Alipay, and JD.com using Vue.js.
Developers choose NutUI for its enterprise-ready design system from JD.com, seamless multi-platform support via Taro, and comprehensive component coverage tailored for mobile scenarios, reducing development time while ensuring visual consistency.
京东风格的移动端 Vue 组件库,支持多端小程序(A Vue.js UI Toolkit for Mobile Web)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
With over 80 high-quality components covering mainstream mobile scenarios, it accelerates development for common UI patterns like forms, navigation, and feedback.
Via Taro integration, it enables writing once and deploying to H5, WeChat, Alipay, and JD mini-programs, saving effort for multi-platform projects.
Based on JD.com's visual specifications, it provides a cohesive, battle-tested look that aligns with large-scale mobile applications.
Offers component-level theming with over 700 CSS variables, allowing deep visual adjustments while maintaining structural integrity.
Server-side rendering support is explicitly noted as being in the testing phase in the README, making it risky for projects requiring stable SSR.
Components adhere closely to JD.com's specific visual specs, which may require significant CSS overrides or theme work to adopt a different design system.
Supports only English, Indonesian, and Traditional Chinese, which could hinder projects targeting other languages or regions without additional localization effort.
Reliance on Taro for mini-program support adds configuration overhead and potential compatibility issues compared to simpler, single-platform libraries.