# Thunderbird for iOS: a native email client, still being built

> The thunderbird-ios repository is a ground-up attempt to bring the Thunderbird email experience to iOS, and it is explicitly not usable yet. The current work is architecture, backend integration and foundations, with the goal of a TestFlight build for early testing before any App Store release.

**thunderbird/thunderbird-ios** — Thunderbird for iOS – Open Source Email App for iOS

- Repository: https://github.com/thunderbird/thunderbird-ios
- Stars: 1,257 · Forks: 48
- Language: Swift
- License: MPL-2.0
- Published: 2026-10-19 · Updated: 2026-10-19 · Language: en
- Canonical page: https://hysenlabs.com/projects/thunderbird-thunderbird-ios

## A native client rather than a wrapped web interface

Thunderbird for iOS is an open source email application for Apple devices, and the README describes the intent plainly: this project aims to bring the Thunderbird email experience to iOS devices, and it is a ground up development effort to create a high-quality email client tailored for iOS.

The phrase ground up is doing the work. The alternative to this project is a mail client on iOS that is a web interface in a wrapper, and the gap between the two is the difference between an application that can do notifications properly, that can integrate with the system, that can use the background processing the platform grants, and one that cannot. Tailoring for iOS also means making different decisions from the desktop client, since a phone is a triage device and a desktop is a working surface, and the vision paragraph says as much.

The design goal is stated in terms of user efficiency: a mobile email platform that enhances user efficiency through focused triage, seamless desktop integration, and a suite of productivity-enhancing services. Three ideas, and each of them is a commitment about what the app is for.

The project is written in Swift, it is licensed under the Mozilla Public License 2.0 with the text in the `LICENSE` file, the default branch is `main`, and the last push was on 2026-10-15. There are no GitHub releases, which is what you would expect for an application that has not yet reached a distributable build.

The rest of the README is the part a potential contributor should read first, and it does not oversell anything.

## The status: architecture, backend, foundations

The README has a section called Current Status, and it opens by saying the repository is at an early stage of development.

Three bullets cover what is happening and what is not. The development focus is establishing the app's architecture, the backend integration and the foundational features. The functionality is not yet functional or ready for production use, and key features like reading and writing emails will follow in future stages. And the vision is the one already quoted, focused triage, desktop integration and productivity services.

So the ordering is worth being explicit about, because it tells a reader where the project is. The architecture comes first, then the backend integration, then the foundational features, and only then the behaviour a user would recognise as an email client. Reading and writing mail is the last item on that list, not the first, and it is listed as future work.

That is a defensible sequence for a client that has to talk to an existing account infrastructure, and it is also the reason a user should not expect a build today.

The current goal is stated separately and is more concrete: to have a version of Thunderbird for iOS available on Apple's TestFlight for early testing. The full App Store release will come at a later stage, and the README says it will most certainly include the standard features one would expect from an email client.

The phrase most certainly is doing a small amount of work, and it is a useful signal. It says that the feature set of the eventual release is not yet decided, which for a client means that the shape of the account model, the sync and the extension surface are still open questions.

## The repository layout tells you it is a real client project

The root directory is the clearest description of the project that exists, because the names say what kind of application this is.

There is `Thunderbird.xcworkspace/` and a `Thunderbird/` directory, which is the standard shape of a Swift application that is built from an Xcode workspace, and a `Thunderbird.xctestplan`, the test plan for the bundle, so the tests are a first-class part of the build rather than a script somebody runs. There is a `Core/` directory, which in an application of this size is where the shared model and services live, and a `Bolt/` directory sitting beside the Swift code, which is where the project keeps its networking engine component. There is `config/` for the build configuration, `CI/` for the continuous integration, and `fastlane/`, the usual home of the TestFlight and App Store upload steps, which fits a project whose stated next milestone is a TestFlight build.

There is a `docs/` directory that contains the contribution guide, and the root also has `CONTRIBUTING.md`, `SECURITY.md`, an `.editorconfig`, a `.swift-format` configuration for the Swift formatter, and a `.github/` directory.

The `SECURITY.md` file is worth noting in a mail client specifically. An email client handles credentials, and the security policy is where a project states how to report a vulnerability rather than filing it as a public issue, and the fact that it is in the root of a repository that is not yet usable is a sign about the priorities.

The development tooling is also modern, with Swift Package Manager implied by the workspace layout, and the presence of both a workspace and a test plan means the project is set up for a large application with several targets rather than a small demo.

## How to help when the code is not ready

The contributing section is unusually careful, and its care is the interesting part.

It opens by saying that at this stage the project is still being built from the ground up, and that while it might not be ready for active contributions yet, here is how you can help. Then it lists four routes.

Report issues, using the GitHub issue tracker, to report ideas or potential problems and help refine the vision. Follow development, by following the repository and the community discussions on Matrix. Prepare to contribute, by familiarising yourself with the project and keeping an eye on the contribution guide for updates. And translate, if you speak a language other than English, which the README says is easy and takes a few minutes for a first success, with the translation hosted on Weblate.

The third route is the one that tells you most about the state of the project. The contribution guide is something to watch rather than to follow yet, which is a polite way of saying that the contribution process is not settled. A project at the architecture stage does not know yet what its reviewers will look for, and publishing a contribution guide before that is known tends to produce a guide that is wrong in six months.

The translation route is the one that a contributor can start today, and it is the most useful of the four for a project that is not yet functional, because translations are needed long before the code is.

The last route is funding. The mobile and desktop applications are funded through financial contributions by users, and the README asks for support with the reasoning that it helps build a secure, private and free email client for iOS.

## The community plumbing around a mobile project

Thunderbird is a Mozilla project, and the community arrangements are described in the README in enough detail to be worth reading, because they say where the decisions actually get made.

There is a general Matrix space, the Thunderbird community channel, and two channels specifically for this application, one for general chat about Thunderbird for iOS and one for development. There is a mobile-planning discussion group on topicbox for planning rather than chat, and the monthly updates on the Thunderbird Blog, in a category for mobile news, which is the closest thing the project has to a status page.

There is Mozilla Connect for ideas and voting, and the Mozilla Community Participation Guidelines are linked with an explanation of how the project treats each other and works together, which is the norm for a project under a foundation's governance rather than a company's.

Two details deserve a mention. First, the translation link points at the Weblate project for the Android client rather than the iOS one, which is consistent with a project where the localisation effort starts where the existing user base is. Second, the project asks people to follow the repository and the discussions, which is what a project without a public build asks for, since there is nothing to install yet.

The Thunderbird ecosystem more broadly is signposted at the end, with the main site and the mobile site, and the README closes there rather than with a call to action, which fits a project whose main call to action is to watch it.

## Where this project is the wrong choice

The honest limits are in the status section, so the review has to start there.

The first is that it cannot be used. The app is not functional, it is not ready for production use, and reading and writing email is future work. So for a person who needs mail on an iPhone in 2026, the answer from this repository is that it does not exist yet, and the useful answer comes from an existing client plus an account setup that suits them.

The second is that the scope is a rewrite rather than a port. A ground-up iOS client has to re-implement the account model, the sync, the threading, the search, the extensions and the notifications, and each of those is a place where the desktop client already has years of behaviour encoded. That is the cost of the approach, and it is paid for by the result, which is a client that is native rather than a browser in a shell.

The third is the delivery uncertainty. The TestFlight goal is a commitment, not a schedule, and the phrase about the App Store release including the standard features one would expect says that the feature set is still open. A team that has to plan around a date should watch the Matrix channels and the monthly blog updates rather than the repository's commit history.

The alternative, for a user, is an existing mail client on the App Store, and the difference in approach is the difference between a client that is a rendering surface for a web interface and one that talks to the account infrastructure natively. The alternative, for a contributor, is the desktop and Android clients, which are shipped and which have the same goals and a much lower barrier to contributing to, since the translation route described in the README already points there.

## Conclusion

Thunderbird for iOS is worth following if you want an email client that is not a wrapper around a web interface, and worth contributing to if the Thunderbird ecosystem is where your work belongs. It is the wrong tool for anybody who needs email on an iPhone today, because the app is not functional and cannot read or write mail yet, and the honest answer for a user is an existing client plus a strong preference for the Thunderbird account ecosystem. Before contributing, read the contribution guide in `docs/` and the current status on the Matrix channels, since the README says the project might not be ready for active contributions yet, and expect the release to arrive through the `fastlane/` pipeline as a TestFlight build first and an App Store submission later.

## FAQ

### Can I use Thunderbird for iOS yet?

No. The README says the repository is at an early stage of development, that the app is not yet functional or ready for production use, and that key features like reading and writing emails will follow in future stages. The current goal is a version available on Apple's TestFlight for early testing, with the App Store release at a later stage.

### What is the Thunderbird for iOS project working on at the moment?

Establishing the app's architecture, the backend integration and the foundational features, with a stated vision of a mobile email platform built around focused triage, seamless desktop integration and productivity-enhancing services.

### How can I contribute to Thunderbird for iOS?

By reporting issues on GitHub, following development in the Matrix channels for general chat and for development, watching the contribution guide in the docs directory for updates, and helping with translations through Weblate. The README notes that the project might not be ready for active contributions yet.

### What licence is Thunderbird for iOS under?

The Mozilla Public License 2.0, with the text in the LICENSE file at the root of the repository. The README also notes that the mobile and desktop applications are funded through financial contributions by users.

## Sources

- [Issues](https://github.com/thunderbird/thunderbird-ios/issues)
- [License: MPL-2.0](https://github.com/thunderbird/thunderbird-ios/blob/main/LICENSE)
- [README](https://github.com/thunderbird/thunderbird-ios/blob/main/README.md)
- [thunderbird/thunderbird-ios on GitHub](https://github.com/thunderbird/thunderbird-ios)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/thunderbird-thunderbird-ios