Chanty
Chanty's feed is an HR statistics content mill, not a product changelog
A side-by-side editorial comparison of Element X Android and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.
Monthly Matrix client releases grinding steadily toward call and location parity
Element X Android ships on a predictable calendar train (v26.05 through v26.08), each release a mix of one or two user-facing features and a long tail of fixes. The two threads that actually move are Element Call integration and live location sharing, both of which graduated from feature flags in May and have been getting incremental polish since. Accessibility work has been unusually heavy for a client at this stage, with a dedicated TalkBack and screen-reader pass in v26.07.1.
Stalwart is chasing mail RFCs and its own storage layer at the same time
Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.
Element X Android ships on a predictable calendar train (v26.05 through v26.08), each release a mix of one or two user-facing features and a long tail of fixes. The two threads that actually move are Element Call integration and live location sharing, both of which graduated from feature flags in May and have been getting incremental polish since. Accessibility work has been unusually heavy for a client at this stage, with a dedicated TalkBack and screen-reader pass in v26.07.1.
The team is converting flagged experiments into default behavior and then hardening them rather than opening new fronts. Calls are becoming first-class timeline objects — active call rendering in v26.08.0, active participants surfaced in the people list in v26.08.1 — and location sharing is picking up the notification plumbing (MSC4505) it needed to be usable outside the app. QR code login and device linking sit in the visible 'In development' section across several releases, which is the clearest signal of what lands next.
Expect QR code login and the protected device-linking flow to exit the in-development section and ship as defaults within the next one or two monthly releases, with call presence continuing to spread into more surfaces.
Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.
Two threads run through every release. One is RFC coverage across IMAP, JMAP, CalDAV and WebDAV, implemented close to the specification including drafts. The other is a long tail of protocol-conformance fixes, many of them cases where JMAP and IMAP disagreed about the same state. The newest release adds a third: memory and scheduling limits, which is what a server codebase starts doing when deployments get large enough for defaults to hurt.
Expect continued RFC additions across the JMAP and IMAP surfaces, with more of the storage-tuning work that v0.16.18 started as RocksDB deployments scale.
Other Comms products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Element X Android or Stalwart.
Chanty's feed is an HR statistics content mill, not a product changelog
Proton Bridge spends its first release in ten weeks on crashes, memory bounds and dead code
Every manual control Mux ships now arrives with a Robots workflow that does it for you
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
mailcow's release notes are almost entirely upstream security currency.
Openfire keeps its XMPP server current without changing what it is.
See all Element X Android alternatives → · See all Stalwart alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Element X Android and Stalwart are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Element X Android and Stalwart are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top Element X Android alternatives in Comms are ranked by recent ship velocity. Browse the "Element X Android alternatives" section above for the current picks, or visit /alternatives/element-x-android for the full list with editorial commentary on each.
Top Stalwart alternatives in Comms are ranked by recent ship velocity. Browse the "Stalwart alternatives" section above for the current picks, or visit /alternatives/stalwart for the full list with editorial commentary on each.