Tammy

Opening Tammy for the first time feels different from other messaging apps. There is no phone number to enter, no SMS code to wait for. Instead, the app asks for a Matrix server address right away. This is the decentralized backbone that sets it apart from mainstream messengers. For someone used to WhatsApp or Telegram, this step can feel unusual. But it is also the moment where the app's core promise becomes clear: you are not locked into a single provider's infrastructure.

The onboarding flow assumes the user already knows what Matrix is. That might be a barrier for some. However, for those who have been looking for a way to escape centralized platforms, it is a welcome change. The interface is clean and modern, with a left-side room list and a main chat area. Colors are muted, and the typography is easy on the eyes. There is no clutter, no ads, and no promotional banners pushing premium upgrades. It is a straightforward chat client that does one thing and does it well.

Once logged in, the app loads the room list quickly. Syncing with the Matrix server happens in the background. Messages appear without noticeable delay. The app uses end-to-end encryption by default for private conversations. This means that only the participants can read the messages. Even the server operator cannot see the content. That is a strong privacy guarantee that many other apps either do not offer or make optional.

Managing Multiple Accounts Across Servers

One of the standout capabilities is multi-account support. The app allows users to add several Matrix accounts and switch between them seamlessly. Each account can be on a different server. This is useful for people who have a personal account on one homeserver and a work account on another. The switching process is instant. There is no need to log out and log back in. The app also supports multiple profiles within a single account, adding another layer of flexibility.

This feature interacts with the decentralized nature of Matrix in a practical way. A user can be in a public room on server A while also having private conversations on server B. The app keeps everything organized under one roof. Notifications arrive for all accounts simultaneously. This workflow is not something that every Matrix client handles well. Some clients make multi-account use cumbersome. Tammy makes it feel natural. The room list updates to show which account each room belongs to, so there is no confusion about which identity is being used in which conversation.

Real-World Performance and Notification Reliability

Push notifications are a make-or-break feature for any messaging app. Tammy handles them through UnifiedPush. This is a system that lets users choose their own push notification provider instead of being forced to use Google's Firebase Cloud Messaging. For users who care about privacy, this is a major advantage. The notifications are reliable. Messages arrive promptly, even when the app is in the background. Developers have highlighted this as a personal highlight, and user reports confirm that it works well in practice.

However, the app is not without rough edges. The comparison table of Matrix clients shows that Tammy lacks several features that competitors offer. There is no support for threads, which makes following long conversations difficult. Polls are also missing. For communities that rely on these features, Tammy might feel incomplete. The app also does not implement sliding sync, a newer protocol that speeds up initial sync and reduces battery usage. This means that the first sync after a fresh install can take longer than on clients that support sliding sync.

Some users have reported issues with hardcoded endpoints. This means that the app might not work with certain Matrix gateways that use non-standard configurations. The developers are aware of this and have discussed opening an issue to address it. For most users connecting to standard Matrix servers like matrix.org, this is not a problem. But for those running their own custom setups, it is something to keep in mind.

Technical Depth and Development Activity

The app is built with Kotlin and Compose Multiplatform. This allows it to run on Android, iOS, Windows, macOS, Linux, and the web. The codebase is open source under the GNU Affero General Public License v3.0. This means that anyone can inspect the code, verify its security, and contribute improvements. The development is active, with regular updates appearing in the GitLab repository. The changelog shows a steady stream of fixes and improvements, including decryption fixes that are critical for a secure messaging app.

One interesting detail is that Tammy is a sibling of Timmy, the TI-Messenger used by German public health insurance companies. Both share the same underlying Trixnity SDK. This connection gives Tammy a level of engineering rigor that comes from being used in a regulated healthcare environment. The SDK is battle-tested with potentially millions of users. That is a reassuring fact for anyone concerned about stability and security.

The app is available as a Flatpak for Linux, an MSIX for Windows, and through the Snap Store. The Android version can be installed via the Play Store or by sideloading the APK. The developers have mentioned that an F-Droid release is planned. This will make it even easier for users who prefer to avoid Google's ecosystem. The iOS version is already available on the App Store.