Most people think the day when telco messaging services lose out completely to WhatsApp, Skype and iMessage is very close. Not Google, however, which has been seeking to breathe new life into the GSMA’s Rich Communication Services (RCS) and, in the process, create an effective messaging application for itself.
Google has been working with RCS since it acquired Jibe Mobile in 2015 and in 2016 it released a universal profile which would allow different implementations to work together. Its unexpected interest was probably the only thing that saved RCS from being completely moribund, given that only a small handful of operators had supported it, and only Spain and South Korea had multi-operator roaming.
Now the search giant has decided to focus its mobile messaging efforts – which are dwarfed by those of Microsoft, Apple and Facebook – entirely on RCS, suspending work on its own app, Allo, which was launched in 2016. This will position it as the operators’ friend, rather than their nemesis (like WhatsApp), since it will cooperate with them while pushing RCS – but it will offer free Android messaging, so it will play its part in wiping out the revenues that still remain for MNOs with paid-for text services.
The early hopes for RCS – that it would support rich messaging experiences which customers would be happy to pay for, despite the rise of free services like WhatsApp – have unsurprisingly been dashed. While the GSMA and the few RCS deployers spent years working on services and interoperability tests, the over-the-top alternatives changed the face of mobile communications, and left Google out in the cold too.
In its latest – and almost certainly futile – effort to seize back the initiative, the company says it will make its implementation of RCS, called Chat, the default messaging service on Android. This will be an evolution of the current Android Messages, with new features which will make it work similarly to iMessage, and set it apart from the OTT offerings. These features will include read receipts, full resolution images and video, and group texts. However, it will not support end-to-end encryption.
Google’s own OTT effort, Allo, will be axed. The future of its other two messaging apps, Duo and Hangouts, is less clear.
The way that Google hopes to encourage usage is by getting the operators on its side. This will be an operator-based service rather than a Google service, and messages will be part of the user’s data plan, not a separate SMS plan. This, the search company argues, will give MNOs a route away from SMS, which will nevertheless keep customers attached to their brand.
Google says the Universal Profile, the GSMA spec which it supported and effectively launched in the market two years ago, is now supported by 55 operators round the world, and by Microsoft. The GSMA says this is “a single, industry-agreed set of features and technical enablers developed to simplify the product development and global operator deployment of RCS”.
Anil Sabharwal, the Google executive behind the Photos app, will lead the initiative. He said: “We can’t do it without carrier partners. We don’t believe in taking the approach that Apple does. We are fundamentally an open ecosystem”.
Successful or not, the RCS adventure highlights the way in which Google behaves very differently from OTT internet providers. In the mobile world, it gets a lot of its power from creating harmonized platforms – notably Android of course – which drive usage for operators and are not inherently hostile to them. Unlike Apple’s walled gardens, Android and apps like Chat can be harnessed by MNOs to improve their own offerings.
Some resent the success of Android in killing off the MNO’s own mobile platforms and experiences, but successive attempts by operators to create open, interoperable APIs, services and apps platforms have failed. Google’s developer base is more effective than those of the individual MNOs because it promises them a vast user base, not a fragmented and politically divided one.
So if Chat succeeds, it will because Google brought the ecosystem together and made a workable app out of years of GSMA operators’ technical tinkering. But success will likely come largely at the expense of remaining SMS usage, not because it steals significant share from WhatsApp, even if it is the default option on Android phones (except Samsung’s, a notable gap).
It is more likely to fail. Google has been surprisingly weak at creating a compelling messaging offer and having RCS as its base hardly suggests this one will be better. Operator support is valuable but not a deciding factor in an app’s success (though some of WhatsApp’s strongest early markets were built in partnership with emerging market MNOs).
But the likelihood of RCS delivering its ambitious goal of saving MNOs’ messaging business is almost as far away as before. Formerly branded joyn, RCS adds value added capabilities such as group chat and high quality video messaging to carrier- supplied voice and SMS, in 3G or 4G networks. It is designed to offer a superior experience to that of WhatsApp, Skype and Facebook Messenger, keeping users loyal to cellular solutions. Though voice and messaging are offered at very low cost by most MNOs to fend off over-the-top challenges, keeping subscribers on the cellular services drives additional, paid-for usage and allows the operator to monitor and monetize the user.
And relying on Google to provide the usable, interoperable app they failed to produce themselves is a double-edged sword for operators, since it puts a standard which was supposed to be controlled by them, into the hands of the greatest challenger to their power.
While Sprint was the first partner to launch Google RCS commercially, in 2016, many MNOs have held back, or moved on to a non-RCS solution. Deutsche Telekom CTO Bruno Jacobfeuerborn spoke for many when he said: “RCS was much too complex. This is something we shouldn’t do again. We need to focus on simplifying services for consumers.”
And also in 2016, RCS suffered a blow when two of the three Korean operators – which had been the first to launch RCS services – shut these down, citing hefty competition from popular free app KakaoTalk. Even those operators with RCS applications often have their own offerings too, as well as partnerships with OTT players.
The issue of control will continue to rear its head, even if most MNOs feel that they have no choice but to support Chat as their contingency plan for SMS decline. To avoid being relegated to the role of bit-pipe, MNOs must keep control of the user experience, and how the subscribers move around the network. The RCS activity is an indication that Google wants to control that experience itself, in order to be in pole position to monetize it, as well as beat back Facebook. Sometimes it does that by using technologies which bypass or sideline the carrier – the multi-network access of Google Fi, services like Google Voice. But sometimes it tries to infiltrate the mobile domain directly.
“We’re excited to team up with mobile operators, device makers and the rest of the Android ecosystem to support RCS standards and help accelerate their deployment in a more consistent way,” said Google when it acquired Jibe. The phrase ‘more consistent’ is key – Google wants to make sure it defines the user experience of mobile messaging for the new generation itself, not MNO-focused bodies like the 3GPP or GSMA.