
Yet the telecommunications industry has not fully adapted its messaging infrastructure to this transformation. Instead, the migration to mobile computing has exposed and, in some respects, amplified the fragmentation of electronic communications. We have made computing increasingly portable without making communications equally portable.
The shift from email to conversational messaging
Email remains an essential communications tool, particularly for business correspondence, formal communications, document exchange, and longer written exchanges. But the growth of mobile computing has changed everyday communication patterns. Smartphones have made messaging immediate and persistent. Notifications, contact lists, conversational interfaces, and always-available connectivity encourage shorter, more frequent exchanges.
For many people, messaging has become the default method of personal communication. It is also increasingly used for business transactions, customer service, appointment reminders, authentication, and interactions with organizations. This is not simply a generational preference or a change in application design. It reflects a broader transition in how people use computing devices. The mobile device has become the primary communications interface for a substantial portion of the population. Consequently, the ability to exchange written messages across devices and networks has become more important, not less. Yet the underlying communications architecture remains divided.
The Apple versus Android divide
The competition between Apple and Android illustrates the problem. Both ecosystems have developed sophisticated messaging capabilities, but their users have historically experienced different levels of functionality depending on which platform they use and which platform the recipient uses. Apple's iMessage is integrated into its hardware and software ecosystem. Android has its own messaging applications and the broader RCS standard. Although the introduction of RCS support on iPhones has improved interoperability, the experience is still not equivalent to having one universal messaging system.
This resembles the VHS versus Betamax competition of the 1980s, when competing video recording formats created compatibility problems for consumers. There is an important difference: Apple and Android are not simply competing technical formats. They are extensive commercial ecosystems with different hardware, software, applications, and business models. Both are likely to remain important competitors. But the consumer consequence is familiar. The choice of technology can determine how easily people communicate with one another.
The irony is that email solved much of this problem decades ago. A person using Gmail can communicate with someone using Outlook, an independent business email server, or virtually any other email provider. Neither party needs to know what computer, operating system, or email application the other is using. There is no comparable universal framework for mobile messaging.
The desktop computing analogy
Consider how extraordinary it would be if desktop email worked the way mobile messaging sometimes does. Imagine purchasing a Windows computer and discovering that you could only send messages to people using computers manufactured by the same company. Or imagine being unable to send an email to someone using a different email provider unless you maintained a second computer or account. Such restrictions would be commercially unacceptable. Yet similar limitations have become normalized in mobile communications.
An iPad provides Internet connectivity, email, web browsing, and access to numerous communications applications. Nevertheless, Apple's native Messages application cannot independently send conventional SMS messages without an iPhone acting as a relay. The device is capable of accessing the Internet, but its conventional text messaging capability remains dependent on another device and a separate cellular service relationship.
From the user's perspective, this is an artificial distinction. Why should sending a text message from a tablet require ownership of a particular smartphone? The problem is not a lack of computing capability. It is the way the industry has organized messaging identities and delivery systems. Separate networks, separate identities
The historical separation between email and SMS helps explain the current situation.
Email developed as an Internet-based communications service. Its addressing system is independent of the device and network used to access it. The email address identifies the recipient, while Internet infrastructure handles message routing and delivery. SMS developed within mobile carrier networks. Its addressing system is based primarily on telephone numbers, with delivery historically controlled by mobile network operators. More recently, proprietary messaging applications have introduced additional identities and communications environments. Apple iMessage, WhatsApp, Facebook Messenger, and other services each have their own methods of identifying users and delivering messages.
The result is a fragmented landscape in which the user must navigate different applications, identities, and networks to accomplish essentially the same task: exchanging written information. This fragmentation was less conspicuous when desktop computers and email dominated electronic communication. It becomes increasingly problematic when smartphones and tablets become the primary devices people use to communicate.
The telecommunications industry has recognized parts of this problem.
The telecommunications industry has effectively moved the user toward mobile computing without establishing a correspondingly universal mobile messaging architecture. Interoperability is the next logical stepRCS, developed through the GSMA, is intended to modernize traditional SMS and provide richer messaging capabilities. Its adoption by Apple has improved communication between Android and iPhone users.
The Internet Engineering Task Force has also established the MIMI (More Instant Messaging Interoperability) working group to develop standards for interoperability between independent messaging providers. The Matrix protocol provides another example of an open, federated messaging architecture in which independent servers and applications can communicate.
These are meaningful developments. But they primarily address interoperability between messaging services. They do not yet establish a universal messaging identity that integrates email, SMS, RCS, and other Internet-based messaging systems. That distinction is important. Making separate messaging applications communicate with one another is useful. Establishing a common identity and addressing framework that makes the underlying differences largely irrelevant would be a more fundamental improvement.
Moving from device-centric to identity-centric communications.
The next evolution in messaging should separate three things that have become unnecessarily intertwined:
- Personal identity: How an individual is identified and addressed for communications.
- Messaging transport: The network or protocol used to deliver the message.
- Device and application: The hardware and software used to compose and receive it.
For example, someone composing a message on an iPad could send it to an Android user without needing an iPhone as an intermediary. If the recipient were reachable only through SMS, the system could use an appropriate carrier gateway. If the recipient used an IP-based messaging service, the message could be delivered through that service. The sender would not need to know or select the underlying transport mechanism. The same identity could be used from a smartphone, tablet, desktop computer, or other connected device. This would not require eliminating email, SMS, or existing messaging applications. They could continue serving different purposes and user preferences while operating within a more interoperable communications environment.
The commercial challenge
The technical requirements for such a system are substantial, but the commercial obstacles may be even greater. Apple benefits from the integration of iMessage with its hardware ecosystem. Google has its own messaging interests. Mobile carriers have historically controlled SMS delivery and telephone-number-based messaging. Independent messaging platforms benefit from keeping users within their respective environments. A universal messaging identity would reduce the ability of individual companies to use messaging access as a source of customer lock-in.
That does not mean eliminating competition. It means changing what companies compete over. Device manufacturers could continue competing on hardware and user experience. Application developers could compete on messaging features, security, and convenience. Carriers could compete on connectivity and network services.But consumers would no longer have to sacrifice basic communications interoperability to participate in those competing ecosystems.
An open framework would also need to address authentication, spam, fraud, privacy, encryption, identity portability, and the governance of the addressing infrastructure. A universal identity should remain under user control rather than becoming another proprietary asset controlled by a single technology company.
The larger telecommunications paradox
The Internet was built around the principle that independent networks could communicate using common protocols. Email demonstrated that electronic communications could operate across different providers, devices, and operating systems without requiring users to belong to the same commercial ecosystem. Yet mobile messaging has developed in a different direction. The industry is investing in 5G, 6G, satellite connectivity, cloud infrastructure, and increasingly sophisticated mobile devices. Computing power and connectivity are becoming more portable and ubiquitous. But one of the most fundamental forms of digital communication remains divided by proprietary applications, separate addressing systems, and carrier-dependent infrastructure.
As mobile devices replace traditional computers as the primary communications interface, this fragmentation becomes increasingly difficult to justify. The future of messaging should not be determined by whether someone owns an Apple or Android device, subscribes to a particular carrier, or prefers email over a particular messaging application. The individual should own the communications identity. Applications should compete to serve the individual. Networks should deliver the message. We have achieved device portability without achieving communications portability. It is time for the telecommunications industry to address that disconnect.
