Re: Finally iOS 18 will be able to schedule messages

Chris wrote on Thu, 13 Jun 2024 20:25:25 -0000 (UTC) :

While technically that's true, how many times have you sent an SMS/MMS
message and had it NOT arrive within seconds of you sending it?

 
I mostly communicate via imessage or whatsapp so SMS is rare. I have had it
fail, but couldn't tell you how often.

In my experience, when I send an (unscheduled, i.e., normal) SMS message,
the recipient gets it within seconds of me sending it.

If I'm not in an area that has coverage at the time I initiated the
sending, then it has been my experience that the recipient automatically
gets it only after I move to an area that has coverage.

Hence, it appears to be queued up on my phone; but I leave it to the
Android experts to explain better how a failed SMS message is queued up.

Ooops. Wrong link. Here's the correct link to the example I just provided.

<https://i.postimg.cc/v86wXwtJ/scheduledmessage.jpg>

 
Does it still work if the phone is off/has no signal/in airplane mode?

 
Completely outside the topic of "scheduled messages", I hike often in
backcountry that has low cellular service where my experience is that any
queued up SMS messages get sent en masse when my phone enters a cellular
service area.
 
Back on the topic of scheduled messages though, based on the WSJ article

 
You misunderstand. I was asking about *your* method. Does it work when
there's no mobile signal? And if it doesn't, what happens? Do scheduled
messages fail completely or is it sent next time signal is available?

Thanks for clarifying the question, where I do NOT know what happens using
the age-old Android method of sending scheduled messages if at the time the
message is scheduled to be sent, there is no cellular coverage.

I suspect that the same thing "should" happen that happens when I send an
SMS message when I have no coverage, but I don't know if that is the case.

Bear in mind the EXTREMELY IMPORTANT distinction that sending messages with
iOS typically involves logging into Apple messaging servers, whereas on
Android, you're never required to log into any server to send a message.

Hence, I suspect that the Android method keeps trying as I don't see any
distinction in HOW it's sent between sending a message NOW versus sending
it scheduled for later. But I could be wrong on that.