Element Android vs Chat Data
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.
Chat Data is turning its chatbot platform into a workflow runtime with payments built in.
Chat Data is no longer just a custom-chatbot builder — recent shipments push it toward an end-to-end agent platform. The last two weeks added cron-driven workflow triggers, native Stripe OAuth, deeper page-context tiers, and access to GPT-5.5. Each move targets a different gap that previously forced customers to bolt on outside tooling.
The arc is unmistakable: chatbot to agent to autonomous workflow with monetization wired in. Scheduling decouples Chat Data's automations from live user prompts; direct Stripe handles the revenue side; richer page context closes the gap with retrieval-heavy competitors. Pricing is shifting in lockstep, with a per-node credit charge for non-AI workflow steps replacing the prior all-or-nothing model.
Expect the next releases to focus on workflow observability — run history, retries, conditional branches — and likely an agent marketplace or template gallery to drive adoption of the scheduled-trigger surface.
See more alternatives to Element Android →
See more alternatives to Chat Data →