← Back to home
Comparison · Comms

Element iOS vs Element

A side-by-side editorial comparison of Element iOS and Element — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:matrix

Element iOS vs Element: at a glance

FeatureElement iOSElement
SectorCommsComms
Velocity score0.05.0
Sparks · 30d00
Top themesmatrix, legacy-client, device-verification, maintenancematrix, open-source, messaging, mvvm
Last editorial update1mo ago3h ago
WebsiteVisit →Visit →

What is Element iOS?

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.

Read the full Element iOS trajectory →

What is Element?

Element rebuilds its timeline with MVVM architecture while cutting legacy OS support in v1.12.28.

Element, the open-source Matrix messaging client, ships on a stable two-week release cadence and is currently at v1.12.28. The project is mid-way through a multi-part Timeline MVVM refactor (parts 1 and 2 in v1.12.26 and v1.12.27), restructuring the core room timeline component. The v1.12.28 release raises the minimum glibc requirement to 2.34, ending support for Debian bullseye and Ubuntu releases older than 22.04.

Read the full Element trajectory →

Element iOS vs Element: editorial side-by-side

E0.0

Renamed Element Classic, this client now ships one small fix every few months

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

E
Element
COMMS
5.0

Element rebuilds its timeline with MVVM architecture while cutting legacy OS support in v1.12.28.

◆ Current state

Element, the open-source Matrix messaging client, ships on a stable two-week release cadence and is currently at v1.12.28. The project is mid-way through a multi-part Timeline MVVM refactor (parts 1 and 2 in v1.12.26 and v1.12.27), restructuring the core room timeline component. The v1.12.28 release raises the minimum glibc requirement to 2.34, ending support for Debian bullseye and Ubuntu releases older than 22.04.

◆ Where it's heading

The Timeline MVVM series is the defining architectural investment of this window — replacing the legacy timeline rendering with a proper view-model separation. This is foundational work that typically precedes faster feature delivery on the timeline surface (thread UX, call integration, richer message types). Parallel work promoting Custom Themes to devtools and updating bundle configurations signals cleanup of the extension and theming surface alongside the core refactor.

◆ Prediction

A Timeline MVVM part 3 or final integration is the immediate next step; once complete, expect improved thread UX or voice/video call timeline integration as the first beneficiaries of the new architecture.

Alternatives to Element iOS and Element

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 Element.

See all Element iOS alternatives → · See all Element alternatives →

Recent activity from Element iOS and Element

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 9h agoElementElement v1.12.28: glibc 2.34 minimum, drops Debian bullseye
  2. 7d agoElementElement Banner module v2.0.0
  3. 7d agoElementElement v1.12.28-rc.1
  4. 7d agoElementElement v1.12.28-rc.0
  5. 15d agoElementElement v1.12.27: Timeline MVVM part 2
  6. 19d agoElementElement v1.12.27-rc.1
  7. 2mo agoElement iOSMandatory verification banner reinstated
  8. 3mo agoElement iOSReset flow wired into verification for users with no other devices
  9. 5mo agoElement iOSMandatory verification banner temporarily disabled
  10. 5mo agoElement iOSJitsi SDK bump raises minimum iOS to 15.1
  11. 6mo agoElement iOSPermanent disclaimer banner for unverified sessions
  12. 8mo agoElement iOSOAuth support moves to stable MSC3824

Frequently asked questions

What is the difference between Element iOS and Element?

Both compete on the same themes — matrix — within Comms. Element is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.

Is Element iOS better than Element?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Element is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.

What are the best alternatives to Element iOS?

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.

What are the best alternatives to Element?

Top Element alternatives in Comms are ranked by recent ship velocity. Browse the "Element alternatives" section above for the current picks, or visit /alternatives/element-web for the full list with editorial commentary on each.