Subsplash vs Element X Android
Side-by-side trajectory, velocity, and editorial themes.
Subsplash wires natural-language AI through People and Analytics — its two highest-leverage surfaces.
Subsplash has spent the last two months putting AI on the busiest parts of its admin. Trends AI consolidated giving, attendance, and events data into AI-buildable dashboards in late March, and People Assistant followed in May with natural-language filtering of congregation lists. Between those, the team shipped a dedicated Events Manager role, a group-attendance analytics dashboard, and smaller workflow-board UX gains.
The bet is clear: ministry staff with no SQL or BI background want to ask questions of their congregation's data in plain language — both for analysis and for action. Trends AI handles the analytical half; People Assistant is the actionable list-building counterpart. The supporting work — RBAC, attendance analytics, faster workflow navigation — is what lets the AI features actually land inside real church-staff workflows.
Expect AI to extend next into Workflows (plain-language routing rules for congregants) and Giving (donor segmentation for stewardship outreach), with a unified AI surface across modules as the natural endpoint. Pricing the AI tier separately, as Trends AI already is, telegraphs how Subsplash will monetize this push.
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 Subsplash →
See more alternatives to Element X Android →