Element
Element ships MatrixRTC calls and starts moving its web client onto Rust.
A side-by-side editorial comparison of Converse.js and Signal — release velocity, themes, recent moves, and the top alternatives to consider.
Converse.js 14 lands OMEMO:2 — the browser XMPP client catches up on modern encryption.
Converse.js reached 14.0.0 in June 2026 after a tight beta train, and the release is defined by one thing: support for OMEMO:2, the current revision of XMPP's end-to-end encryption. The surrounding work is all encryption ergonomics — per-chat encryption state remembered across chat-close and re-login, an explicit error surfaced for undecryptable messages instead of silently dropping them, the toggle hidden on untrusted devices, and original filenames preserved on encrypted image download. New PubSub API methods for create, subscribe and unsubscribe round out the release.
Signal brings Secure Backups to every platform and starts automating key verification.
Signal Secure Backups improvements are now available on all platforms with iOS 8.30, a year after the feature's introduction. Android 8.20 and iOS 8.22 extended linked devices to Android phones, Android tablets and iPhones. Automatic key verification now complements safety numbers as a simpler way to confirm no unexpected party sits in a session.
Converse.js reached 14.0.0 in June 2026 after a tight beta train, and the release is defined by one thing: support for OMEMO:2, the current revision of XMPP's end-to-end encryption. The surrounding work is all encryption ergonomics — per-chat encryption state remembered across chat-close and re-login, an explicit error surfaced for undecryptable messages instead of silently dropping them, the toggle hidden on untrusted devices, and original filenames preserved on encrypted image download. New PubSub API methods for create, subscribe and unsubscribe round out the release.
The project is closing the gap between having encryption and having usable encryption. Almost every OMEMO change in this cycle is about failure modes users previously had to guess at: a silently dropped message, an encryption toggle offered where it cannot work, an abandoned bundle that never self-healed. That is the work a client does when its encryption is no longer a demo but something people depend on daily. Dropping client-compress for native browser APIs points the same way — fewer bundled dependencies in a security-sensitive path.
Expect the 14.x line to settle into interoperability fixes as OMEMO:2 meets other XMPP clients in the wild, with the new PubSub API the most likely base for the next feature layer.
Signal Secure Backups improvements are now available on all platforms with iOS 8.30, a year after the feature's introduction. Android 8.20 and iOS 8.22 extended linked devices to Android phones, Android tablets and iPhones. Automatic key verification now complements safety numbers as a simpler way to confirm no unexpected party sits in a session.
The earlier alternation between protocol work and feature catch-up has narrowed into one theme: making multi-device life safe without asking users to do anything difficult. Backups, linked devices and automatic verification each remove a manual step or a reason to leave.
The entries are teasers and do not point to a specific next feature. Further multi-device polish looks most likely, since that is where the last three posts landed.
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 Converse.js or Signal.
Element ships MatrixRTC calls and starts moving its web client onto Rust.
Postmark answers the agent era with an MCP server and tighter account security.
Fonoster Cloud starts charging for calls as the project moves to fonoster.ai.
Salesmsg Click Tracking puts every sent link, including CRM automation texts, in one report.
Signal Desktop can finally send contacts, ending a fix-only stretch of betas.
Twilio ships GA reconnect and mid-call config for Conversation Relay voice agents.
See all Converse.js alternatives → · See all Signal alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Converse.js and Signal are shipping at a similar cadence (velocity 0.0 vs 0.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. Converse.js and Signal are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top Converse.js alternatives in Comms are ranked by recent ship velocity. Browse the "Converse.js alternatives" section above for the current picks, or visit /alternatives/converse-js for the full list with editorial commentary on each.
Top Signal alternatives in Comms are ranked by recent ship velocity. Browse the "Signal alternatives" section above for the current picks, or visit /alternatives/signal for the full list with editorial commentary on each.