Last year, a change to Chrome OS revealed that Messages for Web would be transitioning from Android.com to Google.com. This lined up with the recent transition from the “Android Messages” name to simply “Messages.” Today, a slightly updated version of Messages for Web with RCS settings has gone live on Google.com.
Last month, we covered the strong possibility of Android Q providing new APIs for RCS messaging to third-party app developers, based on some evidence in Android code. It appears that Google’s plans may have changed in the intervening month, according to a new commit.
With last year’s announcement of the “Chat” initiative, it became clear that Google would be working to make RCS the best possible messaging product for everyone. Staying true to that commitment, it seems Android Q may bring RCS capabilities to third-party apps with new system APIs.
Over the past week, the narrative around Google’s messaging and communication services has been defined by a spate of planned deprecations — both of which NewGeekGuide first reported about. While older services will be “sunset,” the company’s vision for consumers hasn’t changed much since earlier this year, revolving around RCS “Chat” and Google Duo video calling.
However, complicating this dual-service future now is the newly-revealed fact that the enterprise-focused Hangouts Chat and Meet will also be available to consumers, and that Google Voice is still an active service. This is just the latest in Google’s tangled and sometimes incoherent strategy for simply saying “Hello.”
Last month, it emerged that Verizon was planning to launch Universal Profile RCS early next year. The Google-backed messaging standard is now set to officially begin rolling out on December 6th for the Pixel 3 and Pixel 3 XL.
When Google earlier this year detailed that its future consumer messaging effort would be centered around RCS and Messages, AT&T and Verizon also signaled that it would adopt the Universal Profile. The latter carrier might be launching support early next year.
RCS is the next big attempt spearheaded by Google to improve messaging on Android, and today Samsung has announced that it is working with Google to ensure that its messaging app works properly with RCS and Android Messages.
Google last month introduced the highly anticipated ability to send and receive texts from the web. The feature reflects how Google is centering its messaging future around Android Messages and ultimately RCS. That standard, long touted as an upgrade to SMS, is finally getting adoption from all the key players around the world and users are closer than ever to benefiting from it.
But as the world makes this shift, it can be a bit confusing to see what distinguishes Google’s Android Messages app and the RCS standard. Oh, and what’s that “Chat” thing I’ve heard about?
Oreo has been slowly rolling out to various Galaxy S7 and S7 Edge variants over the last several months, and now it’s T-Mobile’s turn. But this update involves more than just a firmware update, it also includes support for RCS Universal Profile 1.0, allowing for richer communications between carriers.
While the Executive Branch is warming up to Chinese companies like ZTE following the reversal of an export ban, Congress is continuing to scrutinize US companies working with China. The legislative body is now particularly focusing on a Google and Huawei partnership announced in January to push RCS adoption.
Over a year ago, Google announced that Android Messages would be preloaded by 20+ OEMs as the official RCS client. Now, Google is finalizing its RCS partnerships with carriers and OEMs and will be calling the RCS standard “Chat.”
Recent weeks have seen Huawei’s attempts to enter the U.S. cellular market flounder, while there might be more trouble ahead related to 5G development. Regardless, the Chinese smartphone maker is pressing on with a new Google partnership to make Android Messages the default RCS client on its devices.
Sprint started the trend in the US last fall, and Canadian carrier Rogers followed soon after. Now, Telenor has jumped on board with Google’s RCS solution in Messenger, bringing the feature to its customers across India, Thailand, and a variety of European nations (via The Keynote)…
Yesterday, several publications across the web reported that T-Mobile — which launched its own RCS platform in the form of “Advanced Messaging” all the way back in 2015 — has begun rolling out support for Google’s RCS offering in the Messenger app for Android devices. Sadly, it seems that this was just a wild and substanceless rumor that has no actual basis in reality…
After laying the groundwork and garnering support from carriers worldwide, Google is finally launching RCS messaging. Android devices on Sprint will be the first to send and receive enhanced SMS messages that feature read receipts, better group chat, high-res photo sharing, and more.
Google made its commitment to RCS (Rich Communications Services) clear last year when the company acquired Jibe, but now things are getting even more serious. The GSM Association today announced that it, more than 15 global mobile operators around the world, and Google, have finally struck a deal to actually make bring RCS to widespread adoption. And Google says that an Android RCS client is in the works, being made in collaboration with several Android OEMs and the aforementioned mobile operators…
Google has today announced that it is acquiring Jibe Mobile, a team that’s now getting on board to help Google bring Rich Communications Services (RCS) to a global audience. As per the company’s Android blog:
As part of this commitment, we’re also very excited to announce that the Jibe Mobile team is joining Google to help us bring RCS to a global audience. Jibe is a leading provider of RCS services and they’ll continue helping carriers easily deploy RCS to their users. We can’t wait to work with them and build on the great work that they’ve already done.
If this all sounds like a foreign language to you, you’re not alone. RCS, like SMS, is a carrier-based standard for messaging. And while messaging apps like Hangouts, Facebook Messages, WhatsApp, and others are gaining popularity, standard messaging via carrier tech is still more than common.
Basically, RCS intends to be the next SMS. SMS is just falling behind in its capabilities in a world where people expect to be able to send videos, photos, and other content easily to friends. RCS hopes to fix that, and Google is working with many partners to aly the groundwork to roll the technology out more widely.
However, the features available in SMS haven’t kept up with modern messaging apps. Rich Communications Services (RCS) is a new standard for carrier messaging and brings many of the features that people now expect from mobile messaging, such as group chats, high res photos and more.
Many leaders in the wireless industry have already put great work into laying the foundation for RCS, and we’ve heard from many of them that there are ways Android can help. 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. We’re already working closely with many of our partners on implementing RCS, and look forward to growing the RCS ecosystem together.
Here’s what Jibe had to say on their blog:
As a good friend once told me, if you want to do something big, start with something small — a single, singular challenge you can lead, and rally others to support.
For Jibe — a company we founded in 2006 — that lesson came true today with the announcement that we’ve been acquired by Google. The big opportunity we saw at the start: to change the way people communicate using their mobile phones.
The “small” challenge we focused on: the future of messaging, the super simple mode for communication that’s favored by billions of people, all over the world.
