youhunwl/TVAPP: an APK index for Android TV boxes, and the TVBox source lists that feed it

What TVAPP actually is: a download index, not an app

TVAPP is a GitHub repository, not software you install. The README describes it as a collection that integrates TV-version apps across film and TV, games, karaoke and tools, and it is organised as a table plus a directory tree. The top-level entries are the categories: 影视/ for film and TV, K歌/ for karaoke, 电视直播/ for live channels, 实用工具/ for utilities, 娱乐应用/, 教育学习/ and 运动健身/. There is also a TVBox/ folder, a wiki/, a LICENSE, and several MX Player APKs sitting at the repository root.

The audience is narrow and specific. It is someone with an Android TV box or an Android-based smart TV who already knows what an interface source (接口源) is, because several of the listed apps ship empty and expect you to paste one in. The README says as much for TVBox: the entry is labelled 空盒原版 (empty-box original), split into white-shell and black-shell variants, and it 需配置接口源, requires configuring an interface source. The same note appears for 影视仓. If that sentence means nothing to you, this repository is not your entry point; the apps inside it are the entry point, and TVAPP is where you find them.

The repository is Apache-2.0, which covers the repository contents. It does not cover the APKs, which are third-party builds, and the README's own banner states the resources come from contributors sharing them for personal study, that commercial use is prohibited, and that rights holders should make contact for removal.

How the index is organised and how a source gets into an app

The mechanism is a table and a set of folders, and the table is the part that carries information you cannot get from a file listing alone. Each row gives an app name, a version, a download link, a status marker and a remark. The status column uses a green circle for working and a red circle for at least one entry: 七星影仓 v6.1.7 is marked red, while its sibling 七星影仓V3 v3.0.35 is green. The remark column is where the real detail lives, and it is not decorative. 影视仓 v6.2.7 is annotated 安卓6.0及以上，不支持纯血鸿蒙 (Android 6.0 and above, does not support pure HarmonyOS). 影视仓V3 v3.0.36 is annotated as compatible with Android 4.4 and below, for old TVs and boxes. OK影视Pro v5.2.1 notes that online subtitles, danmaku search, VLC on TV and MPV on mobile require activating Pro by watching an ad in the About screen, and that users who object should take the standard build.

The data flow for a source-based app is the part worth understanding before you download. You install the shell, open it, and it has no content. You then supply an interface source, a URL or a config that the app reads to populate its catalogue. The README points to its own 接口源 and 直播源 sections further down and invites contributors to share working ones. Nothing in the repository validates those URLs; a source that worked when it was added can stop resolving later, which is why the README asks users to file an issue when an app stops working.

Two entries sidestep the source step entirely. 小苹果影视 v1.6.2 is described as having hundreds of built-in line sources and needing no interface input, 安装即用 (install and use). 月光宝盒Box is described as a single-repository build with built-in data sources and AI ad filtering. That distinction, built-in versus bring-your-own-source, is the single most useful axis when reading the table.

Installing from the repository and configuring a first source

There is no build step and no package manager. The README's download column links straight to APK files either at the repository root or under a category folder, and the pattern is consistent: raw file links under the main branch. A TVBox download link looks like this.

https://github.com/youhunwl/TVAPP/raw/refs/heads/main/TVBox

That path is a folder, not a file, and the README says the white-shell and black-shell versions are inside with their own version notes. Read the folder before picking a build. For a named APK the link points at the file directly.

https://github.com/youhunwl/TVAPP/raw/refs/heads/main/影视/影视仓/影视仓_6.2.7_32位电视.apk

Sideloading is the only route here. These are APKs, not store listings, so the box needs to allow installation from unknown sources. The README does not document that device-side step; it assumes you already sideload. Once installed, a shell app such as TVBox or 影视仓 opens with an empty catalogue and asks for an interface source. The README keeps its 接口源 list further down the page and asks readers to share working ones, but it does not publish a stable, versioned config URL you can point at programmatically, so treat any source you use as something you obtained and verified yourself.

If you want to skip that step, pick a build the README describes as self-contained: 小苹果影视, 月光宝盒Box, 欧歌影视 v6.1.7 or 七星影仓V3, all of which are listed as carrying built-in sources. 七星影仓V3 additionally requires you to tap 配置 then confirm, per its remark.

The Android version split is the constraint that decides most installs

The most concrete engineering detail in the README is the Android compatibility matrix, and it is the thing most likely to waste your evening if you skip it. The repository does not maintain a single current build; it maintains parallel branches of the same app for different API levels. 影视仓 v6.2.7 targets Android 6.0 and above. 影视仓V3 v3.0.36 exists specifically for Android 4.4 and below. OK影视 v5.1.6 has a separate 安卓5专版 (Android 5 edition) folder alongside the standard TV build. 七星影仓 has the same V3 split.

This is a maintenance cost, not a feature. Older boxes are common in this category, and the upstream projects have moved their mainline builds forward, so the repository carries frozen older builds so those devices keep working. Frozen means frozen: the README gives no indication that the V3 lines receive the same updates as the mainline ones, and the version numbers tell the story, with 影视仓 at v6.2.7 and 影视仓V3 at v3.0.36.

There is a second compatibility note that is easy to miss. 影视仓 v6.2.7 does not support 纯血鸿蒙, the pure HarmonyOS line. If your TV runs that rather than Android, the mainline build is not for you, and the README does not offer a HarmonyOS alternative. Check the remark column for your exact device before downloading, because the table's green status marker tells you the entry is current, not that it will run on your hardware.

Where TVAPP is the wrong tool

TVAPP is a catalogue, and a catalogue cannot fix the two problems that actually break these setups: dead sources and untrusted binaries.

The source problem is structural. A shell app with a user-supplied interface source depends on a URL that someone else hosts. When that URL changes or disappears, the app does not degrade, it shows nothing. The README's response is procedural: report broken software via an issue. That is a reasonable community workflow and a poor fit for anyone who needs a media setup that works without periodic intervention. If you want a player that manages its own content pipeline, the repository itself lists Kodi v22.0, described as a professional multimedia player for local storage, network shares and streaming, with a link to a wiki tutorial at /wiki/kodi.md. That is a different model: Kodi is the software, and you supply the media or the add-ons.

The trust problem is also structural. These are third-party APK builds, several explicitly modified: the README lists 欧歌影视魔改 (a modified build), a 去引流 (de-advertised) variant of 金调KTV, and multiple karaoke apps described as unlocked membership versions. The README itself warns, on several karaoke rows, not to believe any prompt asking you to pay for an update. That warning is a signal about the provenance of these files. If your requirement is a vendor-supported, auditable client, this repository is the wrong place to look, and no amount of status markers changes that.

Alternatives and how they differ in approach

The clearest alternative is inside the repository: Kodi. The difference is architectural rather than a matter of quality. TVAPP distributes Android APKs that are mostly thin shells pointing at remote catalogues; Kodi is a single application that plays local files, network shares and streams, and extends through add-ons. With Kodi you install one thing and manage your own library. With TVBox or 影视仓 you install a shell and then depend on a source list that lives somewhere else. Neither is universally better, but the failure modes are different: Kodi fails when your library or network does, a source-based shell fails when someone else's URL does.

A second alternative is to go straight to the upstream projects. The README names FongMi影视, OK影视, 小猫影视 and XMBOX, and several of these publish their own releases. 小猫影视 is described as a cross-platform player for Android, Windows, macOS, iOS and Linux supporting VOD and JS extension sources, and uz影视 is listed as covering iOS, Android, Windows and Mac. If you want a phone and desktop client alongside the TV, those upstream projects cover more platforms than the TV-box table suggests, and going direct means you read version notes from the people who wrote the code rather than from a mirror.

The trade-off is convenience against provenance. TVAPP's value is that it puts versions, Android requirements and status markers in one table, which is genuinely faster than checking four upstream repositories. Its cost is that you are trusting an intermediary's copy of each binary, and the README's own commercial-use prohibition and removal-on-request notice make clear that this is a redistribution index, not a distribution channel.

Maintenance, upgrade cost and licence scope

The repository is not archived and the last push was on 2026-09-17, four days before this writing, so it is being touched. That says the index is current; it says nothing about whether any individual APK still works, and the README treats breakage as a user-reported event rather than something the maintainer verifies.

Upgrade cost falls on you, and it is recurring rather than one-off. Because versions are pinned to specific builds with specific Android requirements, an upgrade is not a single action: you re-download an APK, re-sideload it, and in the source-based apps re-check that your interface source still resolves. The README gives no rollback guidance, no changelog per app beyond the version string in the table, and no checksums for the APK files, so there is no documented way to confirm that a file you downloaded matches what the maintainer intended to publish.

The licence position needs care. The repository is Apache-2.0, which is a permissive licence covering the repository's own contents. It does not extend to the APKs, which are third-party builds of third-party apps, and the README's banner states the resources are for personal study, that commercial use is strictly prohibited, and that infringing material will be removed on request. Apache-2.0 on the index and the licensing of the binaries inside it are two separate questions, and the README answers only the first one clearly. That is a description of what the files say, not legal advice; if you intend to deploy any of this in a commercial setting, the README's own wording already tells you not to.

Editorial conclusion

TVAPP suits people who already run an Android TV box and want one place to compare APK versions and TVBox or 影视仓 interface sources without hunting through forums. It is the wrong choice if you need a signed, audited distribution channel or a player with its own maintenance team: the repository is an index, the binaries are third-party APKs, and the README states the resources are shared for personal study only and must not be used commercially. Before installing anything, check the Android version note for your device (影视仓 v6.2.7 needs Android 6.0+, 影视仓V3 v3.0.36 covers Android 4.4 and below) and read the per-folder version notes under 影视/, because the top-level table does not repeat them.

Frequently asked questions

Official sources

1. Issues
2. License: Apache-2.0
3. Project website
4. README
5. youhunwl/TVAPP on GitHub