Tinode vs Element X Android
Side-by-side trajectory, velocity, and editorial themes.
Self-hosted chat platform shipping steady catch-up features and ops cleanup.
Tinode is an open-source, self-hosted messaging server with maintained Web, Android (Tindroid), and iOS (Tinodios) clients. The release cadence is regular (multiple tags per month), and the recent body of work is split between small bug fixes, infrastructure tuning (CORS, MySQL/Postgres DSN handling, Docker image fixes, healthchecks), and feature catch-up that brings the UX nearer to commercial chat apps — pinned chats, dark mode, subscriber counts, send-on-Enter, in-call messaging. An alpha for message reactions is in flight.
The project is in steady-state maintenance with one visible directional push: catching up on the UX features that mainstream chat apps have had for years. Reactions are the next concrete step. Bug fixes and ops touchups dominate the in-between releases, which is healthy for an open-source server that runs in self-hosted production deployments.
v0.26.0 will ship reactions as the headline feature. Threads, richer notifications, or moderation tooling are the natural next catch-ups — anything that further closes the gap with Slack/Matrix/Element on the UX surface without expanding the protocol surface too aggressively.
Element X grinds toward parity: live location, image editing, fewer crashes.
Element X Android, the Rust-SDK rewrite of Element's Matrix client, ships on a tight ~weekly CalVer cadence (v26.04 through v26.06). Recent releases pair real-time features — live location sharing, Element Call work — with sustained stability effort: ANR fixes, deadlock mitigation, and repeated accessibility passes. The app is steadily closing feature-parity gaps with both the legacy Element client and mainstream messengers.
Development is parity- and polish-driven. Capabilities that sat behind feature flags for several cycles keep graduating to GA — live location sharing, room directory search, sign-in with Element Classic — while image editing, voice-message replies, and custom notification sounds fill out everyday messaging UX. Call quality and push-notification reliability (foreground-service fetching, edge-to-edge calls) are a recurring focus rather than one-off work.
Threads, still marked in-development across recent notes, and further Element Call refinements are the most likely next graduations, following the same flag-removal pattern already seen with live location and room directory search.
See more alternatives to Tinode →
See more alternatives to Element X Android →