# APTV: an Apple-platform player for m3u8 live streams > APTV is an App Store app for iPhone, iPad, Apple TV, Apple Watch and Mac that plays m3u8 live streams from remote m3u playlists. The repository itself holds the README and a m3u folder with test playlists, not the player's source code. **Kimentanm/aptv** — 📺 A tool for playing m3u8 file - Repository: https://github.com/Kimentanm/aptv - Stars: 2,845 · Forks: 253 - Language: Unknown - License: not declared - Published: 2026-09-28 · Updated: 2026-09-28 · Language: en - Canonical page: https://hysenlabs.com/projects/kimentanm-aptv ## What APTV does that a generic video player does not An m3u8 stream is a playlist of short transport-stream segments, refreshed as the broadcast continues. A desktop video player can open one URL, but it will not keep a channel list, group entries, or show what is on now. APTV is built around that list. The README describes it as "一个用于播放电视直播流的多功能工具类App", a multi-purpose tool for playing live TV streams, and its feature list starts with adding a remote m3u file and playing m3u8 files. Around those two core actions it adds channel categories, favourites, a current-channel preview image, a programme guide fetched for the channel, and iCloud sync across devices. The audience is narrow and clear: people who already have an IPTV subscription or a free playlist and want a native client on Apple hardware instead of a browser tab or a VLC window. It is not a source of channels. Nothing in the README suggests APTV bundles licensed content; the only playlists shipped in the repository are labelled test sources. ## How a remote m3u file becomes a playing channel The data flow starts with a URL. The README's first feature line is adding a remote m3u file, so the app reads a playlist hosted somewhere reachable over HTTP rather than importing a local file. That playlist supplies channel names, grouping and stream URLs. When a channel is selected, the app plays the m3u8 stream at that URL. Two features depend on what the source itself provides. Channel playback (回看) requires the live source to support it, and the programme guide is fetched per channel rather than generated by the app. The preview image is described as being obtained in real time for the current channel, which implies a separate request rather than a cached thumbnail. iCloud sync carries the configuration, favourites and playlist setup between devices, which is why the same list can appear on a phone, a TV and a watch without re-entering it. The repository layout matches this: the top level contains README.md, a logo, and an m3u directory. There is no player source tree, no build script and no package manifest, so the published app and the repository are two different things. ## Installing APTV and adding a first playlist APTV is distributed through the App Store, not from this repository. The README links to the App Store listing under the identifier id1630403500 and states that the app is available for iOS, iPadOS, tvOS, watchOS, macOS and, in beta, visionOS. There is no command-line install, no Homebrew formula and no sideloading instructions in the README. If you are not on an Apple platform, the README gives you nothing to install. The first real use is adding a source. The README publishes two test playlists, one for general IPTV channels and one for playback testing, and explicitly says they are for product testing only and must not be redistributed. Copy the raw URL of the playlist you want to try: ```bash # test playlists published in the repository's m3u/ directory https://raw.githubusercontent.com/Kimentanm/aptv/master/m3u/iptv.m3u https://raw.githubusercontent.com/Kimentanm/aptv/master/m3u/aptv-playback.m3u ``` Paste that URL into the app's configuration page as a remote m3u file. The README's screenshots show a configuration screen and a settings screen, and the channel list is what you should see once the playlist loads. If individual channels fail, the README's own advice is to refresh the configuration in the configuration centre, because the test playlists are updated irregularly. Playback of a channel that supports it should offer the catch-up option; on a source without that support, only the live stream is available. ## Where APTV stops being the right tool The platform list is the first boundary. The README names iOS, iPadOS, tvOS, watchOS, macOS and a visionOS beta. Android, Windows and Linux users are not addressed at all, and the repository contains no build instructions that would let them compile something themselves. The second boundary is source dependency. APTV plays what your playlist contains; if the stream URL is dead, the app has nothing to fall back on. The README is candid about this in the test-source note, saying the lists come from the network, that the author only collects and organises them, and that the author takes no responsibility for their privacy or copyright. A user who expects a curated, always-working channel line-up will be disappointed. Third, the repository is not the application. It holds a README, two logo files and an m3u directory. Anyone hoping to read the player's code, file an issue against a specific playback bug, or build a variant is looking at the wrong artefact. Finally, the README's roadmap section lists DLNA casting, aggregated configuration and a search centre as future plans, which is a plain statement that those features are not present today. ## APTV against VLC and Kodi for the same playlist VLC opens an m3u8 URL and plays it, and it runs on nearly every desktop and mobile platform. The difference is what surrounds playback. VLC has no concept of a subscribed remote playlist that refreshes, no per-channel programme guide, no iCloud sync between a phone and a TV, and no CarPlay interface. Kodi comes closer on the living-room side: it has a PVR IPTV Simple Client that consumes an m3u playlist and an EPG, and it runs on Android TV boxes and Raspberry Pi hardware that APTV will never touch. What Kodi does not give you is an App Store install on an Apple Watch, or a CarPlay screen. The trade is therefore hardware and maintenance against convenience. If your playback device is an Android TV box or a Linux mini-PC, Kodi is the more direct answer. If it is an Apple TV, an iPhone and a Mac that should share one channel list, APTV is built for exactly that arrangement, and the repository's m3u directory gives you a playlist to test that arrangement with before committing to a paid subscription source. ## Maintenance, licence and what the repository does not say The last push to the repository was on 2026-09-21, so activity is recent, but the repository is mostly a README and a folder of playlists, and the README itself says the test sources are updated on no fixed schedule. Do not read repository activity as a release cadence for the app; the App Store listing is where versions actually ship, and the README does not document a changelog or a version history. The licence field is empty. No LICENSE file appears in the top-level entries, which list .gitignore, README.md, logo.ico, logo.png and m3u/. Without a licence file, the default position is that no permission is granted for reuse, so treat the repository contents as all rights reserved and check the App Store listing's own terms for the app. The README's note on the test playlists adds a second restriction: they are for testing only and must not be redistributed, and the author disclaims responsibility for their privacy and copyright. If you plan to ship anything derived from these files, that is a question for a lawyer, not for the README. ## Conclusion APTV fits people already inside Apple's ecosystem who want a native, remote-playlist front end for m3u8 channels on a phone, TV, watch or Mac and are willing to supply their own sources. It is the wrong tool on Android or Windows and for anyone who wants bundled, licensed channel line-ups: the README lists no Android or Windows build, the repository carries no licence file, and the test playlists are marked as test-only. Before relying on it, open the m3u/iptv.m3u and m3u/aptv-playback.m3u playlists and confirm the channels you need still resolve, since the README says they update on no fixed schedule. ## FAQ ### Is APTV available for Android? No. The README lists iOS, iPadOS, tvOS, watchOS, macOS and a visionOS beta, and never mentions Android. The App Store link it provides is the only distribution channel described. ### How do I add my own m3u playlist to APTV? The README's first listed feature is adding a remote m3u file, so you supply the URL of a playlist hosted online rather than importing a local file. The repository's m3u/iptv.m3u is the example playlist it publishes for testing. ### Does APTV include channels, or do I need my own source? You need your own source. The only playlists in the repository are labelled test sources, and the README states they come from the network, that the author only collects and organises them, and that they are for product testing only and must not be redistributed. ### Why does channel catch-up not work for some channels in APTV? The README lists channel playback as requiring support from the live source. If the stream you added does not provide catch-up data, the app has nothing to play back. ## Sources - [Issues](https://github.com/Kimentanm/aptv/issues) - [Kimentanm/aptv on GitHub](https://github.com/Kimentanm/aptv) - [README](https://github.com/Kimentanm/aptv/blob/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/kimentanm-aptv