Pssst.
Not all countries support the old GSM/EDGE/HSPA bands anymore so that Nokia 3310 may not work in Canada on Roger's, Bell, nor Telus' networks as those bands got sold off for emergency services.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
RCS in iOS 18: What You Need to Know About Apple's Android Messaging Overhaul
- Thread starter MacRumors
- Start date
- Sort by reaction score
Not all countries support the old GSM/EDGE/HSPA bands anymore so that Nokia 3310 may not work in Canada on Roger's, Bell, nor Telus' networks as those bands got sold off for emergency services.
Everything I look at this Members profile pic I see ..
A face wearing shades, tiny nose and what looks like a cartoon drawing of an O mouth shape holding a cigerrate off to the right side (my right when viewing)
Does anyone else?!
Attachments
Re: Number 2 on your list - Apple has said that they're working with GSMA to add native E2E encryption to the RCS standard. That should eliminate the need for Google to do its own encryption, unless they decide that whatever Apple and GSMA develop isn't as good as what they already have.
It's not "anecdotal" that WhatsApp is more popular globally than iMessage. Compare global usage of iMessage to global usage of WhatsApp and you'll see there are twice as many active daily WhatsApp users*
Apple has already said they're working with GSMA to implement native E2E encryption in the RCS protocol. So, once Apple finally implements RCS, is there any real advantage to iMessage over any other RCS client -- or WhatsApp, for that matter -- other than the green-bubble nonsense? I mean, the reality is that iMessage really doesn't have anything to offer that isn't already offered (or done better) by other apps.
* Sources: https://www.usesignhouse.com/blog/imessage-stats and https://www.statista.com/statistics/258749/most-popular-global-mobile-messenger-apps/
Last edited by a moderator:
I gave you some data to show why I think your claim of many is unlikely, and why I think a majority not experiencing problems significant enough and often enough to warrant action is reasonable.
I used 10% to illustrate if your claim of many held up then the outcry would be noticeable. That there isn't such an outcry leads to teh conclusion many do not have that issue.
You are making my point.
Never said zero issues, just that the problems are not significant enough form users to have issues with iMessage. Just because an occasional message may be problematic doesn't mean a user has an issue with iMessage.
Again, both our experiences are anecdotal.
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...
Native app on the iPhone that you know all iPhones have, unlike other choices where your intended recipient may not have an account.
'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
No? Sending 3 trillion messages does not mean users didn't experience an issue while sending those messages. I never said this confusion prevents people from sending messages.
Having a confusing ux != user cannot send message. Data point is completely irrelevant. A lack of story means nothing.
I never said they couldn't use iMessage entirely. I said there's a confusing UX feature. You are completely misunderstanding the issue.
And you're the one making a claim that is not true. I'm not. Anecdotal supports what I said. You would need more than anecdotal to support your claim of "majority".
Think you are going to need iMessage. Unless you have a third party rcs app you will need iMessage. But imo apple is going to build rcs into iMessage.
That is not what my understanding. RCS is upgrade to SMS, it has nothing to do with iMessage. When I am sending text from iPhone to Android, it will try to default to iMessage, if not, then it will goes to RCS, if not then it will send as traditional SMS. Same as current way of doing things, but instead of fall back to SMS, it will try to send RCS first
iMessage is needed to send an sms unless one has a third party app that lets you do that. While you don’t start out be sending an sms you text to a phone number or contact, if an iMessage can’t be sent you can configure iMessage to send an sms. Rcs will I believe be a protocol to try before sms.
Here is no need for iMessage. I have turned off iMessage on my iPhone.
Text message sent to my Android (Xiaomi) as sms message.
Here is the screenshot for sending text message
Without iMessage, the message app will simply send as text message, even if the recipient has iPhone. There is no need for iMessage to be turn on for iPhone to send text message.
If I have an iPhone with the out of box configuration, without Apple ID logged in, I can still send text message if I have SIM card. It doesn’t make any sense if iPhone can’t send text messages without iMessage turned on.
Last edited:
I believe that is what I said (or what I was getting at). You need imessage (the app) not the service. Imessage,imo, will still send as sms if RCS isn't available.
There is no iMeeeage app… ever. The app you are using to send iMeeeage is called Message….
I have shown you, that iMessage is not needed to send text message…
I think you are wrong about what an issue the UX is for most users. It simply works for most users of iMessage and that is what is important.
People can easily compose a message, messages get through, and people simply use teh software and don't care what a small percentage of users on a forum care or think.
IMHO, this whole "issue" is much ado about nothing.
And you need more than anecdotal to support the claims you are making. There simply is no good data either way, so you have to draw inferences based on experience and what is widely reported.
A I pointed out earlier, I said I suspect a majority of users have no issue with iMessage, and based on what I've seen and read I think that is probably true vs your claims of it being an issue. An occasional glitch does not make something an issue nor just because it effects you make it an issue.
It's clear neither of us will agree on whether or not iMessage has an issue that warrants action. Either way, RCS seems to be in iMessage's future. It will be interesting to see what impact that has on users. I suspect very little.
"simply works" disagreed.
easily? disagreed.
disagreed
Wrong. 100% wrong. My claim of 'many' is subjective. You can disagree what my definition of 'many' is, but I absolutely don't need more data to prove my subjective claim of 'many'
and you would need more data to prove 'majority' than just what you've seen because majority means more than 50% of the user base.
Nor do I for my supposition of a majority.
However, if even "many" users had issues with iMessage it would be news. That is doesn't belies your claim of many, IMHO.
A handful of people on a message board having some sort of issue with iPhone does not mean many do.
Nor do I for my subjective statement. If you read what I said, I never claimed I had data, just a supposition based on observation. As with any observation, it is subject o interpretation.
No. It isn’t. You don’t need iMessage to send RCS message. The message app is simply a messaging app that can send both iMessage and RCS.
Technically, Google can pull this off as well, since it is now mandate all Android phone maker to install Google Message on their phone, Google can achieve similar with iMessage. If Apple allows third party messaging app as default, Google can offer its messaging app on App Store, then you can use Google’s version of iMessage on iPhone.
no, actually you do.
I can't say majority of MacRumors forum members own an Android device. But I can say many do. Many can mean whatever I think many exactly means. Majority would have to mean more than 50% of all MacRumors forum members. I would need hard data to back up "majority". However, I would simply need anecdotal observations to back up my definition of what "many" would mean in this context.
Like the Red Queen., eh?
Except I was not referring to MacRumors readers, who are an unrepresentative set of Apple users.
I gave you numbers why I suppose a majority of users have no issues with iMessage, but you didn’t like them. Frankly, an occasional glitch is hardly an issue. If it was an issue for more than some “many,” whatever you mean by that, it would be news beyond arguing on a forum. That it’s not gives credence to my supposition.
what?
I didn't say you were referring to it. I don't think you even read my post at all if you're making this statement.
anecdotal/irrelevant numbers don't support "majority". they back an arbitrary amount such as 'many'.
it's clear you aren't reading what I write so what's the point anymore? I'm leaving this convo.
Your example was of a self selected data set that can easily be analyzed based on posts, unlike what we are talking about.
One final thought:
Umless your “many” is 50% or greater, 100% - many is less than 50% and thus by your own anecdotal data a majority of users have no issues, as I suspected.
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.