Element Android vs Slack
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.
Slack rebuilds its developer platform around shipping in-channel AI agents.
Slack is well into a platform pivot, restructuring its CLI, Block Kit, and APIs around AI agent use cases. The 4.0.0 release in April formalized this with an agent-scaffolding command, sample agent apps, and a live-reloading dev workflow. Recent additions — streaming chat APIs, Card/Carousel/Alert blocks, and continued MCP server expansion — show the surface area for in-Slack agents widening fast.
The platform is shifting from 'agents can post messages' to 'agents are first-class UI citizens'. The new chat.startStream / chat.appendStream / chat.stopStream methods change what an agent reply looks like, and the Card and Carousel blocks hint at richer multi-turn agent flows. Security work on PKCE and optional scopes is keeping pace, which tells you third-party agent developers are the audience, not just first-party features.
Expect Slack to publish reference agents and likely a discovery or marketplace surface for agent apps within the next minor cycle, with streaming Block Kit becoming the canonical pattern shown in the docs.
See more alternatives to Element Android →
See more alternatives to Slack →