What Happens When Your Weekend Tauri Experiment Goes Viral

You build a small app to learn a new framework, push it to GitHub, and go to bed. A few days later you've got a pile of stars, a sudden audience, and a nagging feeling that maybe you shouldn't have done that. That's the story behind HGhub, a third-party client for a short-drama streaming service, and it's worth reading for the way the author handled the attention.

What It Does

HGhub is a desktop and mobile client built with Tauri 2 and Rust. It targets Windows, macOS, and Android (with iOS instructions included), and it presents a Fluent-style interface with immersive vertical-video playback for short-form drama content.

The architecture is straightforward. On the frontend you've got React 19, TypeScript, Vite 7, and Tailwind CSS 4. Playback runs through hls.js for HLS and AES-128 streams. The Rust backend handles networking with reqwest and rustls, splits into a request layer, business commands, cover decryption plus an HLS proxy with caching, and token persistence. The README notes the app talks to a single unified edge endpoint rather than scattering calls across many routes.

Importantly, the project doesn't host, store, or distribute any video. All content comes from third-party sites, and the README is explicit that the app is meant for learning and technical exchange.

Why It's Cool

The most interesting thing about HGhub isn't really the app. It's the author's response to it going unexpectedly popular.

• The license flip is the story. After getting a flood of stars, the author switched the license to PolyForm Noncommercial 1.0.0 and added a lot of protective language to the README. They openly say the star count is undeserved and describe the project as a toy built while trying out Tauri 2's mobile support. That kind of honesty is rare.

• The scope got deliberately narrowed. Rather than chasing growth, the author stopped maintaining any upstream data-fetching work and shifted focus to UI/UX and usability. PRs and Issues still get low-frequency responses. If a rights holder complains, the plan is to archive or privatize the repo immediately.

• There's a real warning about a fake fork. The README calls out a separate repository that took an old version of the source and bolted on card-key verification and VIP paid unlocking. The author states plainly that HGhub never has and never will include paywalls or ads, and tells anyone who installed the impostor to uninstall it. That's a practical public-safety note you don't often see.

• The usage rules are unusually specific. Don't batch-download, don't hammer the upstream API, don't strip watermarks, don't repost the stream links, don't shrink the built-in caches. These aren't generic platitudes — they're the exact behaviors that would get the upstream endpoints banned for everyone.

• The build setup is documented in real detail. Notes on exFAT drives needing node-linker=hoisted, pnpm 10 versus 11 differences around build allowlists, and separate config files for macOS, iOS, and Android packaging targets. If you're learning Tauri 2 for mobile, this is a decent reference.

How to Try It

If you want to poke at the code (and you should treat it as a study project, not a product), clone the repo from github.com/minireel/hghub.

First-time setup:

pnpm install
pnpm app:dev      # desktop hot reload
pnpm app:build    # Windows NSIS installer; macOS .app + .dmg

On macOS, install the Xcode Command Line Tools first (xcode-select --install).

For Android (requires the SDK and NDK, with ANDROID_HOME and NDK_HOME set):

pnpm android:init
pnpm android:dev
pnpm android:build

There's also an iOS path using Xcode, xcodegen, and CocoaPods with your own signing, documented step by step in the README, targeting iOS 15.

If you just want the app, the author says the only official download channel is GitHub Releases, and the source page ships no binaries. Anything from a random netdisk or QQ group is not official.

Final Thoughts

HGhub is best read as a case study in what happens when a hobby project outgrows its author's intent. The Tauri 2 and Rust stack is genuinely interesting if you're evaluating cross-platform mobile builds, and the README's careful boundaries — noncommercial license, no upstream scraping, clear takedown policy — are a template for anyone shipping something that leans on someone else's data. It's not a product you should build a workflow around, and the author would be the first to tell you that. But as a slice of open-source reality, it's worth a look.

Follow @githubprojects for more developer tools and open source projects.