dcloudio/uni-app

A cross-platform framework using Vue.js

View on GitHub ↗Jump to charts ↓

dcloudio/uni-app has 41k+ stars and 3.5k+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on August 31st, 2026
Created on July 12th, 2018
Open Issues & Pull Requests: 711 (+0)
GitHub issues: Enabled
Number of forks: 3,705
Total Stargazers: 41,616 (+0)
Total Subscribers: 505 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.0 days
Mean response time: 180.1 days
90th percentile: 694.2 days
Tracked items: 1,234

Maintainer activity

6 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in five opened in the past year never receives a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "question" is answered fastest, typically in about 7 hours, while "enhancement" waits about 4 months. 74% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 52% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 296
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 698 days
Stale 30+ days: 291
Stale 90+ days: 278

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • enhancement (98)
  • question (98)
  • 不明确复现步骤、未提供复现工程 (56)
  • 无后续反馈将自动关闭 (46)
  • app (44)
  • mp (40)
  • bug (39)
  • uni api (39)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

uni-app is a cross-platform framework using Vue.js to develop applications for multiple platforms from a single codebase.

uni-app addresses the problem of maintaining separate codebases for different platforms by allowing developers to write once and deploy to iOS, Android, Harmony, web, and various mini-programs including WeChat, Alipay, Baidu, Douyin, Feishu, QQ, Kuaishou, DingTalk, Taobao, JD.com, and Xiaohongshu. The framework offers two versions: the original uni-app using web-view rendering for apps, and uni-app x, the newer generation with native rendering on app platforms. According to the README, uni-app x achieves rendering speeds two to three times faster than native implementations on Android, iOS, and Harmony, and maintains frame rates two to four times higher than native in long-list scrolling tests. The tool supports JavaScript, TypeScript, and UTS—a TypeScript-like language that compiles to Kotlin on Android, Swift on iOS, ArkTS on Harmony, and JavaScript on web and mini-program platforms.

Developers should choose uni-app if they need to target multiple platforms without context-switching or if they are building mini-programs, apps, or web applications individually. The framework is particularly suited for teams wanting to leverage Vue.js across all frontend targets. The README emphasizes that even for single-platform projects, uni-app serves as a capable mini-program framework, app framework, and web development framework. The tool is positioned as AI-friendly, using familiar Vue templates and JavaScript/TypeScript that reduce token consumption and error rates in AI-assisted development.

The project maintains a substantial user base, with almost all open issues originating from external users rather than the core team. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker is dominated by enhancement requests and questions, with many issues tagged as lacking clear reproduction steps or example projects.