Got a Mac? How about iPhone or iPad? Apple Watch? Do you use Apple’s Messages-cum-iMessages app? If you do, if you have any or all of Apple’s best hardware gadgets, then you know about Notifications.
Messages might be the one Notification that most of us keep on all the time. Bradley Chambers wants to change Messages.
One of the best parts of iMessage is its seamless integration with SMS. One of the worst parts about iMessage is its reliance on looking like SMS in an app.
Maybe it looks and works the way a text messaging app works– for a reason.
Before digging into all that Chambers finds wrong with Messages– or, iMessages; I’m not sure which is which– let’s remember that it works very well now, definitely sets Apple’s platform as superior to SMS text messages on Android and elsewhere, and Apple has added new features and functions in a layered approach; something new almost every year. Business Messages, Animoji, Memoji, etc.
With nearly a billion Messages or iMessages users, Apple may not want to upset the applecart (pun intended).
Over six years later, iMessage is mostly the same. It’s still heavily tied to the same app that uses SMS
I think that’s what makes Messages so good. It handles standard SMS text messages very well, but works over Wi-Fi, works between devices, and is more customizable than Android’s SMS text messaging app.
Green bubbles vs. blue bubbles.
Apple is promoting screen time on iOS to help us curb technology addiction, I think rethinking iMessage notifications could help a lot.
Yeah, Notifications can be a pain in the patootie, and even with granular controls, the number of apps that vie for our attention seems to increase. Notifications hasn’t kept up with that change.
One of my suggestions is allowing users to mark outgoing messages as not important or “read at some point”. If I want to send someone a text message at 6 AM, I may not want them to see it unless they open their iMessage app.
Maybe they want to see it right away.
A lot of email apps have the capability to “pre-schedule” messages, so it’s possible for Apple to implement the same for iMessage.
That’s different. I use Spark because it has that function– Send Later– built-in.
Another suggestion is for Apple to stop sending alerts if a group thread has more than 3 unread messages.
Except for those people who want the notification alerts. It seems to that needs to be controlled by the recipient, not the sender.
I don’t need to continue to get vibrations or messages past a couple.
Until you forget to check messages and received one that was vitally important– but you missed it because notification alerts were stopped.
Seeing a badge with 100+ unread messages is useless to me. There is no chance I’ll go back and re-read all of them, so I generally don’t care to know.
You need to start checking Messages when you’re ready to read Messages, dude.
This situation is especially true when I am in a movie, out to dinner with my wife, etc. If I feel one alert from a thread and don’t want to check it, I certainly don’t want to get additional alerts.
Hello? Do Not Disturb!
When I am mobile, I’d like to see fewer alerts.
Do. Not. Disturb.
I love iMessage, and I think some minor changes to how notifications work would reduce the potential of being overwhelmed with new message alerts.
None of Chamber’s changes are minor and each one opens up a can of worms for the recipient who may want notification alerts right away.
Send Later is a good idea, though. So is Read Later, which would not dismiss a read message so easily.