I am currently an IOS user, however, as the title suggests, I wish to switch to android. This is because I would prefer to use free software and not be locked into the apple ecosystem. That being said I am already locked into apple and would like to know how anyone else here has managed the switch.
I for one know I will face problems regarding group chats with friends and family on IOS, I will lose out on iCloud+ features, I will have to buy a replacement for my HomePod, I will need to replace apple home, etc.
How did anyone else here who has made such a switch replace or solve these issues?
I have never understood what this green bubble is. I thought it was plainly aesthetic. Now you both tell me Apple deliberately breaks stuff in an infectious way just because an Android user is around. Apple is evil. I will never buy any stuff from them.
That’s because of a difference on protocol (iMessage vs SMS). This wouldn’t matter if they chose to support RCS which is effectively the Android iMessage equivalent and is an open standard (on paper, not necessarily in practice) but that will never happen.
It’s sad that I will never really know about it. Because for some reason they never made Voice compatible with it. I only have 2 people I really text at all, and I use my voice number for everything, not my carrier number. I use the carrier number only for things that won’t accept what they say it’s a voip number. Even though that shouldn’t have anything at all to do with their end of sending a message. I don’t understand why they even check for that. It’s not much of a problem, almost everything uses an app of some kind, I basically only get to see the actual texting app when the pharmacy says my medicine is ready to pick up. Voice number seems to work for pretty much everything else. (and by Voice number, I’m referring to Google Voice if you’re unfamiliar)
I know, and it drives me nuts when iPhone users complain that it’s my fault for owning an android phone. Like um no it’s quite literally your fault if you stick with Apple and defend their decision to make your life worse. Apple’s business model is basically Stockholm syndrome.
The crazy thing is that RCS is entirely compatible with Apple. If they would refuse to develop for it and lock down their App store to keep 3rd party developers from making apps for it themselves
RCS is not completely compatible. For one thing, it requires a carrier and a phone number. You can go out today, buy a Mac or an iPad with no cell modem, and start using iMessage purely as an IP messaging app. So they can’t just replace the existing protocol with RCS, because RCS is a bag of flaming shit. They could spend the money to develop RCS fallback in addition to their protocol, and that would be awesome, but it costs them money, and I get why they don’t want to do it.
The reality is that this is Google’s fault more than anything. They spent half of my adult life repeatedly inventing and then fucking up the act of sending 200 bytes of text to one person at a time.
I’d love for the modern world to have a great way of messaging people that just worked – used IP connections with SMS fallback, a login you could manage from anywhere, full support for all the real-time typing stuff, the rich media support, the whole thing. That would be great. Someone get on that. But if I have to listen to fucking Google whine about it one more time, I’m out. They’re like a guy with one finger left. If you didn’t know any better, you’d feel pretty sympathetic for him. But if you’ve spent the past two watching him slowly chop the other nine off one at a time with a hatchet and then whine about his bad luck for 12 hours after each chop, the sympathy starts to ebb a bit.
They’re not deliberately breaking it – they just don’t support it. “Deliberately breaking” has the connotation that it would have worked just fine, except they took some extra action to stop it. That’s not true here. It would only work the way people want it to work if Apple spent a lot of money paying developers to make it work.
They’re one of the most profitable companies around, I think they can hire a couple devs to fix those major issues, it just doesn’t help them (it helps their customers) so they dont.
If they chose to support it there wouldn’t be any need to buy an iPhone to stop the issue, they want a monopoly and this is a perfect example of the anti-consumer practices they’re willing to sink to in order to facilitate that.
I’ve wrote some lines of code and I know when it’s “just being lazy” or doing stuff “the evil way”. Imagine when Apple accidentally restricted join/leave actions in their native chat client. That would be minutes until they fix it. We are talking about years here…
Sure, but one of those things is fixing a bug in the protocol they already use for core functionality, and the other is an entirely new software development project. Adding RCS support to iMessage is adding support for an entirely new protocol. That’s what I’m getting at here. It’s not “broken”. Apple doesn’t have to “fix” RCS support. They have to build RCS support, from scratch.
This is like saying that Microsoft Windows should be able to run programs compiled for Apple Silicon on Mac OS. That might be a cool feature, and I have no problem with someone saying they think it should happen, but it’s not Microsoft being “evil” or refusing to “fix it”.
Modern programming requires a common code base and portability. Otherwise Microsoft would never be able to provide Office for macs.
Apple knows it, they simply don’t care to compile it. Protocols are easy to support. It’s a matter of parsing, encoding and decoding.
Two points here. First, Microsoft has 220,000 employees. They absolutely could support two completely separate sets of Office apps if they want to, and in fact they did exactly that until 2018. They could support 200 separate code bases if they wanted to. Second, at best you have provided evidence that Microsoft uses some common code for Office, and that evidence is just that Office for Mac exists. iMessage for Android doesn’t exist, so there’s no such evidence. If I have a million line Windows app that I wish I could make available natively on Linux, but it’s all Win32 from top to bottom, you obviously can’t tell me that “all modern software requires a common code base and portability” therefore I could easily do it. My code base isn’t common or portable, so what Microsoft did doesn’t help me any.
But beyond all that, you’ve just papered over a vast amount of complexity by just declaring it doesn’t exist. Most portable apps today are web apps. You can write Electron and it’ll probably run on just about any platform. You could write Java and it’ll mostly run on any platform. But none of Apple’s stuff is either of those things. iMessage is a UIKit app, probably with a boatload of Objective-C behind the scenes and maybe some Swift for the more modern parts. It runs on Macs because of Catalyst, which is emulates the iPad version of UIKit on the Mac. But that’s it. There’s no UIKit for Android. iMessage simply isn’t portable, as far as any of us know. It’s just factually nowhere close to true to say “Apple just needs to compile it”. The frameworks it’s based off of just aren’t there. It’s exactly like saying that Adobe just needs to compile Photoshop as a KDE app. Photoshop doesn’t use Qt or the KDE libraries to do anything. The code just isn’t portable. (Full disclosure I guess, I have no idea if Photoshop uses Qt or not, but it’s a reasonable illustrative example).
And supporting a protocol isn’t just parsing, encoding, and decoding. HTTP is a protocol. So is IMAP. But you can’t just write a web browser that uses IMAP. The concepts don’t map 1-1 to each other. It’s not like for every HTTP action, there’s a matching IMAP action. You can’t just say, “I’ll just use FETCH instead of GET and everything will be great”. HTTP has redirects, for example. How are you going to make redirects work over IMAP? In the case of iMessage vs RCS, for example, iMessage has the ability to message someone without a phone number. RCS doesn’t. There’s literally nothing in the RCS protocol that makes that possible. So what do you want this mythical compiler to do when you tell it to compile iMessage for Android and use RCS? Should it just core dump if you try to message an email address?
We’re talking about basic chat functions that reportedly don’t work like joining and leaving a chat. How does that break for everyone when there is one Android user around?
I’ve wrote enough code that other devs have ported to machines I couldn’t even think about. If Apple is not able to that I don’t know what they do. There is nothing mythical about supporting phone numbers when you implement that and if you leave out that for Android it still does not justificate to obviously break unrelated functions. No one in the world would develop like this.
Apple is breaking compatibility deliberately. They are well-known to do this for hardware and for software.
It’s software…these are computable problems, and we can solve them with Turing machines. No one is saying Apple is incapable of porting them. I’m saying that it’s work to port them. It’s nowhere near just clicking the compile button in Xcode and having it spit out a binary that speaks RCS or runs natively on Android or whatever. That is work for human programmers to sit down at blank editor windows and start building. Can they do that work? Again, obviously, yes they can.
Someone could sit down and make Vim interpret my .emacs file. It’s software. Emacs isn’t magic, and the Vim programmers aren’t stupid. We could make this happen if we wanted to. But it’s foolish to say that because it doesn’t work today that “Vim is deliberately breaking Emacs compatibility”.
If you can’t join or leave a chat, that’s a bug and they should address it. But that’s different than the whole “blue/green bubbles” conversation where people complain about terrible MMS quality and limitations on group chats and all that stuff. Those things happen because Apple currently speaks two protocols: SMS/MMS as a fallback and the iMessage IP protocol as a primary. To solve those problems cross platforms requires a third protocol (RCS), and that’s firmly back in “why doesn’t Vim interpret my .emacs file” territory.
Please don’t mix everything up. We’re still talking about the same software on different platforms from one single vendor. Apple won’t fix it to avoid competition and try to convince people that Android is bad instead of their very own program.