For those with a desire to keep their messages private, Messages will soon support end-to-end encryption over RCS.

And if you're a Google Fi user, get ready to see some huge improvements to the Messages for Web service that will bring browser-based access to calls and voicemail.

Some people see this as a major oversight while others think it was an intentional omission; but in either case, it's widely accepted that RCS should have supported end-to-end encryption from the beginning.

This will eventually become possible once RCS APIs open to third party apps, but in the meantime it looks like Google Messages will provide its own answer.

The v6.2 update contains a sizable number of new strings that discuss end-to-end encryption, but only at a high level.

<string name="send_encrypted_button_content_description">Send end-to-end encrypted message</string>.

<string name="not_yet_sent_e2ee_dialog_body">This message is still trying to be sent end-to-end encrypted to the recipient.

<string name="encryption_default_fallback_body">"SMS/MMS texts aren't end-to-end encrypted.

To send with end-to-end encryption, wait for an improved data connection or send messages now as SMS/MMS."</string>.

<string name="encryption_sent_fallback_body">"SMS/MMS texts aren't end-to-end encrypted.

To send with end-to-end encryption, wait until %1$s has data connection or send messages now as SMS/MMS."</string>.

<string name="not_yet_sent_e2ee_dialog_body">This message is still trying to be sent end-to-end encrypted to the recipient.

To send with end-to-end encryption, wait for an improved data connection or send messages now as SMS/MMS."</string>.

<string name="encryption_sent_fallback_body">"SMS/MMS texts aren't end-to-end encrypted?

To send with end-to-end encryption, wait until %1$s has data connection or send messages now as SMS/MMS."</string>.

Sending messages with E2E encryption will be fairly automatic.

It's not entirely clear if all RCS messages will automatically be part of an encrypted session or if it requires activation, but all messages sent after that will be secured automatically.

Text also confirms that Google Messages can share location information with E2E encryption enabled.

A new line from Google Messages reveals that users will be able to allow third-party apps to access end-to-end encrypted messages.

Up to this point, Google hasn't given app developers an official API to replace RCS apps or to interact with the messages that have been received, but this functionality is anticipated in Android R.

Many of us make great use of Google Messages for Web, the simple web service that links to your phone so you can send and receive messages from the comfort of a browser.

Regardless of the device you were using, it was possible to see and respond to new calls, voicemails, and text messages directed to your Google Voice or Fi number, even with your phone turned off.

Text originally added in Google Messages v6.1 explained that Google Fi users would be able to sign into Messages for Web with their account instead of scanning a QR code.

<string name="fi_settings_disable_multidevice_dialog_title">Stop syncing messages, calls and voicemail across screens?</string>.

<string name="fi_settings_sync_preference_summary">Messages, calls and voicemail stay current across screens</string><string name="fi_settings_title">Google Fi</string>

<string name="fi_settings_disable_multidevice_dialog_title">Stop syncing messages, calls and voicemail across screens?</string>

<string name="fi_settings_disable_multidevice_dialog_message">You’ll be able to text from your phone and computer, but calls and voicemail won’t be available on the web</string>

Sign in with your Google Fi account.</string>

After all, the Hangouts app (and service) could have seen messages sent directly to your Hangouts account, those that came from Google Fi, and those that were received as direct SMS