How Messaging Went From Open Protocols to Walled Gardens

When Messaging Was Open

Before apps existed, messaging ran on public rules anyone could follow.

Email came first. In 1982, engineers published SMTP 1 — a specification for passing messages between mail servers. No single company owned it. Any server that spoke the protocol could talk to any other. Send a message from one organization to another, no permission needed.

Real-time chat followed. In 1993, IRC launched as a live alternative to asynchronous mail 2. You joined a channel, you talked to whoever was in it, and the server relayed your words to everyone listening. Like email, the protocol was public. Developers could build their own clients and connect to any server.

Both shared one key property: interoperability. Different software, different organizations, different servers — all speaking the same language.

That openness kept messaging cheap to run and easy to extend. It also meant no one could capture the business value. That would change.

XMPP (sometimes called Jabber) tried to hold the open model together. In 2000, the IETF formally defined "presence" 3, the ability to see whether a contact was online before messaging them. XMPP combined rosters, near-real-time messages, and presence into a single open standard 4. A user on one server could message a user on a different server, exactly like email.

Consumer products moved faster than standards. ICQ, AIM, MSN Messenger, and Yahoo Messenger each built their own walls. Each worked well inside them. Switch apps, lose your contacts. Move platforms, start from zero.

How Mobile Broke the Model

Smartphones remade messaging from scratch.

Carriers owned SMS. They charged per message, capped texts at 160 characters, and gave you no delivery receipts or group threads.

Apple moved differently. It built messaging into the operating system. iOS 5 introduced iMessage 5, a service that used a data connection between Apple devices. Most users never noticed the protocol switch. They just stopped seeing the green bubble.

Both moves ended interoperability. WhatsApp users could reach WhatsApp users. iMessage users could reach iMessage users, or fall back to SMS for everyone else. Platform owners now controlled routing, storage, and identity, and held data they had never asked to keep.

Work Added Another Inbox

Consumer messaging saturated fast. The next frontier was the office.

Teams ran on email for async work and a tangle of video, phone, and chat for real-time coordination. The overhead was high. Slack proposed something different: one channel-based workspace where conversations, files, and app notifications lived together.

The model stuck. Microsoft responded by building Teams into Office 365 6, launching in preview across 181 countries and 18 languages, with persistent and threaded chats at the core.

By then, people were managing more contexts than they could track. Slack for work. Teams for a client. iMessage for some contacts. WhatsApp for others. Signal for anything sensitive. The inboxes kept multiplying.

Privacy Raised the Bar

Volume and consolidation created a new problem: trust.

When billions of messages move through a few private servers, the companies running those servers learn a great deal. Who you talk to, when, how often. In some cases, what you say.

The Signal Protocol changed the math. Developed by Open Whisper Systems, it let messages be encrypted end-to-end — readable only by sender and recipient, not the platform between them. WhatsApp completed the Signal Protocol rollout in 2016 7, covering chats, group chats, attachments, voice notes, and voice calls across every major mobile platform. A product with over a billion users had made end-to-end encryption the default.

Encryption stopped being a niche concern and became a product requirement. Other platforms had to respond. Data handling moved from fine print into product decisions.

What the History Means for You

The pattern is consistent: experience wins, then lock-in follows. Open networks gave way to consumer platforms with better UX. Those platforms gave way to encrypted messengers with better trust. Each transition improved something real and made it harder to leave.

A third cycle is underway. RCS updated the SMS baseline: group chat, high-resolution media, read receipts 8. GSMA Universal Profile 3.0 added end-to-end encryption requirements 9, bringing RCS closer to the standard encrypted messengers had already set. The EU Digital Markets Act pushed large platforms toward interoperability from the regulatory side, reviving the open-protocol logic of IRC and XMPP as policy argument.

Standards move slowly. Regulation produces compliance theater as often as genuine openness. But the direction is clear: users and governments are pushing back against the locked-down model that defined the mobile era.

The fragmentation you manage is structural, not accidental. A different app will not fix it. The actual task is consolidating where you can, filtering signal from noise, and building a communication setup around how you actually work rather than how each platform prefers you work.