Google Will Implement End-To-End Encryption of Messages; Complete Global Roll-Out of RCS

Google Will Implement End-To-End Encryption of Messages; Complete Global Roll-Out of RCS

Google Will Implement End-To-End Encryption of Messages; Complete Global Roll-Out of RCS

The American multinational technology company that specializes in Internet-related services and products ‘Google’ has announced new features for messages, Android’s answer to Apple iMessage.

One of the Big five companies in the United States ‘Google’ has now shared an update on its implementation of Rich Communication Services (RCS) and stated that the service is now available globally through the company’s own Messages app.

The Rich Communication Services will bring with it a range of “chat features” that you usually don’t get from SMS, such as read receipts, keystroke indicators, better media sharing, and more. Moreover, Apple has been offering something like this for some time with a post, but Android has been missing from a widely adopted competitor, which is probably why Google is pushing its RCS implementation harder.

However, Increased availability naturally means more users can benefit from these enhancements, and one less reason to consider using an iPhone on an Android device.

In a statement, Google’s Product Lead, Drew Rowny said “Today, we have completed our global rollout of chat features to make this modern messaging experience universal and interconnected for everyone on Android. Now, anyone who uses Messages across the world1 has access to modem chat features either from their operator or directly from Google.”

Meanwhile, Google has also announced that it is building security for RCS messaging for Android by allowing end-to-end encryption, a capability that was rumored to be in work earlier in the year.

Lastly, individual conversations will be the first to support it, and as with other RCS features, both sides of the conversation should use the Messages app with chat features enabled.

Leave a Reply

Your email address will not be published. Required fields are marked *