← Back to all sparks
E

Element iOS

COMMS
Velocity0.0

Matrix-based secure messaging client for iOS

Element Classic now asks its own users to move to Element X, if their server opts in.

matrixlegacy-clientelement-x-migrationmaintenanceencryption
◆Current state
Element iOS, renamed Element Classic in late 2025, has been in maintenance with single-change releases weeks or months apart. After the device-verification banner saga closed in June, 1.11.41 on September 24 adds a room-list banner inviting users to migrate to Element X. Homeservers switch it on through their Well Known file and can set the text, button and target app.
◆Where it's heading
The legacy client is being wound down deliberately, with homeserver operators controlling when their users are nudged to the new app. Releases will likely stay rare and focused on migration and security.
◆Prediction
Expect the migration banner to become more prominent or default-on in a later release; an end-of-support date is not visible in the entries.

◆Recent moves

  1. 1mo ago

    Element Classic adds a server-controlled Element X migration banner

    A room-list banner invites users to switch to Element X, enabled and customised by the homeserver through its Well Known file, and hidden for a week once closed. It is the first explicit step in retiring the Classic client.

    View source ↗
  2. 1mo ago

    Element Classic 1.11.40: release merge, no notes

    A release-branch merge with no notes, tagged hours before 1.11.41 carried the migration banner.

    View source ↗
  3. 4mo ago

    Mandatory verification banner reinstated

    The mandatory verification banner is reinstated, closing the arc that began in 1.11.35 and was rolled back in 1.11.37. It only became safe to re-enable once 1.11.38 gave unverified users a working reset path, so this release is the completion of a three-version sequence rather than a change on its own.

    View source ↗
  4. 5mo ago

    Reset flow wired into verification for users with no other devices

    Hooks the Reset flow up to Verification for users with no recovery method and no other devices — the dead end that forced the verification banner to be disabled two releases earlier. Filed as a bugfix, but it is the change that unblocked reinstating mandatory verification.

    View source ↗
  5. 7mo ago

    Mandatory verification banner temporarily disabled

    Temporarily disables the mandatory verification banner because there was no way to reset from the verification screen. A holding action that reverses 1.11.35 rather than a change in direction — the banner returns two releases later.

    View source ↗
  6. 7mo ago

    Jitsi SDK bump raises minimum iOS to 15.1

    A Jitsi SDK dependency update that drags the minimum supported OS from 15.0 to 15.1, plus zizmor checks added to CI. Dependency-driven housekeeping, characteristic of this branch since the rename to Element Classic.

    View source ↗