AirPodsDesktop dropped 32-bit Windows, titles every 0.6.x release Beta, and credits both a rival and an Apple BLE privacy paper
☄️ AirPods desktop user experience enhancement program, for Windows and Linux (WIP)
At a glance
- What is it?
- SpriteOvO/AirPodsDesktop is a GPL-3.0 Windows tray utility for AirPods, written in C++ with Qt, last pushed to main on 2026-09-19. The repository description promises Linux too, the README header says Windows only, and the release titles carry the word Beta on every tag from 0.5.2 upward.
- Who is it for?
- AirPodsDesktop is a reasonable pick if you are on x64 Windows and want battery levels, ear detection and a lower-latency audio path from an open source tray app, and the migration note is the strongest part of the documentation because it tells existing Qt5 users exactly what changes. Two things to resolve first.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 19 days ago.
- What is it written in?
- Mainly C++, 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
- SpriteOvO/AirPodsDesktop3,944 ★ · +482
| Repository | 2026-09-28 | 2026-11-15 |
|---|---|---|
| SpriteOvO/AirPodsDesktop | 3.5k | 3.9k |
482 Stars in the last 48 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Every release title carries the word Beta, including 0.6.0 and 0.6.1
Three tags are visible, and the pattern is in the titles rather than the numbers.
v0.5.2 is titled v0.5.2 Beta, tagged 2026-09-03. v0.6.0 is titled v0.6.0 Beta, tagged 2026-09-06. v0.6.1 is titled v0.6.1 Beta, tagged 2026-09-19.
So the naming is stable, the version line is pre-1.0, and the word Beta is not a signal about maturity on any particular release. It is doing the job the leading zero already does. That is a defensible choice for a utility that depends on undocumented hardware behaviour, and it does tell you two things at once: nobody is promising a 1.0, and the cadence is fast.
Sixteen days separate the first and last of those tags, with a minor bump in the middle, which is a rapid release rhythm for a project that also has to keep three README translations aligned.
The last push to main is dated 2026-09-19, essentially the same moment as the newest tag, so the branch and the release are in step here rather than ahead of it.
The README header says Windows and the repository description says Windows and Linux
The two descriptions of this project do not match.
The repository description reads as an AirPods desktop user experience enhancement program for Windows and Linux, with Linux marked as work in progress. The subtitle in the README, centred under the title, reads: enhance your AirPods experience on Windows.
The System requirements section agrees with the README rather than the description. It states that official builds support Windows 10 1809 or newer and Windows 11 on x64, and that 32-bit Windows and ARM64 are not supported. There is no mention of Linux anywhere in that section, and no build target for it.
So the file a reader actually opens describes a Windows-only application, while the metadata that search results and API listings show describes a cross-platform one with Linux coming.
That distinction matters for anyone evaluating. If you are on Linux, the description says your platform is on the way and the README says nothing about it, which is a promise with no date and no build. If you are on Windows, the README is accurate and the description overstates.
Windows 10 1809 is also worth noting as a floor. That is a specific 2018 build, and it is the earliest release the current binaries claim to run on.
The Qt5 32-bit line was dropped, and the in-app updater carries your settings across
One sentence in the System requirements section carries most of the migration story: existing Qt 5 and Win32 users can migrate through the in-app updater while keeping their user settings.
That tells you what changed between the two lines. The previous generation was Qt 5 and 32-bit Windows. The current one is Qt 6.8.3 and x64 only. Both the windowing toolkit major version and the processor architecture moved at once, which is the kind of change that normally loses settings.
The updater is the stated mitigation, and the promise is specific: settings are kept. It does not say what happens to anything else, such as a saved device profile or any per-ear configuration, and there is no rollback instruction in the README.
The dependency list corroborates the move rather than describing it. Qt appears at 6.8.3 under an LGPLv3 notice, and the rest of the list is a C++ stack: spdlog for logging, cxxopts for options, cpr for requests, nlohmann/json for parsing, SingleApplication to enforce one instance, magic_enum for reflection, and two Boost header libraries, pfr and stacktrace, under BSL-1.0. Two fonts ship in the tree, Inter and Noto Sans TC, both under the SIL Open Font License.
Four licences in one dependency list is normal for a desktop application and worth reading once rather than assuming.
Three README files must be kept aligned by hand
The language line at the top of the file offers English, Simplified Chinese through README-CN.md and Traditional Chinese through README-TW.md.
Three files, one project, and no tooling mentioned. The Contribute section instead states the rule as a manual obligation: keep README.md, README-CN.md and README-TW.md aligned in section order, features, commands, links and credits when updating project documentation.
That is a specific and sensible instruction, and it names five things to keep in step, which tells you what has drifted before. It is also five checks on every documentation change, done by hand.
The rest of the contribution surface is smaller than that: open an issue from a chooser template, submit a pull request, or translate, with the translation guide in CONTRIBUTING.md.
Two other files at the root point the same way as the README sync rule. There is AGENTS.md and there is CLAUDE.md, so the project carries two instruction files for coding agents. Neither is referenced in the README, and neither is described in the contribution section.
The credits name a competing app and a paper on Apple's BLE privacy leaks
The Credits section has three entries and two of them are unusual.
The first is OpenPods, a separate project for talking to AirPods on Linux and Windows, credited as a source.
The third is MagicPods, linked to its own website. MagicPods is a commercial product in the same problem space, doing the same job on Windows. The file credits it rather than naming it as a comparison, which is a restrained choice and leaves the reader to draw their own conclusion about where the alternative sits.
The middle entry is the one that deserves attention. It is a paper titled Discontinued Privacy: Personal Data Leaks in Apple Bluetooth-Low-Energy Continuity Protocols, hosted as a document on Inria's HAL.
A tray app that reads AirPods battery levels over Bluetooth Low Energy is crediting research into how Apple's Continuity protocols leak personal data. That is a project acknowledging, in its own credits, that the protocol it depends on has documented privacy problems, and it is doing so without a paragraph of commentary about it.
The practical consequence for an evaluator is that the risk here is not theoretical. Whatever this app sends over the air, the underlying protocol has been the subject of published leakage research.
One dependency link points at a fork rather than the upstream project
The third-party list has eleven entries, and ten of them link where you would expect.
Qt 6.8.3 links to the Qt installer under an LGPLv3 notice. spdlog, cxxopts, nlohmann/json, SingleApplication and magic_enum all link to their own repositories under MIT. pfr and stacktrace link to their Boost organisation repositories under BSL-1.0. Inter and Noto Sans TC link to licence files inside the project's own Source tree, under the SIL Open Font License 1.1.
The exception is cpr, the HTTP client library. Its entry links to github.com/whoshuu/cpr, which is an individual account rather than the project's own organisation, and the licence link beneath it points at the same place.
Forking a dependency and building against the fork is a normal thing to do, and it is often the right call when you need a patch. But here it is invisible: nothing in the entry says the fork exists, no patch is referenced, and there is no note in the README about why the fork rather than the upstream release. The version is not pinned either, so what you get is whatever that branch holds at build time.
The two font entries have the mirror-image shape. Their links are repository-relative paths into Source/Resource/Font, which is how the licences are vendored in the tree, and it means those two entries are the only ones in the list that resolve inside the project rather than on an external site.
The README has no build command, and the preview table has two empty cells
There is a Build and test section and it is two lines long. It points to Docs/Build.md for Windows prerequisites, build commands and tests.
So the README you are reading contains no compiler invocation, no dependency installation step and no test command. All of that is in a separate document in the repository, which is the right place for it and means the README is a description of the product rather than a build guide.
The repository layout supports that split. There is a Docs directory, a CMake directory alongside CMakeLists.txt, a Source directory, a Tests directory, a vcpkg.json for C++ dependency management, and both a .clang-format file and a .clang-format-ignore file, so formatting is scoped with an explicit exclusion list.
The Preview section is a two-column table for light and dark themes, and both cells are empty in the file. The table is a placeholder for screenshots, which means a reader arrives at the visual claims, animated popups and theme switching, with nothing shown to check them against.
The four features are stated plainly and are the whole product: battery information in the notification area, automatic ear detection with media playback control, a low audio latency mode, and animated device popups with light, dark or system themes.
Editorial conclusion
AirPodsDesktop is a reasonable pick if you are on x64 Windows and want battery levels, ear detection and a lower-latency audio path from an open source tray app, and the migration note is the strongest part of the documentation because it tells existing Qt5 users exactly what changes. Two things to resolve first. Decide whether the Linux work in progress is something to wait for, since the README header does not mention it at all. And read the dependency list before building, because four licences are in play and one link points at a fork rather than the upstream project.
Frequently asked questions
how to install airpodsdesktop
There is no install command in the README; it links to Docs/Build.md for Windows prerequisites and build commands. The dependency list is managed through vcpkg with a vcpkg.json at the root, and official builds target Windows 10 1809 or newer and Windows 11 on x64.
Does AirPodsDesktop support 32-bit Windows or ARM64?
No. Official builds support Windows 10 1809 or newer and Windows 11 on x64, and 32-bit Windows and ARM64 are not supported. Existing Qt 5 and Win32 users are directed to the in-app updater, which keeps their user settings.
Is AirPodsDesktop available for Linux?
The repository description marks Linux as work in progress, while the README subtitle and the system requirements section describe a Windows-only application with no Linux build target and no date for one.
What can AirPodsDesktop do?
Four things: battery information in the notification area, automatic ear detection with media playback control, a low audio latency mode, and animated device popups with light, dark or system themes.
How does AirPodsDesktop compare with MagicPods?
The README does not compare them. It lists MagicPods in its Credits section alongside OpenPods and a research paper on privacy leaks in Apple's Bluetooth Low Energy Continuity protocols, without characterising any of the three.
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/spriteovo-airpodsdesktop)Star history chart for your README
[](https://hysenlabs.com/projects/spriteovo-airpodsdesktop)Was this useful?