You really can open up the app and do this. It's a tap. I just feel like this is nitpicking. It's called "quick reply," not "drafts of lengthy messages."
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.
Don't accidentally miss the Send button in a quick reply!
- Thread starter SetHutBlue42
- Start date
- Sort by reaction score
You really can open up the app and do this. It's a tap. I just feel like this is nitpicking. It's called "quick reply," not "drafts of lengthy messages."
Not true on my end. I did a bunch of QR a little bit ago and they are all showing up in the appropriate thread in Messages.
ETA: I see you (OP) weren't pushing the send button. Uh, that'll do it. LOL.
Sorry but quick is meant there more in the sense of how fast you can get to reply to the message, not how long it takes you to actually type in that reply or how long it is. Completely different things, and one has nothing to do with the other.
----------
Why? If you are typing in a reply in Messages and leave the app suddenly for whatever reason, if you come back to it your message is generally still there. Why would it be so illogical to have something like that for this which does essentially the same thing but just from within the Notification Center essentially?
Wow, just wow...
Quick reply is referring to the ability to send a quick, as in fast to reply to them, message, not a brief reply. It's meant so you can stay in the app you are in and reply without having to leave that app. It has nothing to do with how long the reply it.
I can not believe how many people are defending Apple for something that was obviously overlooked. Are you guys meaning to say you have never accidentally tapped the screen when you didn't mean to? This is going to be an even bigger problem on the large 6 Plus, where since it's now a two handed phone, the chances of hitting something accidentally is even greater.
Tell me, what is the HARM in having a quick reply saved to your messages if it gets swiped away? If you are typing something in the quick reply but do not send it, there's a good chance you meant to send what you were typing, otherwise you wouldn't have typed it...
I agree, that can be a slight annoyance. But if your replying back a long message, then the blame is on you for not doing so in the message app. Quick reply is meant for short replies.
One thing they did right is ........ if you get another message while typing a quick reply, it will not interrupt anything, and will notify you only after your done.
One thing they did right is ........ if you get another message while typing a quick reply, it will not interrupt anything, and will notify you only after your done.
Since when is quick reply is meant for short replies? How does one even relate to the other?
Even that aside, if you typed even just a sentence in why should it just disappear suddenly if you simply touched the area in the middle of the sceen? How or why does that even make sense that simply touching there makes whatever you typed disappear and he whole quick reply screen just go away on a simple touch on a large otherwise useless area in the middle of the screen?
Since forever.
Cause there is no draft with quick reply.
The "Send" button is not small at all on the quick reply, so this shouldn't even be a common mistake.
Also, do you feel the same way about the home button? Cause pressing that by mistake would kill the quick reply too.
It would be better if they make it a double tap on the screen instead, but whether they do or not, it's not really going to be a serious or common issue.
Sorry must have missed where quick reply meant short messages since forever. Is that actually specified somewhere? Because rationally speaking one has nothing to do with the other. The quick in quick reply refers to the quick ability to get to a reply screen and send a reply without doing anything extra or needing to leave where you are. It's not a reference to how long or short your reply message actually is.
As for taping a large area on the screen that doesn't have a physical characteristic to it compared to a small home button that is located in a whole different area where you aren't even about to touch anything and actually requires a physical push on it to do something...well that already speaks of how these things aren't even comparable.
In other words, it doesn't exist. Quick = a fast way to reply, not quick = you can only type out a very short reply.
It is quick reply, probably intended for short responses.
If you're worried about losing long, carefully crafted texts, maybe just use the app?
If you're worried about losing long, carefully crafted texts, maybe just use the app?
what happens if you get another push while you type in quick reply? (i havent updated yet) but the whole implementation sounds horrible.
i have friends that text me like this
push1 hi
push2 how are you
push3 doing today
push4 lets meet
push5 at the movies
push6 around
push7 2pm
push8 okay?
push9 cool
push10 see you
push11 laters
what if i am in the middle of quick replying to "how are you". and he sends the "doing today" part right after. will my quickreply message go away and i have to start all over?
i have friends that text me like this
push1 hi
push2 how are you
push3 doing today
push4 lets meet
push5 at the movies
push6 around
push7 2pm
push8 okay?
push9 cool
push10 see you
push11 laters
what if i am in the middle of quick replying to "how are you". and he sends the "doing today" part right after. will my quickreply message go away and i have to start all over?
Common sense seems to imply that you are applying quick incorrectly there based on what you think it means. And just because many people might mistakingly believe it's the same thing doesn't really make it so.
Even Apple themselves doesn't refer to these as quick replies but simply interactive notifications. They talk about being able to quickly reply to a message without leaving the app you are in, not about writing a short reply quickly. There's a difference there, even if it's not one many would care to actually see or acknowledge.
----------
Why is it intended for short responses again? It's intended to provide for a quick way to get to a place where you can respond without disrupting what you are doing, but doesn't have some implication as to how fast you actually type out that response or how long at is. Two separate unrelated concepts. Granted in many cases the replies will be short, as it is generally the case with text messages to begin with even within the Measages app, but that doesn't mean that somehow the feature isn't there for longer replies or something else should be needed for those just because.
Last edited:
Don't accidentally miss the Send button in a quick reply!
It's just about fit and finish. If you close the messages app while typing it will be saved as draft, ready for you to continue the next time you open it. The same should really apply here really.
It's just about fit and finish. If you close the messages app while typing it will be saved as draft, ready for you to continue the next time you open it. The same should really apply here really.
So the OP was only bringing this up, evidently plenty of people can understand the caveats of typing a message in the quick reply box only for it be lost instead drafted if you accidentally 'miss' the send button. There's also the issue that you may deliberately touch outside the window to see something... Maybe you're sending a phone number and forgot the last few numbers so touch outside to go look it up and then come back to iMessage to see your text is gone. Things like that, you know, can be a real annoyance for something meant to make life easier and above all else quicker.
So to the people saying this a non- issue for them; whoop de doo for you but you didn't need to come in here to say that. Don't recollect anyone asking if you have the issue or not just warning you about it. And to the complete fucking morons that have gone out of their way to argue in favour of this hindsight, especially the brainless wonders saying a quick reply isn't supposed to contain a long message, seriously, GTFO my Internets.
Edit: And to the bell end below;
People like you need to be castrated. It would prevent future offspring of yours should you ever gather enough braincells to be able to procreate from ever being created and thus eliminating an entire ancestoral line of mentally challenged fuckwits from the Earth's future, which in turn might actually extend it somewhat and make the rest of us all the more safer.
So to the people saying this a non- issue for them; whoop de doo for you but you didn't need to come in here to say that. Don't recollect anyone asking if you have the issue or not just warning you about it. And to the complete fucking morons that have gone out of their way to argue in favour of this hindsight, especially the brainless wonders saying a quick reply isn't supposed to contain a long message, seriously, GTFO my Internets.
Edit: And to the bell end below;
*Slow clap*
People like you need to be castrated. It would prevent future offspring of yours should you ever gather enough braincells to be able to procreate from ever being created and thus eliminating an entire ancestoral line of mentally challenged fuckwits from the Earth's future, which in turn might actually extend it somewhat and make the rest of us all the more safer.
Last edited:
You can really tell in this thread the people who use their own brain and the people who use the brain provided to them by Apple.
This is a UX issue that I'm surprised that Apple would make. There are 2 basic problems here.
First, the quick reply should function the same as the messages app, when you leave the quick reply the message should be persistent.
Second, and I think the larger issue, is that tapping anywhere except the send button dismisses the quick reply in the exact same way that it would be dismissed if you had tapped the send, as a result a few times I've thought I've replied to a message only to find that it never sent and is now lost.
This is a UX issue that I'm surprised that Apple would make. There are 2 basic problems here.
First, the quick reply should function the same as the messages app, when you leave the quick reply the message should be persistent.
Second, and I think the larger issue, is that tapping anywhere except the send button dismisses the quick reply in the exact same way that it would be dismissed if you had tapped the send, as a result a few times I've thought I've replied to a message only to find that it never sent and is now lost.
Yeah, try reaching for that button on the iPhone 6 or Plus and see how many times you miss as your finger doesn't quite extend.
Pretty sure you're thinking of "Short Reply". Just because I have a quick SSD doesn't mean that I store short (small?) files on it. Just because I want to open something quickly doesn't necessarily mean that I want to severely limit what I can do once I get there.
This is the proper solution. Flick it back up. You could even implement two gestures: Pull down above the keyboard to send, flick up above the keyboard to clear and not send. It would give clear audio/visual confirmation of what happened. Or at least put the button lower. The text box and send button are right above the keyboard in the messages app because it makes sense. Why put a giant, tappable cancel button between where you type and where you tap send?
This is a stupid, stupid oversight. Not only for the accidental touches, but because you might need to look something up mid message, decide that your 'quick reply' wasn't really so quick anymore and you need to come back to it, etc.
What downside would there be to saving your text??
What downside would there be to saving your text??
If your writing that long of a message and you miss the send button, IT'S YOUR FAULT!!!! Cause the longer the message, the harder it is to miss the send button.
What's so hard at not touching the screen between the quick reply and the keyboard? Yes, if you're fumbling with your iPhone while doing other stuff, it's possible. But if it's that important or that much of an annoyance, then just FOCUS on the reply which takes less than a minute. Otherwise, IT'S YOUR FAULT!!!
This is not a big deal. I care either way if Apple does something about it or not.
Attachments
Wow.
Why you would go to lengths to defend this issue (which isn't major, but notable) is beyond me. When Apple fix/enhance quick reply and provide a solution to this issue, I wonder if you'll continue to be against it? Why do you care so much?
So to recap, I can see a few scenarios in which this can come about:
- Fumbling and accidentally touching to dismiss
- Realising you need to look up something before continuing your reply
- Misplaced tap
Why not just save the draft? Simple.
However there is also the issue where you don't realise you've missed the Send button. As far as I can tell there's no difference in information and animation on the screen when you hit Send and when you miss it. So you could think your text has sent when it hasn't.
Another slight enhancement then, might be to briefly display some kind of confirmation before the overlap slides up and off the screen. Perhaps collapse to the original size and show a little tick or something for half a second before disappearing.
I'm sure there are more elegant solutions.
Why you would go to lengths to defend this issue (which isn't major, but notable) is beyond me. When Apple fix/enhance quick reply and provide a solution to this issue, I wonder if you'll continue to be against it? Why do you care so much?
So to recap, I can see a few scenarios in which this can come about:
- Fumbling and accidentally touching to dismiss
- Realising you need to look up something before continuing your reply
- Misplaced tap
Why not just save the draft? Simple.
However there is also the issue where you don't realise you've missed the Send button. As far as I can tell there's no difference in information and animation on the screen when you hit Send and when you miss it. So you could think your text has sent when it hasn't.
Another slight enhancement then, might be to briefly display some kind of confirmation before the overlap slides up and off the screen. Perhaps collapse to the original size and show a little tick or something for half a second before disappearing.
I'm sure there are more elegant solutions.
Wow.. I shocked at the amount of blame and ignorance flowing through this thread... I wish Google Search produced more "help" than this thread really :-/
Having made this mistake numerous times on Beta and now the live iOS 8, this has been a huge annoyance.
This is 100% a UI issue and NOT a user error type of issue. And to blame the user is as insane and ignorant as blaming iPhone users for "holding their phone wrong" when WiFi/signal issues were a problem back on the older iPhones.
iOS 8 just released, and I guarantee this will be a bug fix, ideally in their first major update. There just hasn't been enough people using and bitching out about it (give it 2 weeks to a month).
When I am using QUICK REPLY; just like Apple has prevented other messages from interrupting my reply, there should be SOME type of preventative measure in place to keep the user from "accidentally" clicking anywhere but on the keyboard, the message, or the send button. Otherwise please if something, anything, was typed, it should automatically be set to a Draft or kept in the messages app as pre-written text. And please don't tell me how to use my own damn device. If I am in the middle of typing a sentence, and I want to correct a word, but instead I click just below the word and quick reply closes? That was NOT meant. Hell, I don't even remember Handcent, Chomp, or any of the many Android (and Jailbroken iOS) apps making this simple mistake!
It's clearly an overlooked issue, and hopefully enough of us are reporting this to have it be corrected in the first iOS 8 Update.
Having made this mistake numerous times on Beta and now the live iOS 8, this has been a huge annoyance.
This is 100% a UI issue and NOT a user error type of issue. And to blame the user is as insane and ignorant as blaming iPhone users for "holding their phone wrong" when WiFi/signal issues were a problem back on the older iPhones.
iOS 8 just released, and I guarantee this will be a bug fix, ideally in their first major update. There just hasn't been enough people using and bitching out about it (give it 2 weeks to a month).
When I am using QUICK REPLY; just like Apple has prevented other messages from interrupting my reply, there should be SOME type of preventative measure in place to keep the user from "accidentally" clicking anywhere but on the keyboard, the message, or the send button. Otherwise please if something, anything, was typed, it should automatically be set to a Draft or kept in the messages app as pre-written text. And please don't tell me how to use my own damn device. If I am in the middle of typing a sentence, and I want to correct a word, but instead I click just below the word and quick reply closes? That was NOT meant. Hell, I don't even remember Handcent, Chomp, or any of the many Android (and Jailbroken iOS) apps making this simple mistake!
It's clearly an overlooked issue, and hopefully enough of us are reporting this to have it be corrected in the first iOS 8 Update.