Threema vs Slack
Side-by-side trajectory, velocity, and editorial themes.
Threema pushes enterprise security depth while sharpening its privacy-positioning editorial voice.
Threema is alternating between concrete product releases and editorial positioning. Recent product moves: DualLock in Threema OnPrem protects chats even if a device is lost or stolen; Threema 7.1 for iOS adopts Liquid Glass design with reworked workflows; Threema Work and OnPrem on iOS gained screenshot prevention in March. The editorial cadence (DeleteWhatsAppDay, post-quantum collaboration with IBM Research, Zero Trust explainer, response to politician-targeted cyberattacks on Signal and WhatsApp) keeps the privacy-and-security brand active between releases.
Threema is widening the gap between itself and consumer-grade competitors by leaning hard on the two surfaces its target segment cares about: serious enterprise security primitives (DualLock, screenshot prevention, no user accounts, post-quantum prep with IBM) and an editorial voice that frames every WhatsApp or Signal incident as a reason to switch. The OnPrem product line is where the substantial security work is landing, signalling that the enterprise and government channel is the strategic priority.
Expect more OnPrem-side hardening releases — likely around remote wipe, MDM integration, or quantum-safe key exchange from the IBM Research collaboration — and continued issue-driven editorial output every time a rival messenger has a security incident.
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 Threema →
See more alternatives to Slack →