Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I would not put it past Google, especially if stuff stays on Apple's vs Google's servers, and messaging will continue to be balkanized and SMS used as fallback...
I actually have the same concern but in the opposite direction: When my Android device is involved in a group chat with iPhone users (all of whom use iMessage because Apple refuses to allow anything else), every once in a while the group text gets wonky and I end up missing messages or their delivery is delayed. Maybe this is just a weakness in the SMS/MMS protocol (which Apple insists on continuing to use, despite how clear it is that SMS and MMS have long outlived their usefulness), or maybe it's an issue just with how iMessage is encoding its messages. But my worry is that that Apple will do something else to make the RCS experience as bad as it is now with SMS/MMS. I suppose only time will tell -- for both of our concerns.
 
'my experience' would be textbook definition of anecdotal.

usage of WhatsApp doesn't really prove there isn't a confusing ux in iMessage with how it relates to sms/iMessage

I am unsure what your point is. Are you saying that the iMessage interface is confusing?
 
What "account" does the intended recipient need to have? The whole point of a platform-independent and standards-based messaging system is that it should work as long as the user has an app that implements the standard. Are you referring to an iCloud account? If so, how and why should that matter?

It sounds like the only advantage you're suggesting would be a blue versus green bubble? And frankly, that seems trivial.

All the other "superior features" of iMessage are provided by other apps -- whether that's iMessage itself after RCS is implemented, or WhatsApp.
My point was that in the current state of affairs, SMS is the only real cross platform protocol that works between various apps. Others, such as What’s App, require an account to be used; even if the protocol is based on an opens source one, so sending messages cross app is still not possible. At least with iMessage it’s baked into every iPhone; even if it is not a superior app. Ubiquitousness is a superiority al of its own, to paraphrase an old statement.
 
My point was that in the current state of affairs, SMS is the only real cross platform protocol that works between various apps. Others, such as What’s App, require an account to be used; even if the protocol is based on an opens source one, so sending messages cross app is still not possible. At least with iMessage it’s baked into every iPhone; even if it is not a superior app. Ubiquitousness is a superiority al of its own, to paraphrase an old statement.
Okay, I understand your point now. And yes, if anyone wants to replace the current SMS/MMS technology, it's important to have an app on the phone that doesn't require creating another account. But, here once again, it's Apple who is preventing that from happening by refusing to allow any such apps (because they would compete with iMessage) to be available to users in the App Store. If Apple made Google's messaging app available on the Apple Store, or if they made their own iMessage available in Google's Play Store, then people would have the choice. But Apple famously doesn't want to do either of those things.
 
Okay, I understand your point now. And yes, if anyone wants to replace the current SMS/MMS technology, it's important to have an app on the phone that doesn't require creating another account. But, here once again, it's Apple who is preventing that from happening by refusing to allow any such apps (because they would compete with iMessage) to be available to users in the App Store. If Apple made Google's messaging app available on the Apple Store, or if they made their own iMessage available in Google's Play Store, then people would have the choice. But Apple famously doesn't want to do either of those things.

The only way for truly universal messaging standard that replaces SMS/MMS is both platform’s default messaging app need to support same standard.

Currently, Google is mandating all Android phone support RCS as standard messaging protocol. The only logic way now is Apple to adopt RCS on its messaging app.

To be honest, I don’t believe allowing Google Message app on iOS would change anything. Most iOS user would use default messaging app, aka Messages on iOS.
 
I am unsure what your point is. Are you saying that the iMessage interface is confusing?
I'm not going to rehash and summarize the conversation that you jumped into.

Read the past responses and you'll literally find the answer to your question.
 
I already did actually.

You: " Are you saying that the iMessage interface is confusing?"
Me earlier in the thread: "blue vs green bubbles is already confusing for many." https://forums.macrumors.com/thread...-communication-services.2411654/post-32744605

You just admitted that you failed to read. That's great so I'm moving on.
See? Now, was that so hard after all? You could have provided that link earlier, and it wouldn't have necessitated you copping an attitude with me.

Now, if you spent half as much time in critical thought and reason as you do spewing bad attitude, this could have been resolved much earlier.

Or you can continue being confrontational with no reason. Your choice.
 
It’s funny that there’s no mention of whether or not iPadOS 18 and MacOS Sequoia and WatchOS 11 also supports RCS.
 
  • Like
Reactions: lozion
Same here in NZ. One of the providers has said that it'll cost around $3 million to implement RCS and that it's unlikely to happen when so many people already use third-party services and are unlikely to switch away from them.


That came up as well. In many countries, providers are required by law to have a backdoor, and therefore they can't offer encrypted RCS.
See, that would mean that Google couldn’t use encryption on their “flavor” of RCS either. Most likely RCS encryption would just be disabled by the carriers in those countries, this way Apple and Google can continue providing encryption to every other country.
 
I believe they'll keep the Green for non-iMessage, but include the status words ("Sent", "Delivered", "Read"), so that way you can distinguish when a green message is sent via RCS.
That’s exactly what they’re doing, which is a lot better then how Google does it with their weird check mark indicator mess.
 
See, that would mean that Google couldn’t use encryption on their “flavor” of RCS either. Most likely RCS encryption would just be disabled by the carriers in those countries, this way Apple and Google can continue providing encryption to every other country.
In my country it's covered under the Telecommunications Interception Capability and Security Act, which only applies to telecommunication companies. As Google is considered a software company it doesn't apply to Google's own-brand RCS, but it does apply to the 3GPP-standardised one.
 
It’s funny that there’s no mention of whether or not iPadOS 18 and MacOS Sequoia and WatchOS 11 also supports RCS.
It would be madness if they don't. At the same time, it is always possible it could be a deferred feature coming in an update after initial releases.
 
I don't care about the color of bubbles. But I do like the better texting experience with android people.

I can't believe people care about the color of bubbles.
 

Attachments

  • whoosh.jpg
    whoosh.jpg
    16.4 KB · Views: 69
Surely it doesn't have to connect via a phone if it is a cellular iPad?

(And a non-cellular iPad can use WiFi, can't it?)
The iPads have cellular data, phone calls/SMS require different networking chips. It might actually be built into the iPad but to enable it requires paying the licensing fees. In that case it would effectively be an iPhone and I’m sure there are reasons Apple doesn’t want that.
 
The way android and google was making this a big deal, I have 2 Android friends who have this. I thought it would be used a lot more.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.