I'm deep into the Apple ecosystem and don't see myself getting out anytime soon. But I think their stance on iMessage sucks, even while understanding the strategic reasons they're doing it.
I don't see this as "leeching off an undocumented API" as much as demonstrating that iMessage is already in a state that allows 3rd parties to interact with it, documented or not. Every time Beeper starts working again, it shines a light on the fact that iMessage was never so locked down to begin with. It also puts pressure on Apple to answer the growing # of their own customers who are frustrated by the limits. These are good things, IMO.
Apple may have every right, but that doesn't make their stance good for the ecosystem or good for consumers. This is pretty clearly about forcing people to switch ecosystems and not about security. If security was the only issue, Apple could easily provide supported iMessage APIs that make it clear that the other user is not a verified Apple user, while still allowing interoperability.
The market simply chosing a preference is not anti-competive. iPhone and iMessage is able to compete on it's own merits without competition being artificially hindered.
I truly do not understand the reasoning behind this. A product doesn’t need to be popular world-wide for behavior to be anti-competitive. The reality is that the US market is heavily impacted, and the fact that this isn’t true in other geos has nothing to do with the impact here.
> Apple is under no obligation to make an Android app, and it's silly to pretend not making an app for another platform is somehow anti-competetive.
I think that framing this only as an obligation for Apple to make an android app is unnecessarily narrow.
There are many ways this could be solved:
- By not artificially degrading the non-iMessage experience
- By not want until 2024 to implement support for RCS
- By opening up APIs with appropriate restrictions to be consumed by other apps - the thing they do for most other native phone capabilities
Building a first party app is just one of a large number of possibilities that are less broken than the status quo.
RCS will help this. They’re embarrassingly and/or intentionally late to the party.
The answer isn't to say that in other locations we have a different gatekeeper so all is well, the answer should be that Apple's gatekeeping should be broken, and then other gatekeepers' gatekeeping should be broken too.
We should all have one messaging client that can seamlessly use all the major protocols and services - in fact like we used to have over a decade ago.
> why should we intentionally restrict that ability
I don't believe software and hardware companies should be under obligation to support things they don't want to. Users can decide on whether the products meet their needs and decide whether they work for them or not.
Apple made the decision to blend iMessage seamlessly into the phone’s default messaging experience, and with the power of that default, they’ve weaponized the intentional interoperability failure.
Should they be under some obligation to support things they don’t want to? As a product manager, I say that depends on what their customers want out of the devices they’re buying. Apple does owe their users something here, and it’s reasonable to expect that a new device purchased in 2023 is capable of sending a quality photo to other devices. Regardless of obligation, I also think they deserve every bit of anger and bad press they get for the way they’ve played this.
It’s smart business, but that’s not the same thing as good for consumers.
Nobody is asking them to support anything though - Beeper developed their client on their own and isn't asking Apple anything. Apple is in fact spending extra resources to break interoperability, where as they could just do nothing.
It's just worse than the alternative that Apple provides for its own ecosystem of users. Any Apple user is free to opt for that more universal system if they want.
Why not use the more modern, featureful & secure option instead of antiquated SMS? Why are you still defending corporate greed at the expense of user experience?
FWIW there was an era where I felt differently. I was very active in the early Android jailbreak community. It was fun and the freedom has benefits, but those are benefits that I've deliberately chosen to give up for the benefits of the other end of the spectrum. I wasn't tricked into giving them up and neither was anyone else: people are paying Apple for the experience Apple is trusted to deliver. The reason people trust them is because they deliver it. It's super simple.
> I care about having a great experience using my own mobile device.
But you can still do that - I don't see how Beeper changes that? As a happy Apple user you don't need to use Beeper, though might still get benefit from it if your Android-using friends can now use the same messaging app you do.
How does Apple abuse this power in the US but not EU with no differences in the product?
This is a very one-sided framing of the situation and leaves out quite a few factors.
People aren’t just buying Apple products because they like them. They’re being forced to buy Apple products to stay in the “in” group. They face exclusion by peers due to Apple’s dominance in the geo and in certain demographics.
As I understand it, iMessage is not dominant in the EU, so the market conditions are quite unlike each other.
So, uh, factors that have zero to do with Apple are evidence that it is… abusing… the… market…?
Are you auditioning for Apples’ defence team or something?
How does this have zero to do with Apple? It has everything to do with Apple, because it’s ultimately their product decisions driving user behavior.
Had they implemented support for RCS by now, this conversation wouldn’t be happening. They made the explicit choice to capitalize on their poor interoperability and decided to claim it’s for security reasons, which is pretty obviously bullshit.
What chat apps using a centralized server owned by a single company have open APIs that let anyone use them?
- iMessage isn’t a chat app. It’s the default experience for sending the equivalent of text messages from the Apple ecosystem. They’ve blended the experiences such that it’s not fair to compare it to a traditional chat app
- 3rd party chat apps are cross platform. The only reason Beeper exists is because there is no first party option to interact with iMessage chats outside of the ecosystem. This is not the case for actual “chat apps”, and the non-existence of APIs takes on lesser relevance
- 3rd party chat apps are cross platform because they're funded by alternative methods, usually by selling your personal information, though sometimes also by sales of other products within the app (like on LINE). Apple funds its chat app through phone sales.
Keep in mind, iMessage also relies on a server component. It's not some peer-to-peer protocol. Apple has to pay for the costs of sending messages, high resolution videos and photos, audio recordings, and supporting iMessage apps[1]. You can argue that this is included in the price of the iPhone/iPad/Mac but obviously is not for random android devices. Personally it doesn't bother me if Apple has to just eat the costs, but it is a cost, and probably a not insubstantial one.
[0] Social Engineering.
[1] Ok how many people actually use these? Still, they are part of iMessage.
Them taking the fight with Apple should be applauded. A walled down proprietary message platform only a few can use is stupid to fight in favor of.
The original kid who reversed: Great hacking, I think we can all applaud. This is a for-profit (VC funded?) company charging users by piggy backing off of servers they don’t own or pay for (and using apple binary blobs?).
If they used the protocol they reverse engineered on their own servers that’d be completely different. But that wouldn’t be profitable for them.
Apple is free to charge for them. In fact, I think it would be the best outcome and a mitigation to the upcoming spam onslaught now that the protocol has been documented.
> But that wouldn’t be profitable for them.
Is it a problem to profit off creating a tool that some other manufacturer intentionally doesn't want to create (since Apple is more than capable of building an Android iMessage client)? Isn't that the whole point of a competitive market?
But I don’t think anyone disagrees that Apple is (currently) free _not_ to charge for them.
> Is it a problem to profit off creating a tool that some other manufacturer intentionally doesn't want to create
I’d say ethically no - not a problem - up _until_ the point where they are actively, continuously using resources of that manufacturer. Legally? If you or your customers have agreed to a TOS then that’s probably bad either way.
Nobody would care about (or be interested in) beeper if they were running their own servers.
It was really cool news when they reverse engineered the API. It was less cool when they sold paid access to this unofficial API. Beeper is barely pro-consumer because again, they’re charging for something open sourced by a 16yo kid which has no official support.
The green bubble blue bubble story is really tired. Yea it’s real, but it’s not a technical problem it’s a social problem. Haven’t we learned that you can’t out-hacker a social problem?
It's both. For example, Apple degrades the experience for "green bubbles" even though it doesn't need to. That's not, strictly speaking, a social problem.
E.g. MMS messages generally have to fit within 300-600KB so they are horribly, horribly compressed. https://m.gsmarena.com/glossary.php3?term=mms
As for beeper cloud, I’m a paying customer to Apple and I just want to use my damn chat app on desktop that I pay for.
Put a tiny flat rate on the app for the work that they crated and call it a day.
>> "only a few can use"
There are about 1.5 billion iPhone users in the world.
As far as proprietary services, the world is full of them. Google, Meta, X, Instagram, .... Apple built a service to provide advanced messaging services to their many customers. It comes with the phone. Should Apple be required to freely give iPhone cameras to people who don't buy their phone? How about the Touch ID module?
There are plenty of cross platform messaging apps available on iOS. The only thing that could be considered anti-competitive is the inability to change the default messaging app on iOS. Apple has fixed this for some of the other built-in apps, but not messaging yet. I would agree that that should be fixed. However, Beeper is not offering an alternative messaging platform, they are selling access to Apple's platform.
In what world is Apple obligated to keep a service running which allows unauthorized security related behavior? Such a hole in a service is usually called a security vulnerability and is patched away asap.
The inherent problem right now is that they want to create a commercial product using another company's servers/APIs without that company's permission, ultimately leaving Apple picking up the bill (inc. additional support ticket volume, like when iMessage gets locked on a given AppleId).
Is iMessage part of Apple's moat? Absolutely. Is it good for consumers for iMessage to have a hardware lock? No. But even if that is true, this seems like something regulators should be involved in solving.
Plus there is nothing anti-proprietary or pro-freedom that Beeper Mini is doing.
It never has and never will be a ‘free spirited hacker place’ despite the name.
IMessage is a much much much better experience. It's not at all bad for their customers. It's a huge plus of that system over Android and other platforms that still try to piggyback off SMS or haphazardly support RCS.
[0]: https://olvid.io
I bought into the ecosystem exactly because of the quality and functionality of iMessage. There's absolutely no spam, everything works and the ecosystem is tight-knit.
I’m glad I bought into the ecosystem for other reasons, as I definitely receive occasional iMessage spam. It’s about as frequent as WhatsApp spam.
I am then forced to use some $app, persuade my contacts to use said app. Defeating the point of iMessage when I just want native support all around.
Something that Apple had never implemented anywhere else and for which it could decades ago.
I wouldn't switch to an Android because the feature became available.
If all your contacts use Apple Devices, sure go nuts. But when others don't iMessage becomes unpractical.
But hey, vendor device lock-in money is very nice. It's unfortunate that they don't water the lawns of the walled-garden nor restock the bird feeder. We are expected to do that ourselves using a wooden ladder with missing prongs.
(This is one of the reasons why WhatsApp is big in the rest of the world)
I guess the approach is to try and force Apple's hand or push some legislation for interoperability, but Apple is working on RCS so it's not like they've been completely ignoring criticism...
There are still disparities, though, that should be presented. There's no standardized end-to-end encryption yet for RCS (although it could be argued Google's protocol is a de facto standard), and Apple has indicated it will be implementing RCS as the standard dictates, i.e. with no E2E encryption. Using blue bubble to indicate E2E encrypted and green to indicate otherwise is a reasonable UX choice.
After Apple implements E2E encryption over RCS via whatever standard (which can be reasonably inferred as their intention from their announcements), if the delineation for green-vs-blue is still iMessage/not-iMessage (rather than E2E vs not-E2E), then I think "meaningless" applies. But we're not there yet.
A smartphone is essential. Apple and Google tax 30%, control when and how software can be deployed, control browser tech (Apple), prevent web downloads of executable software (Apple) or scare and confuse you about it (Google). They control the payment rails and increasingly enforce using their identity and customer management, so they can sink more claws into business and innovation. They're partnering with governments to be authoritative identify providers. They're usurping payment rails to become the entire payment ecosystem of the future.
The devices are user unfriendly. Can't repair them, can't use third party components, can't replace the battery. Unofficial pieces break core features due to unnecessary cryptographic locks. Updates obsolete old hardware.
Nevermind the petty bullshit about green and blue bubbles giving children (and even adults) fear about their image and reputation. Being bullied for not buying the latest and greatest.
This is scary shit and we're letting them do this.
Nevermind all the fluff of them owning movie studios and music and the arts to keep eyeballs locked.
Car companies wish they had it this good. They'd love to charge you for third party accessories, or to charge McDonalds a fee every time they drive you there. That's essentially the deal Apple and Google are getting.
This is all at once worse than Standard Oil, and comes with heavy Orwellian vibes.
We need more than two vendors, and we need different companies to own different parts of the stack. As it stands, these two companies own everyone and everything these people touch.
I want to add a subtle but important part: outside of the tech community, almost nobody knows this problem exists. If you try to explain it their eyes glaze over. Normies with iPhones, if they think anything, think iMessage is "texting". Blue bubbles mean they can see when you're typing and can send reactions, green bubbles mean you can't because you're on Android (or, "Samsung"). None of them think of iMessage as a "chat application" on par with WhatsApp... it's texting.
And all the government officials we wish would step in are included in this lot. They all have iPhones and they love them. iPhone is synonymous with 'smartphone' in common discourse and Apple is happy to trade brand dilution for that kind of "default" brand status.
And, as you eloquently point out, we could break the world trying to loosen Apple's grip on texting, only to find that we just transferred some of their power to Google, which isn't much better.
Apple doesn't charge for iMessage, and instead that service is funded by device purchases. Beeper is charging people who haven't purchased devices to help them parasitize the infrastructure of the service, and instead of contributing to Apple's operational expenses, they're pocketing the money.
There's no scenario where this stands, even if iMessage came to non-Apple devices Apple is probably going to charge users if they're not buying Apple devices (I can't imagine it being an ad-driven service).
Of course, Apple is welcome to start charging a reasonable fee for the service.
"I'm only stealing fractions of pennies at a time! That's why it's not stealing!"
Do you have numbers for that? Sure, some of the users haven't purchased devices, but many of them have an apple device or two and just want access to the network across all the devices they use.
They’re highlighting the closed nature of Apple’s messaging system more effectively than anyone has in a long time. I support them in doing that.
https://arstechnica.com/gadgets/2023/11/google-argues-imessa...
I imagine Beeper is providing exhibits A and B for any such court case, should it happen. And they get some good brand publicity along the way.
Every major chat app is closed though? For example, I use LINE regularly, there's no way to access that chat system through anything but LINE apps.
Then don't use Beeper.
> I trust an established, trillion dollar company far more with that sensitive info than I do a fast-moving, eager-to-break-things startup. And the list goes on.
Thankfully, you don't necessarily have to trust them since the entire process runs on your device.
> I really don't believe they're entitled to parasite off the undocumented iMessage API.
Do you also believe it's "parasitism" for a tool manufacturer to create a screwdriver that fits another manufacturer's screw shapes? That's more or less exactly what's happening here - they made a tool that fits the existing proprietary API and interacts with it.
And stupid analogies help nobody. Which part of your screwdriver is costing the original manufacturer money every time you turn a screw?
The true cost is so insignificant as to not matter. The normal iOS push notification spam uses orders of magnitude more resources than whatever Beeper uses, and yet Apple doesn't seem to mind those.
The screwdriver would cost a lot to a screw company that based its business model on being the only seller of compatible screwdrivers though, and that's why Apple is mad about this and trying to break it.
If I sold internet off that wireless router and the next OSP tech that gets into that POP (rightfully) unplugs it, why should I have any right to call my ISP and chew them out because people gave me money for that internet access?
Beeper Mini is not "unlocking" anything more than a real iPhone does. It's not exploiting anything, it's following exactly the same protocol and registration flow as the real thing (that's why it works in the first place). No security is being broken here.
You could argue that it's using an (insignificant) amount of resources on Apple's side without having paid for it (since most users wouldn't have purchased an iOS device), but Apple can trivially mitigate that by offering an officially-supported registration flow that charges a reasonable fee.
Beeper isn't "blaming" Apple for being Apple. They're saying that Apple is full of shit when they claim that Beeper hurts the security and privacy of their users.
You mean like SMS and MMS right now, and RCS next year? https://9to5mac.com/2023/11/16/apple-rcs-coming-to-iphone/
This isn't to say there aren't toxic cliques whose alpha-teen leaders insist on certain brands of phones, clothing, ebikes, etc., but just that the flames of this particular media panic are actively fanned by Google and Samsung PR.
To me, this provides an excellent argument for using Android devices if you are single and looking to start a long term relationship. Through one tiny choice, you get some of the most elitist, opinionated, and disagreeable people to voluntarily exclude themselves as potential dates, with no hard feelings on either side. It's a far better filter than most stuff you could put in a dating profile.
This candy fell into the mud. Therefore I will never eat candy again because they are all muddy.
They can blame whomever they want, what difference does it really make.
> For one, I do not want to have my Apple ID login routed through a third party.
As long as you don't use the service, then you're fine. I don't see why you should even care if other people want to use this service.
Sort of like how Apple builds their apps?
There are some very weird takes around security on this to somehow twist it into an "Apple good" scenario. No, like literally every other time in history, closed & controlled does not make it more secure.
To my knowledge, you can't make a 3rd party Signal client and connect it to the official Signal instances.
The Signal guy doesn't want you to do that (just like Apple), but it's absolutely possible. It's in fact much easier than in the iMessage scenario since all the client sources are available.
In fact, can't I not just create an new Apple ID specifically for this?
Edit: Should have read this new post more closely. They are now requiring an Apple ID, when they weren't before.
I don't buy their "Beeper unequivocally makes things secure story" either. For one, I do not want to have my Apple ID login routed through a third party. I trust an established, trillion dollar company far more with that sensitive info than I do a fast-moving, eager-to-break-things startup. And the list goes on.
It's an impressive engineering effort, but I really don't believe they're entitled to parasite off the undocumented iMessage API.
[1]: https://news.ycombinator.com/item?id=38574888