The world of digital communication is a constantly evolving battlefield, where proprietary and open standards compete for primacy, and user experience is often sacrificed on the altar of economic and strategic interests. In the center of this mischia, for years, is located Google, a technological giant with a surprising and often frustrating history of attempts, failures and sharing in the field of messaging. Its last, and perhaps more persistent, crusade concerns the adoption of Rich Communication Services (RCS), a standard designed to modernize the obsolete SMS, bringing features similar to those of modern chat apps directly into the heart of operator-based messaging. However, as evidenced by the chronicle of the events that led Google to decide to implement RCS autonomously in the United States in 2019, the road to a unified and advanced messaging experience on Android was, and continues to be, blocked by obstacles. This situation is not only the result of complex technological dynamics, but also of a fierce struggle of power between tech giants, telecommunications operators and the unstoppable force of the network effect that has consecrated actors like Apple with iMessage or Meta with WhatsApp. Analyzing this whole story means understanding not only why Google has struggled so much to create a solid identity in the field of messaging, but also the broadest implications for privacy, security and freedom of choice of users in an increasingly fragmented digital ecosystem.
The Fragmented Heritage: The Evolution of Message Systems and the Birth of RCS
To fully understand the battle of Google with RCS, it is essential to trace the evolution of messaging systems, starting from their humble origins. The Short Message Service (SMS), introduced in the 1990s, revolutionized the way people communicated, offering an almost universal means of textual exchange. However, with its intrinsic limits – such as the maximum character length, lack of support for rich media and the absence of modern features such as typing indicators or reading receipts – the SMS quickly became obsolete in the face of technological advancement. The attempt to overcome these shortcomings with Multimedia Messaging Service (MMS) it proved partial, due to high costs, file size limits and often poor media quality. It is in this context of dissatisfaction and obvious need for a successor who emerged the concept of Rich Communication Services (RCS). Description GSM Association (GSMA), a consortium of mobile operators and companies in the sector, RCS was designed to be the natural evolution of the SMS, an update that would bring the messaging based on operator in the 21st century, providing functionality comparable to those of the nascent messaging apps Over-The-Top (OTT). The idea was ambitious: integrating features such as advanced group chats, high resolution file sharing, typing and delivery status indicators, voice calls and superior video, and even chatbots and interactions with companies, all managed by the operator network and associated with the user’s phone number. This vision promised to elevate the default messaging experience on phones to a level of sophistication that could compete with OTT services. However, its implementation has been hampered by a number of complex factors, including the reluctance of operators to collaborate on a unified standard, the lack of clear economic incentives for a significant investment and the rapid rise of proprietary messaging services that monopolized users' attention well before RCS could take off. This slowness and initial fragmentation opened the way to Google to intervene, trying to impose its vision and speed up the adoption of RCS in a market that desperately needed it, but which was now accustomed to alternative and often more complete solutions.
RCS: A Technical Overview Between Promises and Structural Limits
Rich Communication Services (RCS) is, in theory, a significant leap from the SMS, designed to bridge the functional gap between traditional operator-based messaging and modern chat applications. At its core, RCS is a set of communication protocols that enable a wide range of features, whose most widespread standard is the Universal Profile (UP), developed by GSMA. This profile aims to ensure interoperability between different implementations of RCS, allowing users of different operators to communicate with advanced features. The characteristics promised by RCS are the ones that every user of modern messaging app now gives for granted: typing indicators that show when someone is writing, reading receipts to confirm that a message has been displayed, improved group chat with the possibility to name groups and add/remove participants with greater ease, the high resolution media sharing (photos and videos of higher quality than MMS), longer messages that exceed the limit of 160 SMS characters, and the possibility to see the presence status contacts (if they are online or have active chat features). These features are crucial for a modern messaging experience and were the focus of Google’s push for the adoption of RCS. However, despite these promises, RCS is affected by significant structural limitations that have curbed its adoption and attractiveness. The most critical among these is the lack of end-to-end encryption (E2EE) native and universal. While services such as WhatsApp, Signal and iMessage have made E2EE encryption a pillar of their offer, ensuring that only sender and recipient can read messages, standard implementations of RCS leave messages open to potential interception by operators, Google itself (in the case of its implementation) or other entities. Google introduced E2EE encryption in its RCS-based Individual Chats app, but this is a Google-owned feature, not an intrinsic and universal feature of the RCS standard itself, and does not extend to group chats or interaction with RCS implementations of other operators. Another limit is its approach career-centric to identity. RCS identifies users mainly through their phone number, giving operators significant control over the identity and flow of communication. Although this was sensible in the perspective of operators who developed the standard, in an age when users expect flexibility and control over their digital identity, this approach may appear restrictive and anachronistic. These limits, combined with the complexity of implementation and fragmentation between different operators and countries, have made RCS an imperfect solution, a basis on which Google had to build its own extensions and bypasses to make it more appealing to users, but which has however generated skepticism and delays in adoption.
The Battlefield of Telecommunications: Carriers Against Giants of Technology
The RCS saga is inherently linked to a broader and deeper struggle of power between traditional telecom operators and modern technological giants. Historically, operators held the monopoly of communication, controlling network infrastructure and, consequently, voice and SMS/MMS telephony services. This control resulted in huge revenue flows. The advent of the internet and, subsequently, mobile applications OTT (Over-The-Top) has upset this model. Services such as WhatsApp, Telegram, Facebook Messenger and, crucially, iMessage of Apple, have bypassed the traditional networks of messaging operators, simply taking advantage of data connectivity. This has eroded a significant part of the revenues of the operators, transforming them, in the eyes of many, into simple providers of “tubes” for data traffic. In this context, RCS has been seen by operators as an opportunity to regain part of the lost control and to modernize its services, making them competitive with respect to OTT apps. However, their proverbial slowness in the collaboration and implementation of the standard has created a window of opportunity Google has attempted to exploit. Google’s strategy, begun with the acquisition of Jibe Mobile in 2015, was to provide an implementation of RCS “turnkeys” to operators, hoping that they would adopt it and integrate it into their networks. This would allow Google to act as a catalyst for the adoption of RCS on Android, while guaranteeing a certain level of control over the standard and its evolution. Initially, operators showed themselves reticent to deliver Google the keys to their messaging, fearing they would lose further control over the relationship with the customer and potential monetization opportunities. They preferred to maintain their own implementation, often incompatible with those of other operators, thus creating a fragmentation that hindered mass adoption. This resistance reached its peak in 2019, when leading US operators – Verizon, AT&T, Sprint and T-Mobile – announced their Cross Carrier Messaging Initiative (CCMI). This move was a clear attempt to create their own version of RCS, controlled by operators, which should have launched a new messaging app by the following year. This initiative, perceived by Google as a betrayal and an attempt to undermine its efforts, prompted the giant of Mountain View to a drastic action: completely bypass operators and launch its own implementation of RCS, based on its Google Messa app, directly to Android users in the United States. This decision marked a turning point, transforming RCS messaging from a standard driven by operators to an OTT service operated by Google, operating in parallel and competing with any future implementation of operators. The battle was no longer just for a standard, but for the control of user experience and associated data flow, a conflict that continues to define the panorama of messaging on Android.
The Net Effect and Tirannia del Default: Why Google Ha Faticato with RCS
The success of a communication platform is crucially dependent onnetwork effect: more people use a service, more that service becomes useful for all others, further encouraging its adoption. It is a powerful dynamic that has allowed services such as WhatsApp, Facebook Messenger and, in particular, iMessage of Apple, to establish a dominance almost unassailable in their respective markets. In the context of messaging, the network effect is amplified by the need to communicate with your existing social network. If your friends and your family are all on WhatsApp, it is almost inevitable that you should use it, regardless of its specific features or personal preference. This is where Google has faced one of its biggest challenges with RCS and its Messaging app. When Google decided to launch its RCS implementation in the United States, it had to deal with the default tyranny. RCS was not (and in many cases it is not yet) the default messaging protocol. The Google Messa app is not installed by default on all Android phones (many OEMs prefer their apps), and even when it is installed, users have to activate it, make it the default messaging app and then enable ‘ chat functionality’ (RCS) in the settings. This multi-step adoption process creates a significant friction for the user. Unlike iMessage, which is integrated at the operating system level on all Apple devices and is automatically activated, or WhatsApp, which has become an indispensable app in many regions, Google’s RCS requires an active commitment from the user. This friction hinders the creation of critical mass necessary to trigger the net effect. If only part of your contacts use Google Messages with active RCS, advanced conversations will be limited to that subset, while others will return to the old SMS, resulting in confusion and frustration. Moreover, the implementation of Google of RCS, being in fact an OTT service that uses a standard below, has lost part of its intrinsic appeal. RCS was promising because it was supposed to be universal default of operators, something that magically worked between all phones like SMS, but with modern features. By removing its ‘defaultness’ and transforming it into a service that requires a specific app and a manual activation, Google essentially created the new messaging app that competes with hundreds of others, without the intrinsic advantage of being ubiquitous and immediately available. This battle against user resistance and the lack of an automatic and universal entry point made RCS’s adoption a slow and fragmented process, despite Google’s persistent efforts to promote and integrate it more deeply into the Android ecosystem.
iMessage: Apple Monopoly and Resistance to interoperability
No discussion on the adoption of RCS and the fragmentation of the messaging would be complete without facing the dominant and controversial role of iMessage of Apple. iMessage is more than just a messaging app; it is a complete ecosystem and a key pillar of Apple's customer loyalty strategy. Launched in 2011, he managed to conquer a position of almost monopoly in key markets such as the United States, transforming messaging into a critical differentiation factor between iOS and Android devices. The success of iMessage lies in several factors: its native and deep integration with iOS, which makes it the default and omnipresent messaging app on every iPhone, iPad and Mac; its ability to fall stylishly on the SMS when the interlocutor is not an iMessage user; and above all, its series of advanced features (type indicators, read receipts, rich group chats, stickers, effects, integrated App Store) available among Apple users, all accompanied by Apple promise end-to-end encryption. But the most distinctive feature, and even the most divisive, is the way iMessage identifies messages sent between Apple users with the famous “blue bubble“, distinguishing them from “green bubblesSMS/MMS sent to Android users. This distinction, apparently harmless, has generated a social and cultural phenomenon, especially among young people, creating a social pressure to possess an iPhone not to be “excluded” or perceived as “differents” in the group. Green bubbles are not only a visual indicator; they also mean a degraded messaging experience: lack of typing indicators, compressed media, lack of advanced group chats, and, above all, the absence of E2EE encryption. Google and other RCS supporters have often invited Apple to adopt the standard, claiming that this would improve the messaging experience for all, promoting interoperability and reducing barriers between platforms. However, Apple has constantly resisted this pressure. The reasons are clearly strategic: iMessage is a powerful tool for keeping users in the Apple ecosystem and attracting new ones. The adoption of RCS could level the playing field, reducing the exclusive attraction of iMessage and, consequently, weakening one of Apple’s most effective levers for customer loyalty. Allow iPhone users to have the same advanced messaging experience with Android users, without “green bubbles”, would deprive Apple of a significant competitive advantage. Although antitrust laws and pressures have begun to question the domain of iMessage in some jurisdictions (as in Europe with the Digital Markets Act), Apple’s resistance to interoperability RCS is a fundamental and persistent obstacle for the vision of a universal and modern messaging, making fragmentation an inherent feature of the current landscape.
Google Labyrinth: A Chronicle of Fallen Messages Apps and Path To Messages
The story of Google with messaging is an emblematic chapter of its corporate culture, characterized by incessant innovation but also by a remarkable inclination to fragment, launch and then abandon products. Before the commitment to RCS with the Messa App, Google has crossed a real maze of messaging app, leaving behind a trail of confusion and frustration among users. The list is long and often ridiculous: starting from Google Talk (an XMPP-based chat service, loved for its simplicity and integration with Gmail), then Google Voice (a single phone number with forwarding and transcription features), followed by more bizarre experiments such as Google Buzz (a social network integrated in Gmail that was a disaster), and Google+ Messenger (part of Google+ social network failure). Confusion has increased with the introduction of Hangouts, which initially promised to unify all Google communications (chat, video calls, SMS) in a single cross-device platform, with clients for Android, iOS, Chrome, web and even smartwatch. For some time, Hangouts seemed to be Google's definitive solution to the messaging problem, but its direction was then deviated to the corporate world with Hangouts Chat and Hangouts Meet, and consumer support was gradually withdrawn. Then he arrived To the, an intelligent messaging app attempt with integrated AI (Google Assistant), launched without SMS support and with end-to-end encryption only in “uncognito” mode, a choice that sealed its fate. At it was quickly abandoned, leaving users once again without a clear direction. Next to these, there was also Space, a group chat app focused on content sharing, also short-lived. Each new app brought with it promises of innovation and simplicity, but inevitably collided with adoption problems, overlapping of functionality with existing products and ultimately abandoning Google. This story of launches and retreats has created a deep distrust among users about Google’s commitment to any of its messaging apps, making it even more difficult for the company to build a solid foundation for a new service. The app Google Messages (often simply called “Messages”) emerged from this chaos as the last, and so far more persistent, Google’s hope for consumer messaging. Born as a simple SMS app, it was chosen by Google as a vehicle for the implementation of RCS, turning into a hybrid platform that manages SMS/MMS and, for compatible users, the advanced features of RCS. This winding and strenuous path of failures is a testament to the difficulties of Google in finding a coherent and winning strategy in an area dominated by network effects and consolidated actors.
Beyond 2019: The current state of RCS and the Google Persistent Impulse
The 2019 events, with Google's decision to bypass careers and implement RCS directly through its Messages app, marked a turning point. Since then, the situation has evolved considerably, and Google has continued its incessant push for the adoption of RCS, with contrasting but undeniable results. In the post-2019 period, Google stepped up efforts to integrate RCS in the Android ecosystem. He worked to make it available in more and more countries, collaborating with the operators arranged and, in the absence of such collaboration, providing it directly as an internet-based service. A crucial step was the introduction of end-to-end encryption (E2EE) for individual chats based on RCS within Google Messa, from 2020. This move responded to one of the most fierce criticisms of the original RCS standard, aligning Google Messages with the privacy expectations of modern users and making it more competitive than apps like iMessage and WhatsApp. However, as mentioned, this E2EE is specific to Google’s implementation and does not extend to group chats or interoperability with other RCS implementations not managed by Google. The Google Messa app has also been the subject of constant development, with the addition of new features, user interface improvements and greater integration with other Google services. The company actively promoted the app as the “future of messaging on Android”, trying to convince OEMs (Original Equipment Manufacturers) to preinstall it as a default messaging app on their devices, thus reducing the friction for the user and increasing its visibility. Despite the initial resistance and creation of the CCMI by US carriers, this initiative proved to be a failure. The CCMI was dissolved in 2020, and many operators eventually opted to support or integrate the implementation of Google’s RCS. Today, most of the major operators in North America and in many other regions support Google Messa’s “ chat features”, and the overall adoption of RCS has grown significantly. However, the great absent in this equation remains Apple. Despite Google’s continued pressure on industry experts and, more recently, investigations of antitrust authorities that examined the dominant position of iMessage, Apple retained its position of refusal to adopt RCS. The debate “blue bubble vs. green bubble” continues, and until Apple integrates RCS, the fragmentation between iOS and Android in messaging will remain a reality, preventing RCS from reaching its full potential of universal standards. Google’s impulse, although it has led to a wider adoption of RCS on Android, has not yet solved the problem of global fragmentation of messaging, and the battle for a seamless and universal communication experience continues.
Security and Privacy in the Message Age: The Right to End-to-End Crime
At a time when data privacy and security concerns have become central end-to-end encryption (E2EE) si è affermata come uno standard de facto per le comunicazioni digitali sicure. Questa tecnologia garantisce che un messaggio, una volta inviato, possa essere letto solo dal mittente e dal destinatario previsto, e che nemmeno il provider del servizio di messaggistica possa accedervi. L’assenza di E2EE nello standard RCS originale è stata, e rimane, una delle sue maggiori debolezze e una fonte di considerevole scetticismo da parte degli utenti e degli esperti di sicurezza. Come accennato, le implementazioni iniziali di RCS lasciavano i messaggi aperti alla potenziale intercettazione e lettura da parte degli operatori di rete, dei fornitori di servizi e, teoricamente, anche di agenzie governative. Questo modello, sebbene familiare nel contesto degli SMS tradizionali, è in netto contrasto con le aspettative moderne sulla privacy, alimentate dal successo di app come Signal, Telegram e WhatsApp (che ha introdotto E2EE per default nel 2016). La decisione di Google di aggiungere la crittografia E2EE alle chat individuali RCS nella sua app Messaggi è stata una mossa strategica fondamentale per legittimare RCS come una soluzione di messaggistica moderna e sicura. Tuttavia, è cruciale sottolineare che questa E2EE è un’aggiunta proprietaria di Google, non una caratteristica universale dello standard RCS stesso. Ciò significa che la crittografia è garantita solo quando entrambi gli interlocutori utilizzano Google Messaggi e le loro chat sono identificate come “funzionalità di chat” attive. Se si chatta con un utente che utilizza un’altra implementazione di RCS (ad esempio, un’app di un operatore che non supporta l’E2EE di Google) o un utente iPhone (che riceve SMS/MMS), la crittografia end-to-end non è attiva. Questa “E2EE selettiva” crea ancora una volta frammentazione e potenziale confusione per gli utenti, che potrebbero non essere pienamente consapevoli di quando le loro conversazioni sono protette o meno. Il diritto alla crittografia end-to-end nelle comunicazioni digitali è sempre più riconosciuto come un pilastro fondamentale della privacy personale e della libertà di espressione. Regolamentazioni come il GDPR in Europa hanno posto una maggiore enfasi sulla protezione dei dati, spingendo le aziende a adottare pratiche più sicure. In questo contesto, qualsiasi standard di messaggistica che non offra E2EE per default, in modo universale e trasparente, si trova in una posizione di svantaggio. La battaglia per la crittografia in RCS è un esempio lampante della tensione tra la necessità di interoperabilità e la priorità della privacy e della sicurezza, una tensione che continuerà a modellare il futuro della comunicazione digitale e a influenzare la percezione e l’adozione degli standard emergenti. Finché RCS non integrerà E2EE come parte intrinseca e universale del suo protocollo, la sua capacità di competere come soluzione di messaggistica definitiva sarà sempre limitata.
Fragmentation and User Experience: The Cost of “Mess”
The “mess mess” (the chaos of messaging), as it was rightly defined, is not only a technological or business battle; it has a direct and often frustrating impact on the daily experience of users. The fragmentation of messaging is the cost that users pay for the lack of a universal and interoperable standard, and for the proliferation of proprietary services competing. This results in a series of inconveniences that influence the quality and simplicity of digital communications. First, the user confusion. In an ideal world, you should be able to send a message to anyone, regardless of device or operator, with the certainty that advanced features will work and that communication will be safe. Instead, users are forced to navigate a labyrinth of apps and protocols: WhatsApp is used for friends, Telegram for larger groups, iMessage for Apple contacts, and Google Messages (with or without RCS) for others. Sometimes, it turns out only after sending a message that a contact does not have RCS active, and the message “declasses” to SMS, losing functionality and quality. This is not only uncomfortable, but it can also lead to misunderstandings or a sense of exclusion when you cannot fully participate in a group chat due to technological limitations. The missing features are another direct cost of fragmentation. Group chats with Android and iOS users are often a lower experience, limited to basic SMS/MMS features: absent group names, low-quality media, lack of read receipts and typing indicators. This not only makes communication less rich, but can also hinder social collaboration and interaction. The platform lock-in is a more insidious side effect. The dominance of iMessage in markets like the United States, with its exclusive “blue bubbles”, creates a social pressure that pushes users to stay within the Apple ecosystem so as not to lose the experience of “premium” messaging with their peers. This is not only a question of technological preference, but it becomes a factor that influences device purchase decisions, limiting user choice and freedom. Finally, there is the impact on privacy and security. The need to draw between apps with different levels of encryption and privacy policies makes it harder for the average user to make informed decisions on how and where to communicate safely. Fragmentation is not only a nuisance, but a significant obstacle to a unified, secure and inclusive digital communication experience for all. The “mess mess” is a constant reminder that despite technological advances, politics and business interests continue to prevail over simplicity and benefit for the end user.
The Future of Digital Communication: Between Open Standards, Innovation and Crusade Resistance
Looking at the future of digital communication, the RCS saga and the Google battle for messaging on Android offer an eloquent case of study on the intrinsic challenges in creating a universal standard and the persistent resistance of consolidated actors. The current landscape is a complex mosaic of proprietary services that enjoy a solid network effect, open standards that struggle to achieve universal adoption and a constant need for innovation that often meets the reality of existing infrastructure and commercial interests. It is plausible that Google’s push for RCS will continue, supported by the introduction of increasingly advanced features and, hopefully, by a universal end-to-end encryption that exceeds current limitations. The regulatory pressure, particularly by government agencies in regions such as the European Union, could also play a crucial role, forcing interoperability between platforms and potentially forcing actors like Apple to consider the adoption of RCS or other open standards. The Digital Markets Act (DMA) of the EU, for example, has the potential to impose interoperability requirements on the “gatekeepers” of the technological sector, which could include iMessage. If this happens, it could be the most significant catalyst for the universal adoption of RCS or a similar protocol. However, even with such pressures, resistance will probably be strong, as companies will fiercely defend their ecosystems and competitive advantages. Innovation will not stop. Beyond RCS, we could see the emergence of new protocols or the evolution of existing ones, driven by an increasing interest in decentralization (such as the Matrix protocol) or a greater emphasis on privacy and anonymity. Augmented reality and virtual reality could also introduce new forms of communication that will require new standards and approaches to messaging. The fundamental challenge remains the balance between the creation of an open and universal standard that benefits all users, and the ability of companies to innovate and monetize their services. As long as these two forces are in direct conflict, the “mess mess” will probably persist in some form. Users, meanwhile, will continue to dexter between different apps, each with their own pros and cons, waiting for a future in which digital communication is really smooth, safe and barrier-free, regardless of the brand of their device or their geographical location. The road is long and winding, but the desire for universal, interoperable and safe messaging remains a persistent driving force in the technological landscape.
