// the find
CarGuo/GSYGithubAppWeex
Weex 超完整的开源项目，功能丰富，适合学习和日常使用。GSYGithubApp 系列的优势：我们目前已经拥有 Flutter、Weex、ReactNative、Kotlin View、Kotlin Jetpack Compose ，Compose MultiPlatform，Harmony ArkUI 七个版本，功能齐全，项目框架内技术涉及面广，完成度高，持续维护，配套文章，适合全面学习，对比参考。
A GitHub client app built with uni-app (Vue 3 + Vite + TypeScript) that targets H5, WeChat mini-program, Android, and iOS from a single codebase. It's part of a larger GSY series that implements the same GitHub client in seven different frameworks — Flutter, React Native, Kotlin, Compose, Harmony ArkUI, and this one — making the series useful for side-by-side comparison of how different ecosystems handle the same real-world app. The repo name says Weex but the actual code migrated to uni-app at v2.0.
The cross-framework comparison angle is the real value here — if you're evaluating uni-app vs Flutter vs React Native for a mobile project, having identical apps in each lets you benchmark bundle size, scroll performance, and API ergonomics against the same feature set. The supply-chain cooldown script (scripts/check-deps-cooldown.mjs) that blocks deps published less than 15 days ago is a genuinely thoughtful addition that most projects skip. The trending page has a three-level fallback chain — custom API to GitHub Search to local mock — so it degrades gracefully instead of just breaking. The Issue feature set is more complete than most GitHub clients: inline editing, long-press menus, lock/unlock, close/reopen, all in one screen.
The repo carries years of dead weight from the Weex era: the entire platforms/ directory is old Weex Android and iOS native shells with checked-in Pods, a debug.keystore, and Gradle wrapper jars — none of which apply to the current uni-app build. That history in the directory tree (not just git history) will confuse anyone cloning it fresh. The e2e tests are stored outside the repo in %TEMP%/gsy-e2e/ by design, which means CI can't actually run them portably and the 14/14 PASS claim in the README is not reproducible from checkout. iOS hasn't been verified on real hardware and is listed as an open roadmap item — so 'one codebase, four targets' is more aspiration than fact for iOS users right now. Vitest unit tests for stores and utils are also still on the roadmap, leaving the business logic untested.