Agreed. Whether it's "I don't have service" or "My battery is dead," there are a number of conditions that keep a recipient from seeing a message right away, all of which are (usually) temporary.
Relying on "delivered" takes care of all of those situations, and is much more elegant in the UI than adding an "auto responder" message.
Does 'Delivered' show up when the message is received by another iOS device? e.g. I often leave my iPad at home but still connected to iMessage, and if that receives the messages my iPhone doesn't, wouldn't this give a false impression of delivery to the sender?
iMessage gets tricky when you have multiple devices.
For example, I went out of the country, but left my iPad at home (which also receives iMessages to my phone #). Because my phone wasn't data roaming, and my iPad was still on the network at home, iMessages were being delivered to the iPad. It basically meant anyone with an iPhone couldn't text me, because the text message fallback wasn't triggering. I had to find wifi with my iPhone to catch up on texts.
The "dead battery" auto-responder has the same issue. What if my iPhone battery is dead, but I'm on a Mountain Lion MacBook and getting messages there?
There are privacy concerns when you tell people about the state of another persons device. There is also the concept of sending a message saying a devices battery is dead "gosh iPhones always have dead batteries I keep getting this alert from my friends". These are good intention designs but not quite there.
iMessages has built in notification to the sender if the message has been delivered to the receiver, hence the status "Delivered" or (if receiver has opted-in) also Read status. I see no point in this feature, since the phone could be dead for various reasons, not just battery
It would be nice if the delivered indicator could be relied upon, but it seems to report that a message has been delivered once the Apple servers have received it, not when the destination device has received it.
This is especially noticeable under poor network conditions (I think I first noticed it at a music festival where even regular SMS messages struggled to get through due to network congestion).
This doesn't make any sense at all. iMessage is now tied to my iPhone, my iPad, an iPod Touch, two iMacs, and a Macbook Air. If my iPhone's battery dies, how will Apple know that I'm not in front of another device capable of getting messages?
"One potential reason that Apple wouldn’t implement this feature is that it increases user awareness of dead iPhone batteries"
I don't even
Why not turn it around and have iMessages send a "message received" notification when receiving a message?
Have it display like a little checkmark next to any sent message that turns green if the other phone pings back.
Just that - no read receipt like there is now, as that isn't always convenient.
Yep, it is built in, but many (including myself) disable it. It's pretty common that I accidentally open a message, but I don't have a response / a chance to respond yet, and I don't want the person to think I'm ignoring them.
In fact, SMS already has this system in place. Naturally there are some networks/phones that don't support it, and its meaning can vary from "network received" to "phone received".
I like this, but can see some problems with iMessage on multiple devices. Ignoring that, I'd love to get a push notification at ~5% battery asking me if I'd like to put an auto-responder on.
It can't make any negative remarks about the battery life of any idevice, but it could be kinda nice if it said whether or not the receivers idevice is turned off.
The problem hasn't got anything to do with delivery notifications or auto-responders: if you need an answer right away you must use a synchronous form of communication, e.g. voice call.
iMessage, SMS, email et al are async by design. Until you hear or see an ack that's from the actual recipient (and not something automated by a device), you can't be sure the message has been properly received.
[+] [-] steeve|13 years ago|reply
But it can be spotty at times with poor data connection.
[+] [-] hartleybrody|13 years ago|reply
Relying on "delivered" takes care of all of those situations, and is much more elegant in the UI than adding an "auto responder" message.
[+] [-] gpmcadam|13 years ago|reply
[+] [-] matthew-wegner|13 years ago|reply
For example, I went out of the country, but left my iPad at home (which also receives iMessages to my phone #). Because my phone wasn't data roaming, and my iPad was still on the network at home, iMessages were being delivered to the iPad. It basically meant anyone with an iPhone couldn't text me, because the text message fallback wasn't triggering. I had to find wifi with my iPhone to catch up on texts.
The "dead battery" auto-responder has the same issue. What if my iPhone battery is dead, but I'm on a Mountain Lion MacBook and getting messages there?
[+] [-] nwh|13 years ago|reply
[+] [-] coob|13 years ago|reply
Message search is also built into the iOS spotlight screen (left of first home screen).
[+] [-] almostbutnot|13 years ago|reply
[+] [-] rem1313|13 years ago|reply
[+] [-] k33l0r|13 years ago|reply
This is especially noticeable under poor network conditions (I think I first noticed it at a music festival where even regular SMS messages struggled to get through due to network congestion).
[+] [-] andrewroycarter|13 years ago|reply
"One potential reason that Apple wouldn’t implement this feature is that it increases user awareness of dead iPhone batteries" I don't even
[+] [-] pomajp|13 years ago|reply
[+] [-] Pwnadog|13 years ago|reply
[+] [-] nwh|13 years ago|reply
[+] [-] 10dpd|13 years ago|reply
[+] [-] treblig|13 years ago|reply
[+] [-] keeperofdakeys|13 years ago|reply
[+] [-] Alphasite_|13 years ago|reply
[+] [-] SparksZilla|13 years ago|reply
[+] [-] thegrul|13 years ago|reply
[+] [-] m_eiman|13 years ago|reply
iMessage, SMS, email et al are async by design. Until you hear or see an ack that's from the actual recipient (and not something automated by a device), you can't be sure the message has been properly received.
[+] [-] GuiA|13 years ago|reply
[+] [-] turutu|13 years ago|reply
[+] [-] adrr|13 years ago|reply
[+] [-] scottbartell|13 years ago|reply
[+] [-] BigBalli|13 years ago|reply