← Back to home
Comparison · Comms

Proton Bridge vs Element X Android

Side-by-side trajectory, velocity, and editorial themes.

P2.5

Proton's IMAP gateway is in deep maintenance, hardening fixes only.

◆ Current state

Proton Bridge — the local IMAP/SMTP gateway that lets standard mail clients talk to Proton's encrypted backend — has settled into a hardening-and-fix rhythm. Recent releases are dominated by certificate validation fixes, mailbox conflict resolution, label/unlabel endpoint regressions, and OS compatibility work (macOS 26). No directionally new capabilities have shipped in over a year.

◆ Where it's heading

Cadence is steady at roughly one minor or patch release per month, structured around mistakes that bit users: a Drafts-to-Trash deletion regression in 3.23.x, the unlabel endpoint reversion in 3.24.1. The team is reacting by adding feature flags so risky logic can be toggled post-release, and by expanding Sentry instrumentation around mailbox sync and auto-update failures.

◆ Prediction

Expect more incremental protocol hardening — mailbox conflict cases, IMAP IDLE behaviour, certificate handling — gated behind feature flags. No directional product change is signaled in the changelog.

E5.0

Element X Android is in feature-flag-graduation mode as it closes parity with the classic client.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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 Proton Bridge
See more alternatives to Element X Android