Element Android vs Element X Android
Side-by-side trajectory, velocity, and editorial themes.
Renamed to "Element Classic" — managed sunset in favor of Element X.
The legacy Kotlin client was renamed to "Element Classic" in October 2025 and has been on a maintenance-and-migration cadence ever since. Recent releases are dominated by interop plumbing for Element X — exposing internal services for the new client to consume, fingerprinting Element X nightly builds, hiding the "Verify this device" banner during migration — alongside dependency bumps, a Google 16KB page-size compatibility pass, and a high-severity sender-spoofing CVE fix.
The trajectory is a managed sunset. The README now recommends Element X; the rename declares legacy status; the in-flight work is about making the handoff to Element X smooth rather than evolving the classic app. Release cadence is slowing and the changelogs are getting shorter and more infrastructural.
Expect the cadence to slow further toward security-and-dependency floor patches only. Feature work has already moved exclusively to Element X Android. A final-release notice is plausible within 6–12 months once Element X reaches full parity for enterprise customers still on the classic build.
Element X Android is in feature-flag-graduation mode as it closes parity with the classic client.
Element X Android is on a tight bi-weekly cadence (v26.05.2 just shipped). The recent rhythm is dominated by feature-flag removals — Sign-in-with-classic, LiveLocationSharing, RoomDirectorySearch — turning experimental capabilities into defaults. Element Call is being polished (edge-to-edge layout, declined-call timeline items), DM flows are being redesigned (new room on invite), and pin-code plus biometric handling has had several iterative fixes.
The team is graduating features rather than introducing new ones, which is the shape you expect when a rewrite is closing in on parity with its predecessor. 'Sign in with Element Classic' specifically reads as a migration bridge for the existing user base. Push notification reliability and foreground-service tuning continuing to appear suggests background delivery on Android is still the hardest correctness problem they are working through.
Expect more feature flags to disappear over the next few releases, and likely a public parity announcement once Spaces UX and full media editing stabilize. The Sign-in-with-classic bridge being now flagless is the kind of thing that usually precedes a coordinated migration push.
See more alternatives to Element Android →
See more alternatives to Element X Android →