In my case I don't care for the green/blue bubble divide, EXCEPT that I have a limited SMS plan and every time someone messages me it potentially costs me $0.10. That is not that significant until someone sends a series of short messages that could have been bundled into one, and I can't help but think "this person just cost me the price of a coffee".

It's not even Apple's fault, but rather AT&T's confusing and expensive billing options. I could also upgrade to an unlimited messaging plan, but 90% of the billing cycles I'd be overpaying.

Check out some MVNO's such as Red Pocket Mobile, or US Mobile. If you don't have heavy data usage, plans can be extremely cheap.

Thanks for the tip. I'm looking at it right now. I feel like such a fool :).

We switched from AT&T to T-Mobile years ago and have had a great experience.

They added a data plan to my bill when I bought my first iPhone... it wasn't the $10 a month, it was the disrespectfulness of "you can't, we're forcing you to".

Switched to T-Mobile that same week.

There are many popular messaging applications(Signal/Telegram/WhatsApp) that are cross platform and handle multimedia content well. This is what is used outside of the US.

I'm very aware of that.

Convincing an entire extended family to switch app is not simple. Making sure they are all set up with an alternative messaging app is not simple. Getting them to remember to use it with your specific chat while they use the default app for other conversations is not simple. Using an iPhone is simple.

There are, but... Incoming rant:

The one big thing about iMessage is that it never really changes. And it cannot be hijacked by some other application like on Android. For better or worse, and for basic services like text messages I'm erring on the side of better. I have no idea how many times I had to go fix messaging issues when my grandparents were using Android. Facebook tried to take over all messaging. Then it was Google, with whatever iteration of failed messaging application they were pushing out. Or when they had phones that actually received updates it would suddenly drastically change the user interface.

We're having weekly video calls on FaceTime, and the superior sound quality of a FaceTime Audio has made it possible to even have a phone call with my hard of hearing grandpa. They don't even know they're using it. I send them high resolution pictures and videos of my hikes, that they can enjoy on their iPhone or iPad, whenever they want. Pictures and videos stay there without them having to do a ton of complicated tasks in a forever changing user interface, like Snap and the likes. The Apple Watches lets them know when someone is calling, and it gives us peace of mind knowing that they always have it with them. Everything uses a format they're used to from long before smart phones was a thing: Phone numbers. My grandmother is writing her life story on her now 7 years old MacBook Air. All their devices are backed up to my iCloud-family subscription. We've started using AirPods with Live Listen to include my grandpa in our conversation when I'm visiting them. If you haven't tried this, you should. It's mind boggling good.

The amount of time spent fixing things for them have gone from an almost weekly thing to non-existing. Being seniors they also have a lot of time on their hands, and Apple-partnered stores, at least around here, provide excellent support for anyone that owns an Apple device, regardless of where it was bought. All their devices are updated almost effortlessly: They get a notification about a pending update that tells them exactly when the device will be updated and what they need to do. The one big wish I have would be to postpone major updates for a couple of months. The recent trend of Apple radically changing the user experience is not a welcoming trend.

There's a lot of things I've really started to hate with Apple. And to be honest, at this point the things I just listed are more or less the only things holding me back. But the things mentioned in this post is such a huge quality of life improvements for all of us, almost like a cliché of Apple advertising. It's almost embarrassing.

Exactly this, I spent 5 years of monthly calls with my mom over the course of 4 Android (admittedly very cheap) phones. Just basic stuff like sending pictures, why so and so didn’t get her text, etc.

Three years ago she got an iPad and it’s zero support calls with way more communication.

So while I suppose it is possible to have a non-horrible text experience on Android, I’ve only succeeded on iOS.

They don't. Whatsapp degrades image/video quality massively. Just a choice they made given that a lot of their customers are bandwidth constrained. If I have to send a photo that I took with my high quality phone camera, I prefer to use iMessage.

> Sharing a video via group MMS is fraught with problems, it often doesn't work, or the resolution is garbage.

FYI, this is carrier related. Many carriers have a hard limit on how big attachments are, and will silently reject them if you go over that limit.

What the limit is varies based on the carrier, but it seems that a "safe" limit is ~1.1 MB (This is the hard limit that Android enforces for the largest MMS attachment it allows). T-Mobile seems to allow higher (I think I got up to 10 MB?), but I do not know what would happen if you sent an MMS to another carrier that is that big (they probably silenty drop it).

So you have two options: either reduce how big it is (which Android Messaging silently does), or flat our reject it. So the video is problem is silently reencoded to accomedate the 1.1 MB limit.

Why doesn't this happen on iMessage? Probably because you can set your MMSC (the Server that sends/recieves MMS) to Apple's MMSC, so you can standardise how big it is.

> Why doesn't this happen on iMessage?

Because iMessage is not MMS - it uses a custom protocol and works completely independently from the carriers.

Fair enough, I admittedly haven't looked the iMessage protocol so I don't know much about it.

I just know that if you have an iPhone, you have to set your MMSC to Apple's servers versus the carrier's servers.

> I just know that if you have an iPhone, you have to set your MMSC to Apple's servers versus the carrier's servers.

I don't believe this is true. To the best of my knowledge (and a quick Google) Apple has no MMSC servers. I've certainly never input any.

SMS and MMS sent on iOS use the same servers an Android phone would. But when the target phone number is detected as being iMessage capable that whole system is ignored and iMessage is used instead.

Fair enough. For a day or so I was looking up if I could somehow emulate iMessage on a Pinephone, and I remember a lot of it being a non-starter unless you had an iPhone. It stuck out to me that Apple had their own MMSC for some reason. But perhaps it is old news or I read the wrong post?

On an iphone, when you send a text message, apple will take a look at the phone number you're sending it to and check if it's linked to an imessage account. If it's linked to an imessage account, you're not sending a text anymore, you're using an internet service just like whatsapp.

There is no technical relationship between SMS and imessage, but to the user it's the same interface

The video messaging being garbage is a huge downside. I have to resort to facebook messenger to get a copy to my whole family.

The actual color of the messages really isn't the problem.