← Back to home
Comparison · Comms

Threema vs Matrix

Side-by-side trajectory, velocity, and editorial themes.

T
Threema
COMMS
5.0

Threema's feed is a privacy-advocacy blog first, product changelog second

◆ Current state

Threema's feed is its company blog, mixing privacy thought-leadership and security explainers with occasional feature announcements, rather than a structured product changelog. Concrete product news in this window is limited: a new availability status in Threema Work, and earlier the OnPrem DualLock feature and the iOS 7.1 redesign.

◆ Where it's heading

Product-wise, Threema keeps investing in privacy positioning (system-level anonymity, the case against username-only privacy) and in business/enterprise features like Threema Work availability and OnPrem DualLock. The blog's publishing cadence far outpaces its shipped product changes, so this feed reads more as marketing than release notes.

◆ Prediction

The 'what we're working on' teaser points to upcoming app updates but names nothing specific, so the next concrete features are unclear from these entries. Expect the feed to keep leading with privacy advocacy and surface occasional Threema Work / OnPrem feature posts.

M
Matrix
COMMS
6.3

Matrix 1.19 lands encrypted room history sharing and custom emoji, clearing a multi-year MSC backlog

◆ Current state

Matrix ships a spec release roughly quarterly and reports weekly via This Week in Matrix. The ecosystem is mid-transition to Matrix 2.0, where simplified sliding sync and closing E2EE gaps are the dominant threads. Version 1.19 is the headline event of this window; the rest is community, governance, and ecosystem reporting.

◆ Where it's heading

The spec is working through a long-pending MSC backlog: image packs merged, simplified sliding sync accepted, and now encrypted history sharing standardized. Each release chips at features that clients (Element X, FluffyChat, Cinny, Nheko) already shipped ahead of the spec, pulling the ecosystem toward a common Matrix 2.0 baseline.

◆ Prediction

Expect the E2EE-related sliding-sync extension MSCs to be the next priority, since simplified sliding sync is accepted but won't land in a spec release until enough extensions (several supporting encrypted messaging) are also accepted.

See more alternatives to Threema
See more alternatives to Matrix