On the other hand, console generations often provide a hard cut-off for compatibility. You can’t always use previous gen accessories with a new console, and those accessories are usually only comparable with that console. I can’t play my Wii games on my switch, nor use the controllers and other accessories. This is kind of inherent to consoles in that they’re meant to be a consistent platform that allows developers to maximize performance by knowing that each console is going to be pretty much the same. With iOS though the software evolved from the idea of desktop software that runs on a variety of devices. Developers develop with the idea that their software will be used on devices with differing hardware and performance. It’s a completely different paradigm. With computers, people expect that the one they buy this year will be better than the one available last year, but they also don’t feel the need to buy every revision(aside specific performance heavy use cases), they decide on their own replacement schedule. That’s the paradigm that the iPhone came from, regular iterations, occasional major revisions, and long term support/backwards compatibility with previous models and accessories.
This is what I was going to say. It’s good to know if a message chain is going over Apples E2E encryption or regular SMS that’s completely transparent to the carrier. There’s also a fundamental technological difference that allows group messages over iMessage, but not over SMS. iOS 18 supporting RCS helps a lot, but I still think it’s a good idea to have an easy way to differentiate iMessages vs RCS vs SMS due to security and functional differences.