RCS: The Next-Generation Texting Protocol That Could Replace iMessage
What is RCS?
Rich Communication Services (RCS) is a next-generation messaging protocol that has the potential to revolutionise the way we communicate via our mobile devices. Unlike SMS and iMessage, which rely on outdated technologies, RCS utilises modern standards such as IP messaging and RTP for media transmission to provide a wide range of advanced features. These features include enhanced group messaging, high-quality media sharing, read receipts, and typing indicators. RCS also allows for Business Messaging, which enables companies to interact with their customers in a personalised manner.
The bone of contention
Apple’s battle with Google over the adoption of RCS on iMessage has been a hot topic in the tech industry. While Google has been actively promoting RCS as a replacement for SMS and has even built it into its Android Messages app, Apple has been slower to adopt the technology. This has led to a disagreement between the two companies over how RCS should be implemented and whether it should be a mandatory part of the messaging ecosystem. On one hand, Google argues that RCS is the future of messaging and that all stakeholders, including Apple, should support its adoption. On the other hand, Apple has expressed concerns about the security and privacy implications of RCS and has stated that it is committed to maintaining control over its messaging platform. As a result, the battle between Apple and Google over RCS on iMessage is likely to continue for the foreseeable future.
Why is RCS such a big deal?
RCS allows for enhanced communication, including interactive features such as conducting surveys, making reservations, and even completing transactions directly through the messaging platform. With RCS, the possibilities are endless, and it has the potential to revolutionize the way we communicate.
My Awakening
I was trying to reset my Google account’s password, and as usual, the OTP has to be sent to my phone to verify the authenticity of the request. Only this time, the SMS’s Alphanumeric sender had a profile picture. This wasn’t an SMS I was curious to find out more about this mysterious sender.
You can see from the screen grab above that I was also able to text back and it was delivered. It was way past midnight but I couldn’t sleep before I got some answers.
My findings
Advancements in technology have allowed bots to send OTPs through SMS apps. I was intrigued by this and spent some time searching the web for more information. I eventually found a demo of the technology, which is still in its early stages. It was difficult to find a fully functional production app at the time of writing, but the future looks bright with innovations like these. If you’re a business owner looking to get your business on RCS, there are a few steps you can take. First, check if your messaging provider supports RCS. If they do, they should be able to guide you through the process of setting it up for your business. If your messaging provider does not support RCS, you may need to switch to a provider that does. Once you have a provider and an RCS-supported app, you can start creating and sending interactive, visually appealing messages to your customers through the SMS platform. For more information on RCS, visit the official RCS website: https://jibe.google.com/
You can head over to https://bonjour-rail.appspot.com to try the demo from the demo, you can view your train tickets and order meals from the train’s menu.
Parting shot
The future of RCS looks very promising. With this protocol, companies will be able to deliver a rich, interactive experience to users directly through their SMS app. This is currently possible through apps like Messenger, but not all users use that platform. RCS allows businesses to reach all their users on a single platform. Unfortunately, Apple is currently hindering the growth of this industry by blocking the protocol from their messaging app. However, if you’ve tried the demo, you know that RCS has the potential to be an iMessage killer.
