iMessage for Android was once just a pipe dream but has since become a reality thanks to a bunch of different solutions. But now, Apple has made it very clear that it doesn’t want iMessage on Android by killing off the Beeper Mini, the first really good implementation of the idea.
In recent years, the idea of iMessage on non-Apple-owned platforms has become a bit less crazy, as Mac server farms have made it possible. However, these platforms have never fully gained trust, as handing over your Apple ID to a third party is an inherently bad idea.
But, on December 5, the Beeper Mini was launched and it really changed the conversation.
Beeper, launched by Pebble founder Eric Migicowski in 2021, originally allowed users to use iMessage on other platforms by logging into their Apple ID on a Mac server farm run by Beeper.
But the Beeper Mini takes the server farm out of the equation.
Using the work of a talented teenager, the Beeper Mini used a method that reverse-engineered iMessage. The app has your Apple ID, phone number, and all your messages delivered directly to Apple. Essentially, it was a “local” iMessage client, and it worked very well. Migicowski was very confident that the app would survive, citing legal protections for apps that reverse-engineer content for the purpose of interoperability, as well as the belief that Beeper’s method of bringing iMessage to Android was beyond Apple’s ability to shut down. The detailed breakdown of how to do everything from Snazzy Labs on YouTube does a great job of explaining why this method is bulletproof.
However, “apparently” is the key word there.
Just a few days later, the Beeper Mini suddenly stopped working for all users, and it has now been officially confirmed that this was due to Apple making a change that turned it off. And in this confirmation (emphasis below), Apple has made it really clear that it doesn’t want this kind of thing to be a thing.
At Apple, we build our products and services with industry-leading privacy and security technologies designed to put users in control of their data and keep personal information safe. We’ve taken steps to protect our users by blocking technologies that exploit fake credentials to access iMessage. These technologies posed significant risks to user security and privacy, including the potential for revealing metadata and enabling spam, spam, and phishing attacks. We will continue to make updates in the future to protect our users.
Although there is a clear privacy and security argument for having iMessage on Android, Apple was within its rights to close the loophole.
The Beeper Mini showed, through iMessage, that Apple’s service has a chink in its armor. For a service that constantly talks about privacy, security, and encryption, the Beeper Mini challenged Apple’s entire offering. Beeper’s Eric Migicowski constantly repeats that the app does not pose a security threat, which seems true, but it is also true that Apple considers the app and its method a security threat.
There’s no world where Apple is going to let this continue indefinitely. At one time or another, the app will be blocked.
However, Bieber seems determined to keep things going. The app was revived just days after Apple killed it off, though with some significant changes including removing phone number support and Apple ID requirements. While this isn’t as good as it used to be, it’s still good to see because, even with a phone number, the Beeper Mini is still the best version of iMessage for Android we’ve seen yet.
Beeper is playing cat and mouse with Apple, who is the mouse.
Apple has made it clear that it will continue to discontinue this application. It’s only a matter of time, probably. Beeper may manage to keep the Beeper Mini going, but at least it seems clear that things will never work the same way as they did at launch, and stability isn’t something I’d ever expect to see. I hope to be proven wrong, but it seems unlikely that Apple will allow this to continue, even as it sees increasing scrutiny around the situation.
As for other iMessage apps for Android, the future is pretty unclear, but it’s not exactly bright either.
Sunbird is still permanently down most likely due to its extremely poor handling of user data. Automattic-owned Texts.com is still up and running as well (although that depends on you own a Mac anyway). Despite facing some issues, Beeper Cloud continues to work as well. Personally, I don’t see Apple really going after the whole server farm or self-hosted bridge angle anyway because those implementations don’t open up questions about Apple’s security. Apple’s side isn’t really being exploited in these cases, it’s the individual user’s choice that carries some potential risk.
But, as far as the existence of iMessage for Android is concerned, it seems that Apple’s quick response to this whole situation has made it clear that Apple does not want iMessage to operate outside of its ecosystem. As much as this is a huge shame, it totally comes true, especially for Apple. So, as much as a native iMessage client for Android makes sense when it comes to user privacy and the prevalence of blue bubble bullying that Apple seems to be doing… WantsIt really seems like this won’t happen unless Apple decides to make it happen, and we all know that’s incredibly unlikely.
At the very least, Apple will embrace RCS next year.
More about messaging:
FTC: We use automatic affiliate links to earn income. more.
iMessage for Android has been a unique and enjoyable experience for many Android users while it lasted. In a world dominated by the iPhone and its exclusive iMessage platform, the ability for Android users to access iMessage through third-party apps provided a rare opportunity to seamlessly connect with friends and family on iOS devices. However, recent developments have indicated that this may not be a long-term solution, leaving many Android users to savor the brief enjoyment of iMessage on their devices.