dcloudio/uni-app

Choose this fork only if its experimental Harmony/iOS/`uni-app x` changes are the point. If you want an actively maintained, broadly compatible `uni-app` base, upstream is the safer choice.

Prefer this fork if you need its Harmony/UTS/tooling customizations and can absorb merge debt. Prefer upstream if you want the freshest, broadly maintained uni-app x line with lower maintenance risk.

Prefer this fork only if you need an old, already-fixed legacy uni-app snapshot and can live without modern upstream progress. For new work or active maintenance, upstream is the better default.

Prefer upstream unless you explicitly need this fork's local patches. This fork suits teams that want a frozen, customized codebase and can absorb the maintenance cost; it is a poor fit for adopters who want current upstream features, active fixes, and lower risk.

Prefer this fork only if you want its customized uni-app x toolchain and bundled integrations. If you want the most current upstream fixes, docs, and benchmark work, upstream is the safer choice.

Choose this fork only if you specifically want a private, lightly maintained copy of upstream. If you want new capabilities or an actively differentiated downstream, there is no evidence this fork provides them; the main value is low-diff proximity to upstream, while the main drawback is being behind current upstream work.

Choose this fork if you want a customized, platform-tuned uni-app branch and do not need to stay close to upstream. Avoid it if you want the safest long-term path, because it is materially behind and appears optimized for local modifications rather than clean upstream tracking.

Prefer this fork only if you need the older 2020-era behavior or its extra ad/platform documentation. For new adoption, the upstream project is the better choice because this fork is stale and materially behind current uni-app/uni-app x development.