Maddy
A one-binary mail server learning to behave like production infrastructure.
A side-by-side editorial comparison of Element iOS and Rocket.Chat — release velocity, themes, recent moves, and the top alternatives to consider.
Renamed Element Classic, this client now ships one small fix every few months
Element iOS was renamed Element Classic in v1.11.32, and the release log since then reads like a maintenance branch: single-PR releases spaced weeks to months apart, mostly dependency bumps, build-tooling changes and one user-visible change at a time. The one substantive thread is device verification — a permanent disclaimer banner for unverified sessions arrived in 1.11.35, was temporarily disabled in 1.11.37 because users had no way to reset from the verification screen, got the Reset flow wired up in 1.11.38, and was reinstated as mandatory in 1.11.39.
Rocket.Chat is building for the air-gapped enterprise, and adding an AI layer on the way
Rocket.Chat ships on a release-candidate train where a single .rc.0 carries every functional change and the RCs that follow it are pure version bumps. The 8.7.0-rc.0 drop is the substantive one: AI Search with semantic message results and optional OpenAI-compatible answers, FIPS-mode support across the monolith and all six microservices, phishing-resistant server-side OAuth, and an offline license flag that suppresses every outbound call to Rocket.Chat Cloud. Underneath, a systematic migration is replacing deprecated DDP methods with REST endpoints ahead of 9.0.
Element iOS was renamed Element Classic in v1.11.32, and the release log since then reads like a maintenance branch: single-PR releases spaced weeks to months apart, mostly dependency bumps, build-tooling changes and one user-visible change at a time. The one substantive thread is device verification — a permanent disclaimer banner for unverified sessions arrived in 1.11.35, was temporarily disabled in 1.11.37 because users had no way to reset from the verification screen, got the Reset flow wired up in 1.11.38, and was reinstated as mandatory in 1.11.39.
The rename is the clearest signal of direction: this is the legacy client, kept working rather than extended. Recent releases raise the minimum supported OS to satisfy a Jitsi dependency, keep the Xcode toolchain current, and adjust CI — the work of a codebase being maintained, not developed. The verification arc is the exception, and even that is about closing an encryption-hygiene gap rather than adding capability.
With mandatory verification now reinstated and its reset path in place, the remaining work in this branch looks like dependency and toolchain upkeep plus security patches. The entries give no indication of new feature work, so the cadence should stay sparse and single-item.
Rocket.Chat ships on a release-candidate train where a single .rc.0 carries every functional change and the RCs that follow it are pure version bumps. The 8.7.0-rc.0 drop is the substantive one: AI Search with semantic message results and optional OpenAI-compatible answers, FIPS-mode support across the monolith and all six microservices, phishing-resistant server-side OAuth, and an offline license flag that suppresses every outbound call to Rocket.Chat Cloud. Underneath, a systematic migration is replacing deprecated DDP methods with REST endpoints ahead of 9.0.
Two pushes are converging. One is regulated and sovereign deployment — FIPS-compliant cryptography behind a licensed fips module, air-gapped workspaces that never phone home, ABAC attribute stores via Virtru in 8.6, and OAuth hardened with PKCE, CSRF and state validation plus 2FA enforcement on social logins. The other is an AI surface, introduced as AI Search plus an AI Center configuration page rather than a scattering of features. The DDP-to-REST work is the plumbing both depend on, and it is gated on the 9.0 boundary.
Expect 8.7 to reach general availability with AI Center expanded past search into a configurable model-provider surface, and the remaining DDP methods retired as 9.0 approaches. Whether the fips and offline license modules become a distinct compliance tier or stay bundled with the existing enterprise plan is not visible in these entries.
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 iOS or Rocket.Chat.
A one-binary mail server learning to behave like production infrastructure.
Friendica keeps betting on being the fediverse node that speaks everyone else's protocols.
The original federated social network now ships roughly once every two years.
Six releases, and every one of them is a security update in some form.
Twilio is selling trust: branded calls, scoped keys, and stricter sender vetting.
Notion is turning Custom Agents into event-driven workers with their own runtime and billing.
See all Element iOS alternatives → · See all Rocket.Chat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rocket.Chat is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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. Rocket.Chat is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top Element iOS alternatives in Comms are ranked by recent ship velocity. Browse the "Element iOS alternatives" section above for the current picks, or visit /alternatives/element-ios for the full list with editorial commentary on each.
Top Rocket.Chat alternatives in Comms are ranked by recent ship velocity. Browse the "Rocket.Chat alternatives" section above for the current picks, or visit /alternatives/rocketchat for the full list with editorial commentary on each.