Maybe Google can work with Google on implementing a user-level API for Android so manufacturers don’t have a monopoly on RCS apps.
Maybe Google can work with Google on implementing RCS on Google’s own product Google Voice.
They all but abandoned that years ago. They ain’t implementing shit on it.
And hopefully everything becomes a standard so people on both operating systems can leverage these features together
This. They haven’t opened up the RCS stuff till now on Android to other apps.
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.
They have abandoned the app and multitudes of others in favour to their closed source apps. Multiple Open Source apps exists to fill the gaps though.
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.
Any bets on which implements RCS first, iOS or Google Voice?
let us have rcs with google messages when we link our google fi account or let us get our visual voicemails in the google dialler already :(
the only reason i link my account and turn off rcs is for visual voicemails on the web since the stock voicemail app is rubbish
So all the apple simps who always said Google refused to do this, what’s your retconned excuse now?
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.)
deleted by creator
This.
FINALLY
If Apple has to work with Google to implementat a protocol existing since ~2008 we know there is something off.
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.
What is rcs?
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.
Rich Communication Service.
It’s SMS or MMS but better.
You don’t need a messenger app and share your contacts with Facebook and Co.
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.
deleted by creator
I’m pretty close to switching to iPhone.
deleted by creator
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.
Many years of android experience and none of it matches any of this at all.
In fact I just kept a smartphone for my longest record. 3.5 years on a $350 Pixel 4a. That works out to half of the amount you say you strive for but cannot make work.
Sounds like user error.
I’ve just recently switched from my Xiaomi mi8 (May 2018, and about $300 I think) to a pixel 8 pro, mostly because I wanted a better camera and was curious about pixels. It’s so fascinating to hear about all the bugs and terrible experiences on old android devices, but I guess people like us are just the luckiest people in the world.
I don’t think we are that lucky. We just aren’t people who waited until 2023 to try Android the first time and then got super pissy because it differs from the locked down prison that iOS is. Apple users have Stockholm syndrome
I can relate to the comment. Within the last month Google messages has required me to resync my tablet app several times. Fixing that required logging out all devices and changing the login method. Speaking of messages, the tablet app is… Not very good. Messages take a long time to notify there, well after my watch, and when I open the app the message still takes a couple seconds to show up as it is apparently retrieving the message from the phone app. Even though the message is (still) shown in the notification. Reading messages on the tablet don’t clear the read receipt on the phone. Various random bugs seem to popup. On the phone I randomly get pictures or messages I had written to OTHER PEOPLE waiting to be sent. Google messages is king of a shit app and I greatly miss Textra and even Samsung Messages. Thank you Google for not opening the RCS API to third parties.
But that’s just messages. Googles auto fill service has sucked from day one. Often I will click a username or password multiple times trying to get the popup to show up. I’ll then sigh, go open Bitwarden, copy my password, go back to the app, click on the password field, and then… the fucking auto fill popup appears. This experience has been shit from day one and Google has never made any attempt to fix it that I can see.
Android Autos new split screen is nice. But every once in a while the maps side will become unresponsive. Or the media app just dissapears and I have a black in its place. Only way to fix that is to unplug the phone and plug it back in. Super fun driving down the road.
I really could go on and on… Google has a habit of dumping random features in the OS and then never bothering to update again as they go on to their next shiny feature like the dog from the movie Up when someone yells squirrel. Apple users may be smug with their “just works” mantra, and they are not immune to bugs like any software developer, but it really does seem to be a more polished experience devoid of issues like the above. It’s also a lot more boring… but I can understand why someone would make a switch. Attributing another person’s issues to user error because you THINK the android experience is flawless seems rather snarky.
I never said it was flawless. I just have a LOT of experience with android and reading that comment was like reading fiction about a strange but semi familiar topic. Not relatable at all.
Apple software is chocked full of bugs though despite your assertion it is more polished. I would know, I use it every day. I abandoned iOS many years ago for personal use because it’s utterly dogshit in every way, but for a couple of other examples, iOS simulator and Safari have more problems than I could list. IOS simulator I just thought of because of your claim that Google constantly abandons features. IOS simulator is the only way to test websites on older versions of safari, which is the worst browser by far often waiting 5-10 years longer than everyone else when it comes time to implement a new web standard. Good luck supporting users who can’t afford to buy a new device every couple of years. It’s like they actively work toward breaking older software. Currently the oldest iOS you can test against in iOS simulator is 13. Not that old…
I have trouble with all the software I’ve ever used, but your description of messages doesn’t sound like the one I have used for 5 years or so. I have only had a little trouble with the web version, a feature that iOS users have never had. If they want to send a text from their PC, they need a Mac and to use imessage. Gross.
You make some valid points. But they pertain to your own experience. Their post is just as valid, because someone asked him why he was thinking about switching and he gave his own experience. Also a valid point for his own view. It’s an opinion after all.
To say you haven’t experienced the problems are well and good, but to trivialize his points down to “user error” was kind of dickish.
They were making their statements as though that’s just the way android is. it isn’t.
Ah yes the classic “why are you using a feature, it’s your fault for wanting it to work”. Thanks. So helpful.
Are you high? No one said anything like that
I’ve had a ton of bugs on iPhone. But I completely agree with you. especially for the average consumer, iPhone will be just the easy choice.
Also Pixel 6 is just god awful with bugs. At this point I don’t think Google can fix all of them, so many just feel related to the chip. I’d assume it’s better on their newer phones but you shouldn’t have to buy a newer phone to get a bug fixed.
I have been diehard android but this is really testing me. I want to use the best phone, and Apple had already been making the hardware. (Though, snapdragon 8 gen 2 has really redeemed itself, absolutely incredible, efficient and great chip. One of the reasons I just can’t see myself using a Pixel again)
