# AntennaPod for Android: what the GPL-3.0 podcast manager actually does > AntennaPod is an open source podcast manager for Android, licensed GPL-3.0 and distributed through Google Play and F-Droid. It is a solid choice for Android users who want local control of subscriptions and playback, and the wrong choice for anyone who needs an iPhone, Windows or browser client. **AntennaPod/AntennaPod** — A podcast manager for Android - Repository: https://github.com/AntennaPod/AntennaPod - Website: https://antennapod.org - Stars: 8,193 · Forks: 1,807 - Language: Java - License: GPL-3.0 - Published: 2026-09-22 · Updated: 2026-09-22 · Language: en - Canonical page: https://hysenlabs.com/projects/antennapod-antennapod ## What AntennaPod solves, and for whom Google Play and F-Droid are full of podcast players that tie your subscription list to an account, a recommendation feed or an ad network. AntennaPod takes the opposite position. The README calls it "the easy-to-use, flexible and open-source podcast manager for Android", and the repository carries the whole client under GPL-3.0. That licence is the point: anyone can read the code, build it, or fork it if the project changes direction. The audience is narrow and clear. You need an Android phone or an Android Wear device, because the repository contains app/ and app-wearos/ and nothing else in the way of a client. You want subscriptions stored locally on the device rather than on a vendor's server. You are willing to install from Google Play or F-Droid, the two distribution links the README gives, instead of an app store that bundles a social layer. If any of those conditions does not hold, AntennaPod is not the tool you are looking for, and the rest of this article explains why. ## How the Android app is put together The top-level layout tells you more about the architecture than the README does. AntennaPod is a multi-module Gradle project, not a single app folder with everything dumped inside. The modules are split by responsibility: model/ holds the data types, parser/ handles feed formats, net/ does network access, storage/ persists data, playback/ runs audio, ui/ holds screens, system/ covers platform integration, and event/ carries internal events between components. That separation is why the project can support a Wear OS companion without duplicating feed logic. The README itself is thin on internals. It points contributors at CONTRIBUTING.md for build instructions and describes beta testing as a program you join through the project wiki. What the repository does confirm is the shape of the codebase: Java as the primary language, Gradle as the build system, and a develop branch as the default target. A build therefore behaves like any other Android project, which is exactly what the README says. The practical consequence of this layout is that you cannot treat AntennaPod as a service. There is no server component in the repository and no web front end. All parsing, storage and playback happen on the device. That is a design choice with real consequences for sync, which I cover further down. ## Installing AntennaPod and a first real use The README gives two install routes and no third one. The Google Play badge links to the package de.danoeh.antennapod, and the F-Droid badge links to the same package on f-droid.org. There is no APK download link in the README, so if you want a sideloaded build you are expected to build it yourself. If you are building from source, the README says to refer to CONTRIBUTING.md and that you build it "just like any other Android project". The README does not print a Gradle command, so the exact invocation is not documented on the front page; the repository does ship the gradlew wrapper and the gradle/ directory, which is how an Android project of this shape is normally built. Once the app is on the device, the first useful action is adding a feed by URL. The README does not walk through the screens, but the repository's ui/ module and the store screenshots are the only sources for what the interface looks like. The workflow a new user follows is: open the app, add a podcast by its feed address, then let the parser/ module read the RSS or Atom document and the storage/ module keep the subscription locally. Nothing in that chain requires an account. If you are contributing rather than listening, the README points at the forum for discussion and at the GitHub issue tracker for bug reports, with a request to read CONTRIBUTING.md first. It also notes that a bug reported during the beta period is likely to be fixed before the next stable release, while one reported later may wait a full beta cycle. That is worth knowing before you file anything. ## Where AntennaPod stops: no iOS, no Windows, no web client The most common misconception about AntennaPod is that it is a cross-platform podcast service. It is not. The repository contains app/ and app-wearos/, both Android targets. There is no iOS project, no desktop application and no browser client in the tree, and the README links no such thing. Anyone searching for AntennaPod on an iPhone, a Windows machine or in a browser will not find an official client, because the project has not shipped one. A second limitation follows from the same architecture. Because subscriptions and playback state live on the device, there is no first-party server to sync between two phones or between a phone and a tablet. The README does not document a sync service, and the module list contains no sync component. If your listening is split across devices, that is a real gap rather than a missing preference. A third constraint is the build requirement. Building from source means a working Android toolchain and Gradle setup. The README delegates all of that to CONTRIBUTING.md, which is honest but means the repository front page will not get a newcomer to a running build on its own. For a listener this does not matter, since Google Play and F-Droid cover installation. For someone who wants to modify and rebuild the app, it does. ## AntennaPod against a hosted podcast service The clearest alternative is a hosted podcast platform, the kind that keeps your subscription list on its own servers and offers an app for every platform you own. The difference is not cosmetic. A hosted service can sync playback position between your phone and your laptop because the state lives on a server it controls. AntennaPod cannot do that, because the state lives in the storage/ module on your device and there is no server in the repository. What you trade away in exchange is control. AntennaPod is GPL-3.0, so the client code is available to read and to fork, and the README points translators at a Weblate page rather than a closed localization pipeline. A hosted platform typically gives you a polished multi-platform experience in return for an account and whatever data policy it operates under. Neither position is universally better. If you listen on one Android phone and care about licence terms and local data, AntennaPod fits. If you switch between an iPhone, a desktop and a browser, a hosted service will save you from managing three separate subscription lists by hand. ## Maintenance, releases and the GPL-3.0 licence The repository is not archived, and the last push was on 2026-09-20. Releases are frequent: 3.12.0 on 2026-08-14, 3.12.1 on 2026-09-05, and 3.12.2 on 2026-09-18. That cadence matters for upgrade cost, because it means security and playback fixes arrive as point releases rather than waiting for a major version. If you install from Google Play or F-Droid, you get those updates through the store and pay nothing in maintenance effort. If you build from source instead, the cost is different. You are tracking the develop branch, which the repository sets as the default, and you carry the toolchain yourself. The README's beta testing section is worth reading in that case: it explains that bugs caught during beta are likely to be fixed before the stable release, and bugs caught later may wait a full beta cycle. A source builder who never joins the beta program is effectively testing stable releases after everyone else. The licence is GPL-3.0, with the text in the LICENSE file. That is a copyleft licence, which means derivative distributions carry obligations the project states in that file. I am not giving legal advice here; if you plan to redistribute a modified build, read the LICENSE text and, where it matters to you, get proper advice. For a normal user installing from a store, the licence is mostly a guarantee that the source stays available. ## Conclusion Adopt AntennaPod if you listen on Android and want a GPL-3.0 client you can install from F-Droid or Google Play without an account. Do not adopt it if you need an iPhone, Windows or browser client, because the repository ships only app/ and app-wearos/ modules and the README links no such client. Before committing, verify Android Auto behaviour and background playback on your own phone, and check whether the release you install has a matching tag rather than a develop build. ## FAQ ### Is AntennaPod free to use? Yes. The README distributes it through Google Play and F-Droid with no paid tier mentioned, and the project is licensed under GPL-3.0. ### Is AntennaPod open source? Yes. The repository is the official AntennaPod source, the primary language is Java, and the LICENSE file carries the GPL-3.0 text. ### Is AntennaPod on iPhone? No. The repository contains app/ and app-wearos/, both Android targets, and the README links only Google Play and F-Droid for installation. ### What is the AntennaPod app? It is a podcast manager for Android. The README describes it as the official repository of "the easy-to-use, flexible and open-source podcast manager for Android". ## Sources - [AntennaPod/AntennaPod on GitHub](https://github.com/AntennaPod/AntennaPod) - [License: GPL-3.0](https://github.com/AntennaPod/AntennaPod/blob/develop/LICENSE) - [Project website](https://antennapod.org) - [README](https://github.com/AntennaPod/AntennaPod/blob/develop/README.md) - [Releases](https://github.com/AntennaPod/AntennaPod/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/antennapod-antennapod