iOS 11.3 - Delete Message Confirmation

LACAllen wrote:

It’s an engineer who decided it was a cool feature and doesn’t understand how quickly we want to delete crap.

I see a lot of dumb and ill-informed statements here. This one is going in to my hall of fame.

Yup.

IdrisSeabright wrote:

LACAllen wrote:

It’s an engineer who decided it was a cool feature and doesn’t understand how quickly we want to delete crap.

I see a lot of dumb and ill-informed statements here. This one is going in to my hall of fame.

Yup.

Thrice Yup!

LACAllen wrote:

It’s an engineer who decided it was a cool feature and doesn’t understand how quickly we want to delete crap.

I see a lot of dumb and ill-informed statements here. This one is going in to my hall of fame.

Yup Yup. Yup. Yup.

Some people have no concept of how any large company works. Engineers NEVER make decisions about anything. They do what Marketing, Human Factors, User Experience, Sales and other higher level organizations dictate. And every design change is reviewed through many levels of management. No engineer has ever decided something was a cool feature and implemented it on their own. And there is a very good reason for every change. No changes are made as whims, except by Steve Jobs, and he hasn't had any whims in quite a while that he made known to anyone.

But how much time does it save when it prevents the deletion of message by mistake?

The users who want to turn this feature off are probably the same ones that refuse to backup also because it takes too much time.

i keep hearing the same argument (over and over) from people who like this feature: "What is the point in saving a little time if it keeps you from accidentally deleting a message you want to keep?" If deletion actually occurs on all devices, then why can't they at least add the feature back onto Mac whereby I could search for the messages I KNOW I want to delete, hold "option" and click the message without having to confirm. Yes, I have submitted it to apple.

ANNOYING when you have to delete multiples!

Only if you let it be ANNOYING.

We here at Apple Support Communities recognize that you have a choice of 1st world issues to let raise your blood pressure.

This really shouldn't be top of the list.

LACAllen wrote:

ANNOYING when you have to delete multiples!

Only if you let it be ANNOYING.

We here at Apple Support Communities recognize that you have a choice of 1st world issues to let raise your blood pressure.

This really shouldn't be top of the list.

Housemates who use the last of the toilet paper and don't get another roll from the linen closet are much more annoying.

LACAllen wrote:

IdrisSeabright wrote:

don't get another roll from the linen closet are much more annoying.

Somewhat afraid to ask ... but... over or under once deployed?

Depends on the absence or presence of cats.

Over and, because we have free standing holders, it also needs to be turned the right way or the roll slides off when you pull on it.

Fortunately, the cat isn't interested in toilet paper, just the empty cardboard rolls.

Batterista wrote:

If you have only one message to delete. ANNOYING when you have to delete multiples!

Then don't use swipe to delete if you have multiple messages to delete. Use Edit, tap all the messages you want to delete, then tap the trash can and voila, multiple messages are gone and without a need to confirm deletion. Had you bothered to actually read the thread, you'd have seen this option as well.

Batterista wrote:

If you have only one message to delete. ANNOYING when you have to delete multiples!

OMG - if you have to delete multiple messages, why wouldn't you just tap Edit (once), tap each message you want to deleted (1 tap for each message), and then tap the trash can.

So, if you were deleting, say, 10 messsages, you would tap one tap for Edit, ten taps for selection, and one tap for trash. A total of 12 taps.

If you were to delete those 10 messages the "old" way, it would take 1 tap to slide to the left, and one tap to delete each of the 10 mesages. So, a total of 20 taps.

With the new verification, you tap one tap to slide to left, one tap to delete, and one tap to verify deletion for each of the 10 messages. So a total of 30 taps.

So, you are grousing about 10 extra taps, when you have never even used a method that allows you to accomplish the same exercise in a measly 12 taps as opposed to your (original) 20 taps.

If saving nanoseconds of time is that critical to you, then it would be a good idea to figure out where you are wasting those nanoseconds by using inferior methods for achieving the same ends.

Best,

GB

gail from maine wrote:

If saving nanoseconds of time is that critical to you, then it would be a good idea to figure out where you are wasting those nanoseconds by using inferior methods for achieving the same ends.

Best,

GB

Think of the hundreds of messages that could have been deleted in the time it took to post a whiney message in ASC that will not affect anything in the world.

Webstuff wrote:

One more reason we need Samsung and google to provide competition to

Really? And another person who didn't read this thread. If you had, you'd have learned Samsung, Google, Pixel etc., ALL make you confirm delete for a text message. In fact, they ALWAYS have and Apple was just late to the confirmation party. But sure you can buy one and still have the same great feature to deal with if you want.

Bonhamet wrote:

I’m glad you agree. Too many people are having a problem with this. So far over 1500 people agree that this is an issue. There was a time when Apple set itself apart from everyone else.

I don't agree. I think this feature is essential now that Apple has introduced iMessage syncing.

I'm just tired of people complaining about it here.

There is no issue that has been fixed, and not sure what syning your test messages with your watch has to do with the additional "Delete" requirement for removing conversations.

You should try starting your own thread with your own question. Also, do not assume that anyone knows what you are referring to. Provide a clear and complete question describing the issue you having and any related relevant material.

Best,

GB