hongguo-player is a Windows and macOS client for a Chinese short drama app

A third party client for a service it does not own

hongguo-player is a desktop client for a Chinese short drama service, described as a version made for the computer so that you can watch without an Android emulator. The reasoning given is plain: watching short dramas on a phone is convenient, but if you are already at a computer, picking up the phone for a few episodes, or starting an emulator, is a nuisance.

The feature list is long and consumer oriented. There is an immersive browsing mode over the recommendation and category feeds with the mouse wheel or arrow keys to switch, and content is preloaded as you scroll. Episodes and seasons play automatically one after another and the app remembers where you stopped. There is search with input suggestions, multi dimensional filtering including completed and ongoing series, ranking lists, new releases and a release calendar. Followed shows and scheduled ones produce a reminder when the app opens.

The important context is in the notice at the end. This is an unofficial third party client built by one developer, not related to the official service, published free for personal study and exchange, and resale is prohibited. The repository is used only to publish the installers and contains no source code. That last point shapes how the project can be judged, and it is where the licence field for the repository is empty, because there is no code to license.

Video playback leans on two Windows runtimes

The Windows package is a zip archive that you extract and run, no installer required. Alongside the executable the archive contains a MicrosoftEdgeWebview2Setup.exe installer for the WebView2 runtime, an HEVC video extension package whose file name is in Chinese and ends in .appx, and a text instructions file. All of them have to stay in the same folder as the program, because on the first run the application installs the missing runtimes itself, and WebView2 needs a network connection to do that.

The HEVC extension is the more consequential of the two. A machine without it plays the audio of an episode with no picture, which is the failure mode the FAQ spends most of its words on. The guidance is to use the restart program button in the player, then to restart the machine if that did not work, and to install the extension package by hand if the automatic install failed. The README also notes that remote desktop and virtual machine sessions usually have no hardware decoding available and will fall back to software decoding with a higher CPU load, and that the settings panel has a software decoding checkbox for garbled or black pictures.

Since version 1.1.5, the client is said to fall back to software decoding automatically when hardware decoding is unavailable, so the older symptom is largely a thing of the past for current builds.

The macOS build is universal and unsigned

The macOS download is a single universal archive that works on both Intel and Apple silicon. You unzip it and drag the app into Applications.

The app is not signed, so Gatekeeper will object on first launch. The README documents the standard workaround for an unsigned app, which is to strip the quarantine attribute from the bundle:

xattr -cr /Applications/红果短剧.app

That command removes the extended attributes macOS applies to downloaded files, which is what triggers the cannot verify developer and damaged messages. It is worth understanding what it does before running it, since it disables the check that produced the warning in the first place, and it applies to that one bundle rather than the system as a whole.

The Windows build has the mirror image of the same situation. If Windows says it has protected your computer, the README says to choose more information and then run anyway, and it explains why: the program has not purchased a code signing certificate. An unsigned binary is the normal state for a single developer shipping a personal project, and it is also the reason the macOS and Windows first run experiences differ so much.

A local playback service that firewalls can block

The FAQ has a section on the message that the program cannot connect to the local playback service, and the explanation is specific: the application starts a small service on the machine at 127.0.0.1 to feed video to the player, and it does not reach the outside network for that.

When a firewall or security product blocks that loopback service, the player has nothing to play. The fix offered in the app is a one click allow that needs administrator confirmation, and the alternative is to tick the program in the Windows firewall allow an app to communicate list, or to add it to the trust list in 360 or Huorong style security software.

This is worth flagging because it is the one place where the client asks for permission that touches the machine's security posture. A local service bound to 127.0.0.1 is a common and reasonable pattern for a desktop application, but the request arrives as a firewall rule change, and the honest way to evaluate it is to understand what the service does before allowing it rather than after.

Updates are handled in the same place. When a new version is available the program prompts, and the restart and update action replaces only the main executable. The releases also carry a standalone exe for the main program for that purpose, while new installations are told to take the zip.

Windows and macOS behaviour differs in the small ways

Two features behave differently by platform, and the README is upfront about it.

The first is the global keyboard shortcut. The default bindings are said to match the Douyin web version and can be changed by the user. The second is automatic paste, which does not exist here, but the closest equivalent is the small window mode: the window can be pinned on top so you can keep an episode running while you work, and in a stealth mode it pauses and hides itself when the mouse moves away.

The small window mode is also where the vertical video handling pays off. When an episode is a vertical short drama, the window narrows to fit the picture rather than leaving black bars on both sides.

The quality options are worth knowing about too. The default is the highest quality, and there is an optional enhancement mode offering sharpening and Anime4K for animated drama. When the aspect ratio of the picture and the window are close, the frame fills the window automatically.

The interaction features are the parts that make it feel like the mobile app rather than a video player: danmaku with likes, replies and a +1 button, comments expanding on the right of the picture, and reviews, all of which the README says sync with the mobile app. There is also a sharing feature that copies a link the phone app can open directly, and pasting someone else's share link makes the app play it.

An account is optional, and the data stays local

The FAQ answers the two questions that decide whether someone installs it. It is free, and you do not need to log in to watch. Your favourites, likes, viewing history and scheduled shows are stored on the machine when you are not logged in, and once you sign in with a phone number they sync with the mobile app.

That is a sensible design for a third party client. The default state requires no credentials, so you can try the application and decide later whether you want the synchronisation, and the local storage means the interesting data stays where the application can read it.

The price question has a simple answer, which is that there is none. The README also states the application is free and without advertisements, which is the other half of what a third party client for a free service is offering.

Feedback has a defined path: a feedback button in the left panel of the program that accepts an optional email address, notifies you when the issue is resolved, and allows a continued conversation with the author after a reply. There is also the repository issue tracker and a QQ contact listed in the README.

A distribution repository rather than a codebase

The top level of the repository contains a README and a docs directory. There is no source, no build configuration and no license file, and the README says so explicitly: the repository is only used to publish the installation packages and does not contain source code.

The topics listed give a hint at the stack. They include golang and wails, which is the pairing that produces a native desktop shell around a web front end, and vue3, which is the front end framework. The list also names hevc, macos, windows, video-player, short-drama, duanju, desktop-app and hongguo.

So the application is a Wails application, a Go binary that hosts a Vue 3 interface in a web view, which is also why the Windows build needs the WebView2 runtime at all. That runtime is not an accident of packaging, it is the component that renders the interface.

For a reader evaluating the project, this is the key point. There is nothing to fork, nothing to build from source, no issue tracker that maps to a commit, and no licence that grants rights to the code. The maintenance question is answered by the release tags instead, which show v1.2.5 on 2026-10-19, v1.2.4 on 2026-10-17 and v1.2.3 on 2026-10-17, and by the download page, which serves the current Windows and macOS builds by architecture.

Editorial conclusion

hongguo-player suits someone who watches short dramas on a desktop and wants to do it without an Android emulator, since the client runs on Windows 10 and 11 and on both Intel and Apple silicon Macs and needs no account to browse. It is the wrong thing to build on, because the repository publishes installers only and contains no source code, so there is nothing to audit, fork or extend. Before installing, read the notice that the app is unsigned, expect to allow the WebView2 runtime and the HEVC video extension, and note that if the local playback service is blocked by a firewall or security product, you have to permit it explicitly.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. yangbin1322/hongguo-player on GitHub