They won't. It's part of their "slowly-closed-source-all-of-Android" plan. The old messaging app used to be part of AOSP and you could read the source, how delightful that was.
Would be a good time for a contender to start the third OS. In a few years, more of the population would have interest enough that it might actually get traction.
Fucking A. I hate using Googles shitty messaging app, and maybe I would have more than 2 other rcs users in my contacts if the 3rd parties could implement it.
I had visual voicemail on my previous 2 pixels (O2 in the UK), but not on my galaxy s23 ultra on the same network. Seems to be a pixel/iphone exclusive feature.
We don't know any details. Google is trumpeting a success and indicating a willingness to assist but it doesn't really tell us much of what it will look like. Apple is committing to RCS, the industry standard as it is (and I assume will be as I hope it breathes new life into the standard...) and not Google's current RCS + proprietary bits implementation.
When MS created a Windows Phone YouTube app, Google blocked it with requirements that were either arbitrary (it needs to be HTML5 for example despite iOS and Android apps being native) or impossible to meet. (requiring specific access that Google would not provide)
So while Google framed it as "Microsoft just needs to do X, Y, Z and it'll be all good!" - sounds good but it intentionally made said requirements impractical or impossible to complete.
Since Google's been conflating their RCS implementation with RCS the standard, I think it'll be a funny (if unfortunate) monkey's-paw result if Apple's adopts RCS completely as the backup to iMessage but continued carrier and Google implementation fumbling results in no change and the iPhone having to resort to SMS/MMS anyway.
(see: a while back when AT&T's RCS could only be used between a couple AT&T Samsung phones - but I do hope it's different this time, I got a group chat I rather take off Instagram.)
Google's paying for it and Apple's going to be using jibe.
It the same shit as Google being the default search on safari and iPhone.
Data scraping and advertising dollars.
Google currently has very limited insight about iPhone users messaging habits. iPhone users are using apple's iMessage, SMS, WhatsApp, Facebook messenger, telegram, signal, discord, slack etc. Most of which have limited Google interactions. On Android Google at least gets some info from third party messaging services. Like use time, installation, stored data size etc. On iPhone they can only scrap through search and Gmail.
Google has been trying to crack the messaging space for a while. They keep dropping messaging apps because they haven't been able to get the mass adoption. They've found their solution with RCS.
Take a open protocol that no carriers will seriously implement. Adapt it to your needs and restrict acces to it (no third party apps only Google and limited second party like Samsung). Create the implementation (jibe) give it to the carriers. When carriers don't do it, make a fallback to jibe in the messenger app. Unlike apple, Google messaging service is hard to notice - therefore easier to slip by. RCS messages have small text only at the start and a slightly different shade of blue.
Once it's established on Android. Publicly shame apple for not using your open standard, where most messages run through your server. Privately pay them for adoption and ensure it meshes with your version of the open standard. Taking away one of the last reasons the messenger app on android has to avoid Google by default.
It was the next, more feature-rich SMS/MMS. It floundered with carriers, Google flip-flopped several times on messaging and today, it has two forms. Google's RCS, but I'd liken it more to Google iMessage. And RCS the standard, which Google's implementation is based on and Apple will be adopting. I am hoping that this is a kick in the butt that everyone needs to actually get on the same page for an SMS successor.
You do need a messenger app. Google wants you believe you don't but you do.
It's baked into Google messages and Samsung messages (Samsung messages is just rebranded Google messages). It pre installed and defaulted if the person you tried to text can receive it.
Google RCS goes through the internet, not carrier networks. Most likely Google jibe service. Which you carrier may have Google implement for them, if not it will default to Google's own jibe service.
If a practically brand new flagship like the Pixel 6 has more bugs than an ancient iPhone XR, I don't think base Android can survive much longer. Basic functionality like YouTube PiP and theming glitch out regularly. Not to mention extended features like bubbles in Messages being broken since day one. Sure, I can sideload on Android, but if that comes to iPhone....
I can't seem to make $200 per year for a device work out with Android anymore. The pixel 6 should last 3 years in my opinion, but support for the 6 has been limited since the pixel 7 came out. Even at $900, I think the iPhone could prove to be a better deal with 6 years of support backed by a history of keeping such promises. USB-C, RCS, Sideloading are all I've been waiting for.