yattee's README is 135 words with no installation instructions, and its UI tests need two real accounts
Privacy oriented video player for iOS, tvOS and macOS
At a glance
- What is it?
- A SwiftUI video player for iOS, tvOS and macOS, AGPL licensed, whose version 2 pairs with a self-hosted backend powered by yt-dlp. The feature list is five bullets, one of which has configuration detail. The rest of the substance is in the repository root: a Ruby toolchain driving the release process, an AltStore distribution manifest, and a dotenv file holding credentials for two third-party services.
- Who is it for?
- Yattee is a reasonable choice if you want an Apple platform video client whose data comes from a server you run, and the client/server split is the right shape for that: the app carries the interface and the playback, and the extraction side lives in a separate project you host. Four things to know before you rely on it.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 15 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- yattee/yattee3,815 ★ · +113
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| yattee/yattee | 3.7k | 3.8k |
113 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
There is no installation section at all
The whole file is about 135 words. A title, a subtitle saying it is a privacy oriented video player for iOS, tvOS and macOS, three badge links, a block inviting readers to a beta, five feature bullets, and a licence line. There is no installation section, no App Store link, no TestFlight signup procedure, no system requirements, no troubleshooting and no configuration reference. The beta invitation links a beta page and a Discord invite and a separate documentation site, which is where the guides, roadmap and changelog were moved. So the file's implicit instruction is go and read somewhere else, and the two answers a new user most needs, how to install and where the data comes from, are the two it does not contain. Three named platforms also arrive without any note about how distribution differs between them.
The player is a client, the extraction side is a separate project
One sentence in the beta block does the architectural work: version 2 pairs with a new Yattee Server, a self-hosted backend powered by yt-dlp that the file says supports 1000 and more sites. So the app repository contains no extraction logic at all. You supply the backend, the app talks to it, and that division is why the project can be AGPL licensed as a thin client rather than as a downloader. The repository's own test configuration shows the client is not tied to one kind of backend either: the dotenv file asks for Invidious and Piped endpoints and credentials alongside a Yattee server URL. The site count is a claim about the server project, not about this app, and the README repeats it without a link to a list.
Beta 270, and the release names add nothing to the tags
The three newest releases are 2.0.0-beta.270 on 2026-08-23, 2.0.0-beta.269 on 2026-08-03 and 2.0.0-beta.268 on 2026-07-27. Each release name is identical to its tag, with no build number, no commit reference and no date suffix beyond the tag itself. The pattern says something useful: this application has been in beta for hundreds of builds, roughly one every week and a half for the last three, and there is no stable 2.0 in the visible list. For a client that people install on an Apple device, that matters less than it would for a library, but it does mean the tag you install is a moving target and the beta channel, not a release, is the distribution mechanism the project points at.
A Ruby toolchain runs the release process for an Xcode project
A Swift project with Ruby at the root is not a mistake, and the entries say what each piece is for. There is a `Gemfile` and `Gemfile.lock`, a `.ruby-version`, a `.rubocop.yml` and a `spec/` directory, which together describe a linted, tested Ruby toolchain. That toolchain exists to run the release automation in `fastlane/`, the Xcode coverage reporting configured by `.slather.yml`, and the unused-code detection configured by `.periphery.yml`. The changelog is generated too: a `cliff.toml` sits next to `CHANGELOG.md`, which is the configuration format for deriving release notes from commit history rather than writing them. So the packaging, linting, coverage and release notes of an iOS app are all driven from Ruby scripts, and the Swift code itself lives in an Xcode project.
The UI tests need accounts on two third-party services
The dotenv template at the repository root is a test configuration, and its comments are specific about what is mandatory. Copy it to `.env` and fill in the values. Invidious credentials, an email and a password, are marked as required for the import subscriptions tests. Piped credentials, a username and a password, are marked as required for the import tests. Three optional URL overrides follow, commented out, and their example hosts all sit on one personal-looking domain rather than on the public instances. So the test suite is not hermetic: a contributor running it needs accounts on two services that this project does not control, and the file's defaults point at somebody's own instances. Two service passwords living in a dotenv at the repository root is the other thing to notice.
An Xcode project is the integration surface, and the version 2 icon is already committed
There is no `Package.swift` and no workspace file in the root. What is there is `Yattee.xcodeproj/` alongside `Yattee/` for the app itself, `YatteeTests/`, `YatteeShareExtension/` for the share sheet integration, and `YatteeTopShelf/` for the Apple TV shelf. So the app cannot be consumed as a Swift package; you either install a build or drag the project in. `buildServer.json` declares a build server for Xcode, and `CNAME` is a custom domain file for GitHub Pages, which is how the help site is served from the repository. One entry is ahead of its time: `Yattee2.icon/` holds icon assets for version 2 while the README describes version 2 as still being built and available through a TestFlight beta.
Privacy is the name and the description, not a section
The subtitle calls the app privacy oriented and the repository description says the same, and then the file stops. There is no permissions list, no description of what the app sends and to whom, no account model, and no statement of where the video metadata comes from beyond the pairing sentence with a self-hosted server. The feature list is five bullets and only one of them has any configuration in it: SponsorBlock, with categories to skip that you choose. Everything else is a noun phrase, a queue and history, a player with custom controls and gestures and 4K, fullscreen and Picture in Picture and background audio. So for the one property the project is named after, the README gives you a mechanism to reason about yourself rather than a claim to check.
Editorial conclusion
Yattee is a reasonable choice if you want an Apple platform video client whose data comes from a server you run, and the client/server split is the right shape for that: the app carries the interface and the playback, and the extraction side lives in a separate project you host. Four things to know before you rely on it. The README gives you no installation path at all, and the only distribution signals in the repository are a TestFlight beta page and an AltStore source manifest, so check where you are actually getting the binary from and how re-signing interacts with an AGPL build. The privacy claim is the project's name and description, and the file contains no permissions list, no network description and no threat model, so verify it yourself. The UI tests are not hermetic, since they need real accounts on two third-party services. And the version you would install is a beta: the newest release is 2.0.0-beta.270. Licence terms are AGPL version 3 for the app and its components.
Frequently asked questions
What platforms does yattee support?
iOS, tvOS and macOS, with a native interface built with SwiftUI and customization settings. The features cover the player queue and history, a player component with custom controls and gestures, 4K playback, fullscreen, Picture in Picture, background audio and SponsorBlock with configurable categories.
Does yattee need a separate server?
For version 2, yes. The README says it pairs with Yattee Server, a self-hosted backend powered by yt-dlp which it says supports 1000 or more sites. The repository's own test configuration names Invidious and Piped endpoints and credentials alongside a Yattee server URL.
What license is yattee under?
AGPL version 3, in both the repository metadata and the README's licence line, which covers Yattee and its components. The repository also ships an AltStore source manifest, which is an alternative distribution channel for iOS apps that need re-signing.
Is yattee 2 available yet?
As a beta. The README says version 2 is being built with a refreshed experience and invites readers to join the TestFlight beta for early builds, with guides, roadmap and changelog moved to a separate documentation site. The newest release is 2.0.0-beta.270, dated 2026-08-23.
How do I install yattee?
The README does not give installation steps. It links a beta page for the TestFlight build and a Discord invite, and the repository ships an AltStore source manifest, but no App Store link, sideloading procedure or system requirement appears anywhere in the file.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/yattee-yattee)Star history chart for your README
[](https://hysenlabs.com/projects/yattee-yattee)Was this useful?