Session vs Element X Android
Side-by-side trajectory, velocity, and editorial themes.
Session shipped a protocol rewrite and a paid tier, then went publicly broke — the founder is asking users to bail it out.
Session is simultaneously in its most ambitious technical phase and an open funding crisis. Protocol V2 — re-implementing forward secrecy and layering post-quantum cryptography on top of Session's onion-routed transport — has been announced, and the Session Pro paid tier exited beta planning into a December development update. Then in March, cofounder Chris McCabe published a personal appeal saying the project cannot continue developing without user support, and the public feed has been quiet since.
The product roadmap that was meant to fund itself via Session Pro is colliding with the underlying problem the appeal makes plain: the Loki/Oxen-era token economics and donations aren't covering ongoing development. Protocol V2 and Pro are the bets that have to land for Session to remain viable; if Pro doesn't convert a meaningful share of the user base, the next twelve months are about scope reduction, not feature growth. The Feb 1 APT key rotation in January suggests the core infrastructure is still being maintained — for now.
Watch for either a hard Session Pro launch and conversion announcement, or a more explicit wind-down / handoff post. A long stretch of silence after a funding appeal usually resolves one way or the other within a quarter; the absence of any new posts since mid-March is itself a signal.
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 Session →
See more alternatives to Element X Android →