WhatsApp is Meta’s end-to-end encrypted messaging app: one-to-one and group chat, calls, media and status, built on a proprietary centralised service.
CHOOSE A PRODUCT · BUILD WITH YOUR AGENT
WhatsApp is Meta’s end-to-end encrypted messaging app: one-to-one and group chat, calls, media and status, built on a proprietary centralised service.
Catalog categories: messaging.
Catalogued capability areas: - End-to-end encrypted messaging and calls - Group chats, media sharing, status - Multi-device sync
This summary reflects the catalog record, not a complete product specification. Verify intended users, end-to-end workflows, supported platforms, edge cases, data handling, and constraints against cited sources. Treat capability labels as research leads until that verification is complete.
5 candidate projects in the landscape. A candidate may cover all, part, or none of what WhatsApp does — read the coverage and gaps below.
Federated, end-to-end encrypted messaging; self-hostable.
The main open alternative.
Private messenger with no user identifiers.
Strong metadata privacy.
Client is open source.
Server is not open source.
Open federated messaging protocol.
The older federated standard.
Peer-to-peer and community chat.
Specialised alternatives.
Alternative coverage
Available. Federated and P2P open messengers cover the function.
The gap
Network effects and the multi-billion-user contact graph are not reproducible; the protocol and clients are open.
This Markdown file is the coding-agent skill for WhatsApp. Give it to your agent in your project; it guides research, reuse decisions, implementation and verification.
Give the WhatsApp skill to your coding agent in your project. Ask it to evaluate Matrix / Element ↗ against your needs, reuse what fits, then follow the skill's build and verification instructions.
Give the product skill to your coding agent in the project where you want to build. Optional starter workspace: rae build product meta-whatsapp --out ./meta-whatsapp. CLI reference.
