The migration from email to mobile messaging has made everyday communication faster and more immediate. But it has also created a fragmented communications environment that many users don't fully understand and encounter difficulty navigating. As smartphones become the primary computing and communications devices for an increasing share of the population, people are becoming more dependent on text-based messaging while becoming less familiar with email. Yet the messaging environment replacing email is considerably more fragmented and, in many respects, less intuitive.
Consider a simple example: an iPhone user wants to send a message to someone using an iPad. They ask for the iPad's telephone number, assuming that every device receiving messages must have one. But an iPad can receive Apple's iMessages through an Apple Account email address without having a cellular telephone number at all.
Or consider someone entering a recipient's telephone number into Apple's Messages application and encountering an unexpected indication that the number isn't available as an iMessage destination. The user may conclude that the number is incorrect or that something is wrong with the recipient's phone. They may not understand that iMessage is Apple's proprietary messaging service and that communicating with someone outside the Apple ecosystem involves a different messaging protocol.
These aren't isolated technical curiosities. They illustrate a growing problem with the way digital communication is evolving, and they share a common cause: messaging identity and addressing have become bound to particular ecosystems rather than to the people trying to communicate.
Email: A relatively universal communications standard
Email established an important principle of Internet communications: users could communicate across different hardware, software, service providers, and operating systems using a common addressing system.
A Gmail user could send a message to someone using Outlook, Yahoo, or an organizational email server. The applications might look different, but the underlying communications standards were interoperable. Users didn't need to know which email client the recipient used, what operating system they owned, or which manufacturer produced their computer. The email address was the essential identifier. The communications infrastructure largely operated behind the scenes. That relative universality was one of email's greatest strengths.
Mobile messaging: A fragmented ecosystem
Text messaging has evolved along a very different path. Today, users encounter multiple applications, messaging identities, and communications protocols:
· Apple Messages/iMessage: Apple's messaging application and proprietary messaging service, integrated into iOS, iPadOS, and macOS.
· Google Messages: Google's Android messaging application, supporting SMS/MMS and RCS.
· SMS/MMS: Traditional carrier-based messaging standards that provide basic interoperability across mobile networks.
· RCS: A more modern messaging protocol intended to provide richer messaging capabilities across networks and devices.
· Third-party messaging services: WhatsApp, Facebook Messenger, Signal, Telegram, and others, each with its own application, identity system, and ecosystem.
The distinction between an application, a messaging protocol, and a communications service is largely invisible to ordinary users. iMessage, for example, is at once an application (Apple Messages), a proprietary service (Apple's messaging servers), and a protocol of Apple's own design. RCS is different again: a protocol carried by whichever application a device happens to include. WhatsApp bundles its own application, service, and identity system into a single product.
The iPhone owner who calls all of this “texting” and the Android owner who means Google Messages can exchange messages without using the same application, service, or underlying protocol. The problem becomes more pronounced when users encounter capabilities that work within one ecosystem but not another.
The disappearance of a common mental model
A major consequence of this fragmentation is that users increasingly misunderstand how to address and reach other people. Traditional telephone numbers are still widely used, but they are no longer the only way to identify a messaging destination; the iPad from the opening example needs none at all to participate in Apple's messaging ecosystem. Yet many users continue to assume that messaging is fundamentally an extension of traditional telephone service.
Others assume that a messaging application on one operating system has an equivalent application on another, without recognizing that Apple Messages and Google Messages are separate applications with different platform integrations and capabilities. The confusion becomes visible in small failures: the group chat that behaves differently once one participant switches to an Android phone and the conversation silently falls back to SMS.
The resulting confusion is familiar:
“It won't let me.”
“I can't open it.”
“It won’t go through.”
Smartphone dependence doesn't necessarily mean digital literacy
Many people who are highly dependent on smartphones are remarkably proficient at using familiar applications but have relatively little understanding of the systems supporting them. They know how to navigate their messaging application, share photographs, and participate in group conversations. But when something falls outside the expected workflow, they may have difficulty diagnosing the problem.
Modern smartphone interfaces deliberately conceal technical complexity. That is generally good design. Users shouldn't need to understand network protocols to send a message. However, the combination of proprietary ecosystems, multiple messaging applications, different addressing systems, and increasingly invisible technical boundaries creates a situation in which users may not even understand why communication sometimes fails or behaves differently.
RCS helps, but doesn't solve the larger problem
The introduction of RCS support across Apple and Android devices is a welcome development. Where carriers and devices support it, cross-platform conversations gain typing indicators, read receipts, and higher-quality media sharing. But encrypted cross-platform RCS has lagged behind what proprietary services already offer, and rollout still varies by carrier.
RCS addresses only part of the problem. It doesn't make Apple Messages and Google Messages the same application. It doesn't eliminate third-party messaging services or their separate account requirements. Nor does it establish a universal identity and addressing system for all forms of mobile messaging. The distinction between application, protocol, and platform remains.
A case for universal messaging identity and addressing
Perhaps the larger question is whether the telecommunications industry should revisit the concept of a universal messaging identity and addressing framework. Email provides a useful precedent. A person doesn't need to know whether the recipient uses Gmail, Outlook, or another email application. A common addressing convention allows the message to reach its destination regardless of the recipient's device or service provider. Why shouldn't mobile messaging aspire to a similar degree of interoperability?
Imagine a system in which an individual or organization has a persistent, universally recognized messaging address. That address could be associated with a telephone number, email address, or another verified identity, but would not be dependent on a particular device manufacturer, operating system, or messaging application. A sender could initiate a conversation without first determining whether the recipient uses an iPhone, Android phone, tablet, or desktop computer. The underlying infrastructure would negotiate the appropriate delivery method and supported features.
Such a framework would need several foundational elements:
· Universal addressing: A consistent way to identify messaging recipients independent of their device or application.
· Interoperability: The ability to exchange messages across platforms and service providers without requiring users to understand the underlying protocols.
· Identity portability: Messaging identities that remain with the individual when changing devices, operating systems, or service providers.
· Protocol negotiation: Automatic selection of supported messaging capabilities, including encryption, media, and delivery features.
· Security and privacy: Strong authentication, protection against impersonation, spam prevention, and user control over who can initiate contact.
This wouldn't necessarily require replacing Apple Messages, Google Messages, WhatsApp, or other existing applications. The proposal is not another messaging application; it is a common identity and interoperability layer that existing applications can use. They could continue competing on interface design, features, security, and user experience while supporting that common framework. The objective would be to separate the identity of the person being contacted from the particular technology used to contact them.
There are significant implementation and governance challenges. Apple, Google, telecommunications providers, and third-party messaging services would need to agree on common standards, identity management, security requirements, and interoperability rules. Commercial incentives and proprietary ecosystems would also have to be addressed. Nevertheless, these are challenges worth examining.
The telecom industry's interoperability challenge
For telecommunications providers, this raises a broader question about the direction of consumer communications. The industry has spent decades building interoperable networks, and mobile voice, SMS, and Internet connectivity demonstrate the value of common standards across competing providers. Messaging should not be excluded from that conversation.
The consumer experience, however, is increasingly determined not by network connectivity but by the messaging ecosystem a user happens to occupy. The commercial obstacle is equally clear: identity lock-in is an asset for the platforms that own it, which is precisely why a neutral addressing layer will not emerge on its own.
There is a lesson here from email. A successful communications environment doesn't necessarily require everyone to use the same application. It requires common standards, interoperable addressing, and the ability to communicate without having to understand the technical preferences of the recipient. Mobile messaging has made substantial progress, particularly through RCS. But the broader experience remains divided among proprietary services and platform-specific applications.
As more people abandon or minimize their use of email, this fragmentation becomes increasingly consequential. Text messaging is no longer just a convenient supplement to traditional communications. For many people, it is becoming their primary communications channel. The question is whether the telecommunications industry will continue to accept fragmentation as the inevitable consequence of competing ecosystems, or treat universal messaging identity as the next standard worth building. We have made communication faster, more immediate, and more convenient. But have we actually made it simpler?
