upvote
> It's not as if Apple doesn't have the money to dedicate a team to matching the EU's requirements on a deadline. They just choose not to.

Exactly, that's actually why I LIKE this decision so much. I'm not on Apple's side, but I REALLY like the idea that a company just says, "Fine, we'll comply by not even offering this product." It's a perfectly legitimate choice, and it FORCED Apple to evaluate the pros and cons.

I want more companies to not get exemptions and thus not offer law-breaking products. I LIKE that the government is saying, "fix it or don't bring it here" and Apple just has to live with it. I like that Apple also is refusing to just bend over to the EU. We need more of these types of conflicts so we can work out good regulations, and not just always bend over and take it from whatever party won.

While I like a lot of Euro regulations, some of the privacy ones go too far with the whole "we're going to enforce this on the whole world" crap. I like California's method of "to sell it here you have to have this but we're not going to sue you for selling a noncompliant product elsewhere."

reply
Yes, exactly! Also forced EU voters to consider how much they value these services, and whether the regulations are worth it not to have them, or to have watered down versions of them. I say this without judgment - I see it as a legitimate area of consideration.

I think the worst is hugely impactful laws for which exceptions are constantly carved out so nobody can truly evaluate whether the law/reg is a good one or not.

reply
> Also forced EU voters to consider how much they value these services

It's been a while since I left Europe, and I'm rusty on that particular layer of civics. Do EU voters actually have a say in this kind of regulation? Or is it all decided on the executive side which is only accountable to member states and not to individual citizens?

reply
They do have a say. They can elect representatives who could change the legal framework and the incentives for the bureaucrats. Then these regulations would not get passed and that would be that.
reply
None. The EU is getting more and more un democratic by the year. More power centralized in the bureaucracy vis regulations and other mechanisms.
reply
EU "voters" don't get a say in any of this.
reply
I value them a lot, happy that the EU didnt bend down to Apple.

If it werent for the EU, the companies would get away with all sorts of shit.

Is as if people forget companies are evil by nature and will fuck you any chance they get.

reply
Meanwhile: EU pushing to snoop on private chats and US companies are pushing back.
reply
Where do you think that lobbying money is coming from?
reply
I'm curios what kind of shit specifically DMCA protects you from?
reply
I think you mean DMA, not DMCA. DMCA mostly protects copyright holders. DMA is about protecting users and competitors from platform lock-in. Bending for Apple would just make that lock-in harder to challenge.
reply
DMCA provides some rather important protection for service providers (including small-scale services like web forums, not just ISPs and web hosts) - it makes them not liable for copyright violations by their users, so long as they take down infringing content upon receipt of a DMCA notice.

But I agree, that's probably not what OP meant.

reply
deleted
reply
"Let's discuss how countries should bend their knee before supranational corporations"
reply
And as a consumer, I am somewhat happy that a company says "well, then not" if it cannot comply with the law.

If the law makes sense, that I cannot judge in this case.

reply
You should remember that according to a court testimony the whole European area (which goes beyond EU) gives Apple 7% of their revenue, whereas breaking DMCA may incur penalties of ups to 10% of global turnover.

Those numbers make withholding "risky" products a no-brainer strategy. Also, those numbers put a hard limit of how much Apple will want reevaluate their general strategy of tightly integrated first-party software.

reply
Which court testimony are you talking about? A quick google search suggests that Europe is responsible for roughly 25% of their revenue.

Edit: 26% of their net sales comes from Europe for Q1: https://www.apple.com/newsroom/pdfs/fy2026-q1/FY26_Q1_Consol...

reply
there's a difficulty in evaluating how much goes into Apple revenue because Apple mixes Europe (not just EU) and Middle East.

The 7% probably comes from a Daring Fireball article, based on misunderstanding some Apple communications, and which Gruber later had to backtrack

https://medium.com/luminasticity/when-smart-people-cant-reas...

reply
Yes, I was coming from Gruber's article, thank you for correcting me!
reply
[dead]
reply
Google eng mgr here. I've worked on a few projects related to compliance with various government policies. This isn't "assign a two-pizza team to it, will be done in a quarter"; these types of compliance efforts can mean completely redoing multiple core systems to handle privacy, wipeout, audit, reporting, per-location policies, etc etc. These efforts can involve hundreds to thousands of people for multiple years.

Sure, there's a messaging component to this. However, any company that isn't trying to just skirt the law will aim to do this sort of thing correctly, and it's an enormous effort.

reply
To me that reads as an even greater reason not to delay it. If you knew the restrictions day one you’d be able to engineer the system to accommodate them. Waiting until post launch now means a massive amount of re-engineering.

I know it’s not quite as simple as that but I do think it shows Apple are more interested in blaming the EU than reducing the potential issues ahead of time.

reply
> If you knew the restrictions day one you’d be able to engineer the system to accommodate them

This slows down deploying the system globally. Particularly if the target is moving, it may make sense to build lightly so one can pivot, and then build in the compliance stuff after you know you have a winning configuration.

The EU has its laws. Apple has its strategy. The only thing I fault anyone on is the public bickering.

reply
If Apple is so pro-privacy like they claim, then they'd look for the most strict international privacy laws and abide by them. Then they could feel safe in knowing they could release the product anywhere. The fact they want to make the product available under the "rules" of the least privacy protecting countries first says a lot to me
reply
DMA is a not a privacy-oriented law.
reply
But Apple’s excuse not to comply with it is privacy-related.
reply
How does that reflect poorly (or positively) on their privacy chops? The dispute is about a competition law, a law Apple is complying with by withholding this feature.
reply
> If Apple is so pro-privacy like they claim, then they'd look for the most strict international privacy laws and abide by them. Then they could feel safe in knowing they could release the product anywhere.

Those are not equivalent statements. You're assuming that privacy is a one-dimensional quantity, so that anything that complies with "the strictest international privacy laws" automatically also complies with any other privacy laws. But this is not actually true. It can easily be the case that every national law allows some set of behavior (different sets for different legal systems), at the same time that the intersection of all those sets is empty.

reply
DMA is about competition, not privacy. Apple weren’t requesting a GDPR waiver.
reply
Apple's concern is at the intersection of DMA and privacy. Apple is worried that other parties having the same level of data access that Apple has today would create privacy issues. This is because Apple's current privacy posture is "Trust Apple with your data" rather than "Trust no one with your data - including Apple", but that would be less profitable, but would have prevented the request for an exception because Apple would be on an equal footing with everyone else, if all they could see was client-encrypted data indistinguishable from random bytes.
reply
> This is because Apple's current privacy posture is "Trust Apple with your data" rather than "Trust no one with your data - including Apple"

I think that's uncharitable. Apple prefers not to have the data either, hence the preference for on-device processing.

reply
> Apple is worried that other parties having the same level of access that Apple has today would create privacy issues

But this is solvable. The problem is the work it takes to solve it isn’t worth the hit to time to market. (And possibly even the cost.)

reply
So Apple doesn't want to compete? Cry me a river.

I could almost feel sympathy if it were something to do with some contract that Apple signed with their AI provider. Who's that, Google?

Ahh, a "competitor"? Yeah... cry me a river.

reply
> This slows down deploying the system globally. Particularly if the target is moving, it may make sense to build lightly so one can pivot, and then build in the compliance stuff after you know you have a winning configuration

This kind of approach is how startups justify everything, however for established companies this would be backward.

I get a feeling that Apple never wanted to do it. They already knew the compliance requirements existed and if they would have wanted to test things then the narrative could have that they are rolling out in other markets first and would roll out with compliance in EU later. Asking for exemption was a bet they tried to play here, they lost and now spinning the narrative.

reply
Laws and strategy are not fixed, and public bickering is part of how they get optimized.
reply
Nothing usually gets fixed by making belligerent appeals to emotion in the court of public opinion (which, in the EU, isn't nearly rooting for Apple as much as they might imagine, fwiw). If you want to launch something in a market you know to be heavily regulated, you figure it out or you don't launch. Sure, drop a hint here and there when asked in interviews about your product strategy, but you generally don't pick a public fight with the regulator or legislator in question.

Just imagine a European bank publishing a press release about how onerous the US credit card consumer protection laws are, or a Japanese car maker publicly whining about European car safety testing protocols delaying the market release of some of their models. Apple really is behaving in a very unusual way here.

And even though I don't like the implication of this (the law should not disadvantage anyone purely for being critical of it), I can't help but wonder how many fewer pages the DMA would be if Apple had engaged with its predecessors in good faith instead.

reply
> imagine a European bank publishing a press release about how onerous the US credit card consumer protection laws are, or a Japanese car maker publicly whining about European car safety testing protocols

Both of these happen. European banks complain about American securities law. And all manner of car makers delay releasing vehicles in America and the EU.

reply
Definitely, but both tone and forum of the complaints are generally pretty different.
reply
That’s fair. Apple bickers in the EU and U.S. It doesn’t in China. I have a clear preference for one set of political systems.
reply
They aren't releasing it in China either.
reply
Yet. But they are probably working with Chinese partners (including the government) on releasing something (maybe with Alibaba models instead of Google models, on a Chinese-local cloud rather than google cloud).
reply
A quick check showed it is estimated that Apple gets about 18% of it's profits from China but only maybe 7% from EU countries (ignore Apple's definition of Europe!).

Maybe China is easier to work with - perhaps their rules are made clearer?

reply
And they are framing the completely different in that case.
reply
As I understood it, you prefer systems with less freedom of speech.
reply
deleted
reply
Then don’t deploy it for Pete’s sake if you can’t guarantee basic privacy.
reply
> This slows down deploying the system globally.

Good. Pretty much everything should roll out way slower.

reply
I imagine complying with all kinds of laws and regulations slows releases in some way or another and having none of them would allow people to ship faster, so what makes these EU regulations so distinct? Do what you have to do to comply with the law and release, as always.
reply
> complying with all kinds of laws delays release in some way or another and having none of them would allow people to ship faster, so what makes these EU regulations so distinct?

DMA was designed to be a comprehensive regulatory suite. Lawmakers knew it would be onerous; that’s why it only applies to large companies.

Also, the DMA’s interoperability requirement creates external partners. Let’s face it, Apple’s track record with Siri sucks. If they launch a system and it is crap again, they may not now want an entire ecosystem of folks who will cry foul if they dump the API and start over.

> Do what you have to do to comply with the law and release, as always

Just follow the law. If that means not releasing in a jurisdiction, do that and then don’t tweet snotty things about it. (Siri AI isn’t launching in China, either. I don’t see PMs complaining about that in public.)

reply
No one complains (out loud) about US regulations either. Ultimately it’s about the weight you can throw as well as PR. Probably easier for Apple to make the EU look bad and drag their feet on it. I imagine they’re still not thrilled about the Lightening->USB-C change
reply
> No one complains (out loud) about US regulations either

Everyone constantly does!

reply
> Everyone constantly does!

In the aggregate, I agree, but in tech things are pretty loose outside of California.

reply
The same way they constantly do and don’t about the Chinese government I’d say.
reply
[dead]
reply
Don’t forget they’re already basically two years behind when they originally promised this stuff.
reply
So whats the issue delaying a few more months for a worldwide release?

The only reason for this is to take a swipe at the EU and try to push some bad opinion on to them from their customers.

reply
Okay? I don’t see the problem, these requirements are known from the beginning so if complying wasn’t planned and requires re-architecturing the software to make it happens that’s on the engineering org not on the EU regulator. Unless I’m missing something?
reply
These are relatively recent and may have come into force after development began, definitely after Siri development an initial integration into personal data.

I suppose if you think these rules are reasonable, you’d be happy to not have this functionality. The rest of the world will be happy to not allow third parties access to our data.

As a small developer, the cost to support something like this would be so overwhelming I wouldn’t consider supporting the EU officially.

reply
> As a small developer, the cost to support something like this would be so overwhelming I wouldn’t consider supporting the EU officially.

As a small developer, you wouldn't fall under the DMA.

reply
> These are relatively recent and may have come into force after development began,

If it were the case, Apple would just say it (with receipts).

> I suppose if you think these rules are reasonable, you’d be happy to not have this functionality.

As a European Apple user I am absolutely OK with not having these functionalities, which I am 100% sure would not even work as advertised given the company track record.

reply
> These are relatively recent and may have come into force after development began, definitely after Siri development an initial integration into personal data.

The DMA was substantially finalised by 2020, and came into force in 2023. Apple's AI thing was developed with the full knowledge that it existed. The issue isn't personal data here (that'd be the GDPR, and maybe to some extent the AI Act). The DMA is about _competition_. The EU's issue here is that Apple is giving its own AI thing a level of access unavailable to other vendors' AI things, I'd assume.

> As a small developer

You are not covered by the DMA. You'd need an EEA turnover of 7.5bn and/or a market cap of 75bn, for a start. And you'd also need to be a _platform_. The DMA only really applies to a few companies.

reply
I’m happy to not have it if it’s not compliant, yes.
reply
The point is complying with the DMA from the outset could mean having to launch a year later everywhere. Skipping the EU makes sense in a fast-moving market (if you’re designated as a gatekeeper).
reply
> Skipping the EU makes sense in a fast-moving market (if you’re designated as a gatekeeper).

Skipping the EU makes sense if the company doesn't want to comply with regulations aimed directly at it.

> complying with the DMA from the outset could mean having to launch a year later everywhere.

Oh no! Anyway...

Once upon a time, companies delayed launches specifically so they'd launch a better product. That seems to be gone these days and end-users have garbage products as a result.

reply
> Skipping the EU makes sense if the company doesn't want to comply with regulations aimed directly at it

It makes sense if you’re prioritizing time to market and agility. Once you’ve nailed down your product, you can make it compliant for more-onerous jurisdictions. You see this in finance all the time, where the U.S. tends to have the tightest rules around e.g. betting and crypto.

> Once upon a time, companies delayed launches specifically so they'd launch a better product

Because software shipped in a box. Also, compliance is orthogonal to how good a product is. Siri AI might be crap. It might be great. It might be almost perfect and then made great on second release. Everything slows down if the entire development process has to deal with open APIs and lawyers at every turn.

It’s perfectly legitimate to say we’ll develop this in other markets and ship it to the EU when it’s fully baked.

reply
They have already launched two years late. Remember when we all had to buy an iPhone 16 to get Apple Intelligence?

Besides that, Google has shipped many (not all) similar features to Pixels in the EU and have been for years.

reply
DMA has been a thing for 4 years.

Whatever Apple is cooking and however long its taken them, the DMA is not a surprise and they could well have been taking it into account from the very beginning.

reply
deleted
reply
> these types of compliance efforts can mean completely redoing multiple core systems to handle privacy, wipeout, audit, reporting, per-location policies, etc etc.

Maybe the phrasing is unfortunate, but if compliance to the law requires a “redoing”, launching in that market was never a priority in the first place. That’s a completely legitimate choice, but usually companies whining about regulations are making a financial decision rather than an ethical one.

reply
The point isn’t that it’s easy or straightforward to do. The point is that one of the world’s wealthiest companies can spare the resources needed to comply with the regulations of one of the world’s largest markets.
reply
> one of the world’s wealthiest companies can spare the resources needed to comply with the regulations of one of the world’s largest markets

At what cost? This is Apple’s second bite at AI. Giannandrea fucked up the first time. I’m honestly with Cupertino on not over complicating it the second time around. If they found the right mix of features and architecture, great, then work to port it to high-bar jurisdictions.

reply
> At what cost? This is Apple’s second bite at AI. Giannandrea fucked up the first time. I’m honestly with Cupertino on not over complicating it the second time around. If they found the right mix of features and architecture, great, then work to port it to high-bar jurisdictions.

I totally agree with you in principle here, but Apple have a pretty large vested interest in not supporting interoperability here (and in the other cases, like Mac mirroring) so I honestly don't see that happening at all.

This is purely a lobbying move against the EU to get EU citizens/politicians to complain about the laws and get an exemption.

And to be fair, Apple's business model is currently structurally incompatible with a lot of the DMA (which I personally think is a good thing), so they kinda have to fight it for a while.

reply
That lobbying move has been tried how many times? It hasn't worked once. There is no disagreement along any political lines I can think of.

It's not that we particularly like the EU government here in the EU. But we do like when they make pro-consumer laws.

reply
> Apple have a pretty large vested interest in not supporting interoperability here

Yeah that needs to stop. This is kinda why the DMA was created in the first place...

reply
It doesn't _have_ to stop - the features just can't ship in the EU while these requirements are in place, which is exactly what is happening here. The law is working as intended, just not in the way the proponents thought it would.
reply
> the features just can't ship in the EU while these requirements are in place,

Yes, they can. Apple wields its duopoly power to try and bend governments to its will.

reply
> purely a lobbying move

It can be more than one thing. It’s a lobbying move, to be sure. But it’s also almost certainly a time-to-market and potentially cost-mitigation play, too.

reply
The cost is almost certainly in time, not staff
reply
Yet, they chose not to. That also speaks for itself.
reply
Having worked at Apple and similarly giant companies, the idea that "they have enough money to do it" is incredibly naive. Rewriting all the basic software primitives of the iPhone, or the Mac, or iCloud, or CloudKit, or choose whatever massive surface area this legislation impacts, is not a matter of simply spending enough. Doing so requires the time and attention of the very few subject matter experts who are able to competently do it. The true cost is to your strategy, your business plan, and your product roadmap.

So it becomes a purely business decision: Do we risk a 10% global revenue penalty to release this globally, do we release this everywhere the DMA does not apply, or do we simply not build it? And make no mistake, even if Apple moved heaven and earth to try to comply with DMA they are STILL RISKING the full 10% penalty if the EU decides against them.

reply
Didn’t write “money”, wrote “resources”, but sure.

Yes, there’s a risk to releasing a product whenever you can be held accountable for that product. I understand that Apple seeks to be as unaccountable as possible.

So we ultimately agree with one another: Apple can do it, but doesn’t want to, for various reasons.

reply
There wouldn't need to be a redo if the products had been built with compliance in mind. This law isn't something new; it's been around for years now. Not taking it into account from the beginning with the intention of operating in the jurisdiction means there's definitely intention to skirt. Particularly given the previous issues in the same department.
reply
No one implements compliance goals for fun. If they didn't think they were going to have to comply, they wouldn't do it. If they thought the law would be overturned they wouldn't do it. Same if they thought they would successfully fight the law in court, if they thought consumers would revolt, if they thought that they were a Special Squirrel who would get exemption, or whatever.

Does this put them stupidly behind schedule? Yes, and bummer for them, but I highly doubt that a company as politically savvy, legally savvy, and wealthy as Apple would do this "by mistake".

reply
It’s not an enormous effort if you plan for it. They clearly knew about this, and could’ve afforded to plan for it. Their whole shtick is locking users in, and DMA is their nemesis.
reply
Meta research eng here

Yes, but also its much cheaper to build it in at the very start.

When we built pervert glasses research platform, if we'd just ignored the data privacy laws we could have built it much quicker. But, the only reason it took extra time is because

1) we had no idea what we were doing and

2) the lawyers had even less idea, so we had to do a bunch of reading and make a best guess.

Turns out the guesses were right, but it was painful getting the lawyers to understand.

reply
> these types of compliance efforts can mean completely redoing multiple core systems to handle privacy, wipeout, audit, reporting, per-location policies, etc etc. These efforts can involve hundreds to thousands of people for multiple years.

What if I tell you that there's a surprisingly simple, straightforward and above all very cheap solution: don't implement privacy-invading or anti-competitive features in the first place ;)

reply
Sure let me wave a magic wand and have a data center that can meet all these regulations materialize before us. Yes I'm sure every American tech company is tripping over themselves rushing to build data centers that are subject to European taxes and regulations for the exact same compute.
reply
> completely redoing multiple core systems to handle privacy, wipeout, audit, reporting, per-location policies, etc etc

So Google chose to be evil, now they have to rip all the evil out and redo it from scratch. Can't say I have any sympathy. Should have done the right thing from the start.

reply
Why does systems are not designed take into account that compliance work?
reply
I assume you're asking this in good faith, so I'll answer in good faith.

Laws vary from country to country, state to state, and they vary tremendously. Laws are also changing all the time. There's literally no way to predict what rules will be in place at any given time.

Also, adding code to meet some government regulation takes time and effort that (form the company's perspective) could be better spent building a product and making money. No one would "choose" to implement some random compliance rule unless they're forced to.

reply
But EU has a pretty uniform laws, so this comes to just one issue: time. Did Apple start working on this feature before EU implemented the law? This might be the case, but even if it was after, they could start working on implementing that sooner.

It would be good for US companies to know that EU laws are not "guidelines", just as US enforces their laws on companies from outside.

reply
Sure but we're talking about the unified law of almost an entire wealthy continent here. It's EU ffs. Not some small island country in the middle of the ocean.

This looks to me like yet another bet from Apple: "they'll buy iPhones anyway, let them wait".

reply
Because of move fast and break things mentality. Let's say if ChatGPT was launched respecting GDPR, or respecting copyrights, they would have reached nowhere.
reply
> Let's say if ChatGPT was launched respecting GDPR, or respecting copyrights

Bad comparison. Launching with GDPR compliance isn’t particularly taxing if you’re already complying with California’s CCPA. (You need your twenty-eight EU law firms on retainer, but the big firms package that conveniently.)

Copyright theft in AI, on the other hand, is a global phenomenon.

DMA is most akin to the U.S. system of designating financial institutions SIFIs and then putting a bunch of extra requirements on them. Almost intentionally onerous. Hence ringfenced to select large companies.

reply
You're essentially saying that privacy violations are baked into the cores of these systems.
reply
The DMA has nothing to do with Privacy - it's an anti-competition scheme. Apple is saying that privacy is baked in to their approach, and they can't ensure that if they allow every other AI provider the same level of access.
reply
DMA is not about privacy.
reply
So, what are the chances they'd completely redo multiple core systems in the 18 months they asked for?
reply
It's also not a "two-pizza team" market.
reply
So? It's also more effort to work everyday to earn a living than simply stealing what you need from your neighbors at gunpoint. But the law's the law.

As a European I'm conflicted because I think this particular set of privacy laws are overreaching bordering on stupid; but "exemptions" for one of the richest corporations on earth would be beyond absurd and infinitely worse.

reply
> these types of compliance efforts can mean completely redoing multiple core systems to handle privacy, wipeout, audit, reporting, per-location policies, etc etc. These efforts can involve hundreds to thousands of people for multiple years.

Then you should have done it right the first time.

reply
Agreed, unless you specifically know how a regulator will interpret a broad requirement on a edge case it’s a lot of effort to even figure out what the plan is, much less implement it.
reply
I have a crazy idea: design the product with compliance in mind already!
reply
Privacy by design isn‘t enormous effort, as every European engineering manager will tell you. It‘s just another reasonable and straightforward set of requirements. Of course, if you want to have privacy-less features in jurisdictions permitting it, that‘s a different story and that‘s a choice.
reply
In this case it looks like EU is requiring to let competitors mess with Apple users privacy.
reply
Privacy by design while making a seven-figure salary because you make people buy stuff they don't really need is quite difficult ;)
reply
The truth is very often that it is long and hard not to do the work to comply but how to not comply or do complicated things to abuse of loophole despite being able to pass the law on the letter of it.

Especially in the case of apple or Google. Look at the app store situation. It is very straightforward to do the work for the whole thing to be open to any competitor. But it is hard to try to design and implement a solution to try to not break any regulations but still manage to keep users captive the maximum without having competitor entering our walled garden.

reply
Yet Gemini had no issues to comply with EU's DMA and release on all phones?

Let's call it how it is: Android phones allow every competitor to run their chatbot in place of Gemini. Want Perplexity instead of Gemini? You can have it. Samsung launches with Perplexity as of late.

Apple? As always, went into "ay mate, too integrated, can't give the same APIs to competitors" lame excuse.

reply
Appples architecture prevents them from seeing customers data (see Private Cloud Compute documentation). Data that Gemini Assistant (not referring to the distilled version Apple uses) see goes straight to Google. Big difference here.

Weird to say it but the only assistant with any guarantee for privacy by design is Siri at the moment.

reply
What is the source of this claim that this is the reason?
reply
> Data that Gemini see goes straight to Google.

That's not how the deal was announced. You don't pay Bs / year for a licence to gemini to send them your data. You pay that to run it on your own hardware, in your own garden, so the data stays put.

I know the internet is always anti big companies, but this is likely a "not worth it for now, we'll eventually do it" effort from Apple. The EU AI act is a mess, and the effort to simply know what they have to do to comply with it is likely going to take armies of people (not devs) and a lot of time, as the OOP said.

And the saddest part about it, is that Apple has the money and resources to sink into this. Think about all the small players that don't. This is yet again a miss for the commission, with the end result being an insidious form of regulatory capture. It sucks for those of us running small companies. Oh well.

reply
I was referring to Google Gemini AI (their branding is horrible) - Google can see ALL of your interactions with their services - that's not what Apple gets to see

https://security.apple.com/blog/private-cloud-compute/

reply
If the options are "launch in the rest of the world quickly and get to the EU later" or "launch everywhere at once years after the competition" PMs and execs are going to choose the latter every time.
reply
Former, you mean?
reply
Yes, indeed, I wasn't paying attention.
reply
reply
100%, it's been almost 2 years that you can choose whatever you want.[1]

I run Perplexity in place of Gemini, but I can also run Claude and others.

[1] https://i.imgur.com/BgvxqQQ.png

Apple is just being the usual Apple being both an hardware vendor and giving it's own software advantages that competitors don't have and using the security bogus argument as always.

And yet, people believe that crap and jump into defending Apple as if being an Apple user is their identity, sad.

reply
But read the article, the EU wants even tighter integration for third parties, so it’s not exactly like Google is out of the woods regarding the DMA and this.
reply
That's not fully true. Lots of things get to Europe later (Gemini memories, though we have them now, Spark as latest noteworthy)

Or never. Like the majority of Pixel 10 on device AI features (image editing, magic cue).

reply
Some features don't land in Europe because US companies can't handle the amount of languages. For them it is English and maybe Spanish or Chinese because they don't care how heybmake money.
reply
Nonsense, Google is among the most aggressive when it comes to localization to the point of being oblivious.

I have not been able to switch language in Sheets since 2018, and I've changed any possible setting (even account language).

All guides are in English and I'm stuck with Sheets in Italian.

reply
I have the AI image editing features on Pixel in Europe.
reply
Wow, Google must be a poster child for privacy then.
reply
>These efforts can involve hundreds to thousands of people for multiple years.

And yet Apple had no major issues complying to the draconical demands of the CCP to sell and operate there. Weird.

Also, it's not like Apple can't afford the manpower for this. They're not a hole in the wall mon & pop shop.

reply
The new Siri isn't available in China yet either.
reply
Or really anywhere, since it comes out in Fall. Unless you count developer betas as available of course.
reply
It’s also only in English initially.

They can only do so much at once. And Apple is not a “hire an extra 30,000 people“ kind of company.

Apple usually rolls stuff out in stages. This is just an extremely high profile example.

reply
It goes to show that privacy is not a priority. And it should be.
reply
No, this is unrelated from privacy. The issue is that the EU won’t allow the new Siri because Apple isn’t willing to open up the system enough for 3rd party AI agents to get the same functionality.
reply
Because Siri is the brand and other competitors will dilute the brand with their inferior products, is the line of reasoning, I'm sure. I'm unclear on why apple is branding the AI launcher or whatever if it's just going to be a wrapper for a third party product, however.
reply
Functionally the EU is requiring that Apple dramatically RELAX their privacy and security postures.

I’m sure Apple doesn’t want to cave and give OpenAI free access to the spotlight semantic db, the ability see what’s on your screen at all times, etc.

reply
> Functionally the EU is requiring that Apple dramatically RELAX their privacy and security postures.

No. Interoperability doesn't require Apple relax their privacy and security postures. It could instead require third parties to improve theirs.

reply
> It could instead require third parties to improve theirs.

Apple made it sound like their proposal for that was rejected by the EU. And it would be consistent with previous regulatory decisions by the EU for them to not want Apple to be setting the rules for how third-party interoperability partners/competitors ensure privacy.

It seems to me that the EU has a preference for protecting privacy with legal mechanisms, and generally doesn't approve of Apple's attempts to protect privacy with technical mechanisms because that inevitably limits interoperability with systems that aren't designed around the same restrictions and assumptions.

reply
Same as you wouldn't want every app to read your contacts or location. If we only had something to do that.

</s>

reply
Which I would argue is HARDER to do while preserving privacy.
reply
Part of it is also a certification circus.

For example, with Copilot, you get a contractual pinky promise that they cannot access your data.

Can engineers really not access ? Can the police really not access ?

It's like AirTag for example. Apple cannot access it because it's scientifically "impossible" by design, but if they sign-in to your account, well it's over.

Once Apple fills the right audit / certification / paperwork they will be able to enable that feature. It could also be a negotiation lever.

reply
> privacy is not a priority

Isn’t this less about privacy than competition?

reply
EU privacy laws are not there to protect your privacy, its there because the law makers don't know how modern privacy works and wants their name on the law so it seems they did something.
reply
I think you should elaborate a bit on that because to me it seems that EU privacy laws are actually fairly good at protecting privacy.
reply
EU has some of the best consumer protection and privacy laws on the planet.
reply
Their laws are basically the equivalent of if there is no code, there are no bugs. EU laws forces citizens to get no new tech, privacy preserved.
reply
Uhm no, EU privacy laws are actually pretty simple: do not collect data you don't need without asking consent from a user first.

Which should IMO be the basic principle worldwide. But unfortunately in many countries, companies are more powerful than governments/regulators, so they get to grab everything they can get their hands on.

reply
Man, if we had computers in EU we'd be really angry at your dumb false posts.
reply
Also it does not matter what you do in the end. If you are Big Tech the EU will sue regardless and always finds an excuse.
reply
Do you think this is a problem with the EU? I don't. I think it's a problem in the way that Big Tech operates: by function of theft and laundering of data, and by screwing end-users and consumers in favor of profits.
reply
As I follow the situation, it seems that regulatory uncertainty is a major issue though- the EU’s requirements are framed in terms of outcomes sought, rather than in terms that can be quantitatively shown as met or broken. So it’s not a matter of dedicating a team to meet a list of requirements, but instead navigating the worst case scenario of enforcement if post-launch the EU determines that the proscribed outcomes aren’t being met.
reply
In this case it looks much simpler: Apple strictly does not want to open up the iOS platform to other competing agents, as they lose the monopolistic moat if they do. While making a true developer platform with good documentation is often hard and expensive, with the market access they'd get, companies would gladly jump on it even if it was badly documented as long as they have guarantees of continued legal access.

At the same time, this potentially opens up the entire worldwide market (imagine EU iPhones being imported into US to use with OpenAI or Claude Cowork), and they probably made the estimation that keeping EU out is still better value (70% of the market all to themselves) than fair competition in the 100% of the market (I guess they estimate they might get less than 70% in that case).

Or they are hoping that EU customers will want Siri AI enough to campaign for a change, but I'd find that highly unlikely.

reply
> imagine EU iPhones being imported into US to use with OpenAI or Claude Cowork

That's not the case. it's merely software (exactly like my iPhone 16 lacking the promised AI features claimed at WWDC24).

Anyway as I'm now within the EU with phone I bought before moving to the EU, regional features (or restrictions) depends on the logged in account and device regional settings. Except physical considerations (eSIM design, actual radio transceivers). The hardware is the same thank god.

reply
deleted
reply
Yeah, Siri was such a poor solution compared to Google (and Google's is also poor in EU) that no one would make a campaign.

If Siri wants to be seen as anything it should first support every EU language and they can work from there.

reply
Those requirements are explicitly on the outcomes because companies like Apple used to abuse loopholes in previous, non-outcome defined laws. They, as always, have no one to blame but themselves.
reply
A lot of regulation is legally defined in terms of outcomes. That in itself isn't unusual. Checklists of technical requirements are almowt always a derivative and a suggestion about a safe path to meet the regulated outcome. This is how "blessed" standards for e.g. medical devices work. This shields the laws themselves from overly technical discussions.

The only difference that I can see here is that the standards layer hasn't solidified yet.

reply
> but instead navigating the worst case scenario of enforcement if post-launch the EU determines that the proscribed outcomes aren’t being met

This is true of most things that involve legal. Laws are not code, in basically any jurisdiction they are subject to interpretation, and just because you've dotted your Is and crossed your Ts, doesn't mean an enterprising enforcement agency won't still come after you

reply
That is fundamentally how EU law works

The intent matters, not the letter of the law. No loopholes, no bad faith interpretation. Just do what the law wants from you, if you make a mistake in good faith, you'll be given leeway to fix it.

> When interpreting EU law, the CJEU pays particular attention to the aim and purpose of EU law (teleological interpretation), rather than focusing exclusively on the wording of the provisions (linguistic interpretation). This is explained by numerous factors, in particular the open-ended and policy-oriented rules of the EU Treaties, as well as by EU legal multilingualism. Under the latter principle, all EU law is equally authentic in all language versions. Hence, the Court cannot rely on the wording of a single version, as a national court can, in order to give an interpretation of the legal provision under consideration. Therefore, in order to decode the meaning of a legal rule, the Court analyses it especially in the light of its purpose (teleological interpretation) as well as its context (systemic interpretation).

https://www.europarl.europa.eu/RegData/etudes/BRIE/2017/5993...

reply
EU laws are written like this to give companies maximum freedom in how they implement their solutions, not to lay traps for them to fall into.
reply
The criticism reads like people who don't understand a high trust society - which I don't think is actually the case here, more like assuming that the foreign guys are bad guys.

"They really don't try to fuck you over if you engage with them in good faith?"

"Yes, really."

reply
> let them get used to using it every day for 18 months, then pressure the EU to let it continue or you rip the feature away and anger users (who you then point to the EU as the problem)

And you’re saying that consumers would be incorrect in thinking that?

reply
Throwing infinite money at engineering problems doesn't move deadlines arbitrarily.

But Apple's position here is actually really wild: Apple claims to protect user privacy all the time. But they can't offer a product in a major jurisdiction that has actually meaningful privacy laws? Didn't they consider that while designing the product?

This is quite the contradiction.

reply
> Apple claims to protect user privacy all the time. But they can't offer a product in a major jurisdiction that has actually meaningful privacy laws? Didn't they consider that while designing the product?

Complying with complex privacy laws is surprisingly orthogonal to making a product with good privacy.

In another regulatory area (not privacy, but something more historically regulated) we ran into strange situations where complying with the letter of the law would require us to walk back things that we had done in a better way. The laws are not simple and they're not written by engineers or even people who understand what future product needs look like.

reply
Complying with complex privacy laws is surprisingly orthogonal to making a product with good privacy.

Maybe it's more because the privacy is largely marketing and helps with continuously shutting out competitors under the guise of privacy?

If they really cared about privacy, they would end-to-end encrypt iCloud backups [1] by default and not just when ADP is enabled, which only a small subset of users do. In fact, many technical people I know don't even realize that iCloud backups are not end-to-end encrypted. At any rate, this large hole opens a lot of data (including iMesssage) open to Apple, law enforcement, etc.

https://support.apple.com/en-us/102651

[1] And iCloud Drive, and photos, and notes, and voice memos, and wallet passes, and contacts, and reminders, and...

reply
It's incredible how people are acutely aware how technically inept regulators are (laws affecting their personal use of technology) and how quickly they side with regulators when a law affects how corporations use/create technology.

If regulators suck at understanding tech, they are making poorly thought out laws for corporations just as much as they are for you.

reply
Privacy laws are not complex, they only become complex if your goal is to actually skirt them.

Tax laws are also quite easy, tax lawyers are only needed if you want to NOT pay what the country you're operating in is owed.

reply
Respectfully, it sounds like you just haven't dealt with any significant tax or regulatory tasks.

There's entire industries of experts who work on these tasks, and they don't just work for people trying to skirt the rules. I've hired people for both tasks and the reason was specifically to comply.

reply
Not privacy, but as an example:

NIST, MS, and the security community all recommend against forcing people to change their passwords on fixed intervals. They should only be changed when there is an indication they have been compromised.

PCI requirements demand mandatory 30 day rotation intervals on user passwords for users with administrative privileges, IORC. Something like that.

They haven’t kept up. So until they change the rules you can either be PCI compliant or implement the current best practice. Not both.

reply
And where the complexity comes in is where you need to comply with PCI and NIST 800-63 at the same time.
reply
would you say civil engineers are only required if you want to skirt building codes?

Someone has to understand the codes and how they might be applied to a specific project, and direct a project such that the outcome will comply.

Codes dont provide a blueprint for a house or a bridge. They stipulate features and properties that it must have. Design resides with the firm.

reply
> Privacy laws are not complex

Privacy isn’t complex, compliance is.

> Tax laws are also quite easy

Yet audits are still a pain.

> tax lawyers are only needed if you want to NOT pay

This is nonsense. Tax lawyers are sometimes used to skirt the law. They’re much more often there to help prove you followed it.

reply
The exemption Apple wanted was not from a privacy law, but from the DMA. They never claimed to have an issue meeting their privacy laws when using their own product, it was other people's products that they said they couldn't guarantee the privacy of.

Here's their argument in their own words: https://www.apple.com/newsroom/2026/06/due-to-dma-siri-ai-de...

reply
You mean they wanted there to be no confusion whatsoever that they wouldn't allow competition in their ecosystem.
reply
The exemption requested was temporary.
reply
The 18 months was to entrench themselves in favor of other players.
reply
EU response said it was "for a minimum of 18 months" — does not sound temporary to me.
reply
How is that not temporary? "Ok, you asked for an exemption for a minimum of 18 months, we're granting you what you asked for, an 18 month exemption".
reply
By now, Apple has accrued years of malicious DMA/DSA compliance. After those 18 months they'll try to find another reason not to allow competition.

Besides that, the law is the law and the DMA/DSA has been around for years. Why should they get an exception is one part of a duopoly?

reply
That's even worse, then. They are not responsible for other companies' products. So this is just another piece of anti-DMA propaganda then. They have been fighting it loudly and with toddler-level arguments since they became subject to it.
reply
A huge part of Apple’s marketing, whether you believe them or not, is that they try to protect your privacy.

The smartphone is probably the most sensitive device most people own. It knows your location always. It has your banking apps. Your password manager. Your instant messages, and social media chats, it knows whether you’re walking, or driving, or talking on the phone, and to whom.

Once Apple allows any other vendor to vacuum all of that intensively private information out of an iPhone, Apple becomes indirectly responsible for potentially massive privacy breaches.

reply
All of that happens only if the user chooses to do it though. Anybody is free to stay in the caged Apple garden. The EU just wants them to leave the door unlocked.
reply
A door with a lock is different from a wall with no door. Same argument that gets made with government-keyed or government-breakable encryption schemes: it's better for everyone to not have the backdoor at all.
reply
> They are not responsible for other companies' products.

Legally, maybe not, practically it becomes their problem.

reply
>But Apple's position here is actually really wild: Apple claims to protect user privacy all the time. But they can't offer a product in a major jurisdiction that has actually meaningful privacy laws? Didn't they consider that while designing the product?

The DMA isn't a privacy law. In this case, the DMA would appear to require Apple to open up all user data to any AI agent. That removes the ability to provide privacy protections.

You can argue Apple should do that, but you can't in the same breathe argue for privacy.

reply
No, this isn't the claim.

EU wants Apple to open 'Siri AI', with access to a personal context, open to other model/AI providers.

Apple says "We can't do this in a privacy preserving way".

You can definitely question what their true motivations are, but it seems pretty plausible that there is a moral case for this system to not be opened up to other providers who may do a worse job at privacy than Apple (especially when you are Apple and you trust yourself).

I think there is a place in these sorts of ecosystems for privileged players. If you buy an iPhone you implicitly must trust Apple to some degree.

reply
As has been pointed out elsewhere, DMA isn't a privacy regulation. It is simply about competition. You can be in 100% compliance with DMA and poor privacy protections. This is the crux of the problem. How do you preserve the privacy of your customers while complying with regulations where the simplest path is to compromise your customer's privacy?
reply
The issue here isn't EU privacy laws (which Apple has been historically quite good at complying with, by big tech standards); it's EU _competition_ laws.
reply
Lemma 1: you want to protect your users privacy, and are also beholden to regulation enforcing that commitment (GDPR).

Lemma 2: you are obliged by other regulation to offer equal access to user data to third parties, so others can build equivalent functionality (DMA).

Lemma 3: malicious third parties will absolutely try to abuse the access and trick the user into sharing their data by all means possible. You will be held responsible in court of public opinion at minimum and legally at maximum if/when a malicious third party abuses said access.

This is a hard, possibly technically unsolvable problem no matter how much money you might have, because the root issue is not technical, it's the fact that you legally have to give third parties access and no way to control what they do with it - and as others have mentioned in the threads, it's exacerbated by the fact that the regulation doesn't say "this is okay and this is not", it is vague and judges things "by outcome", so you may spend all the time in the world implementing a solution you think will work, and then get hit by fines/lawsuits because the implementation is judged as not sufficient after the fact.

reply
I am not sure this is as much of a tension as you make it sound: where is the obligation that a marketplace administrator will be blamed for any and all breaches of data privacy trust from a participating (likely malicious) third party?

According to GDPR, the app developer is the "data controller" and thus ultimately responsible. Only in the case where Apple knowingly participated in unlawful behavior is it likely to be held accountable, and even then, in addition to the app developer. Obviously, if we are not talking about leaks from the actual App Store system (eg. Apple account logins and user data).

So while it sounds plausible, the legal framework is exactly not what you describe here — Apple can claim to want better protection for customers by not allowing third party apps, but EU rejects that (it can similarly extend to app store itself) and pushes for competitive landscape with DMA instead.

reply
Apple certainly is held responsible for such breaches by the public. And, believe it or not, I think they feel responsible for protecting their users.
reply
But this isn’t a normal app. Apple is the one handing over all the data to the AI service.

Couldn’t someone argue that they “knowingly participated“? Do you think they want that risk?

reply
Like they now hand over all your contacts, your location, calendar entries, microphone access, camera access. If you choose to do so.

Nothing holds them from having designed this as an API that others can use where the user has permission toggles of what data they want to share with the LLM provider.

reply
This is the smartest summary in the post
reply
> Apple claims to protect user privacy all the time. But they can't offer a product in a major jurisdiction that has actually meaningful privacy laws?

The DMA and the GDPR are laws that at their core make each other more difficult. the stated outcome of the DMA - allowing any vendor/user full access to your device - is not easily supported when solving for privacy.

reply
A popup that's like "do you want to give app XY access to this data?" is really not that hard to build... It's a lazy excuse, nothing more.
reply
There’s a difference from being able to protect privacy, and doing so in a way that complies with EU law
reply
Apple is providing a level of privacy far beyond what the laws require. It would be easy if they only wanted to comply with GDPR and DMA.
reply
Protecting user privacy and reducing surface area for litigation against the business can happen simultaneously. Not that it is, but just saying, politics and difficult to define thresholds muddy the waters.
reply
> But on the other hand it also feels like a straightforward play for consumer sympathy

100% - just like Apple making such a grandiose show of "privacy". "Privacy" for Apple eventually led to Apple specific and Apple-only allowed ads in first party apps and now Siri connecting to Google servers.

reply
Indeed. If they really cared about privacy, they would end-to-end encrypt iPhone backups by default. But since they don't, US law enforcement can request my iMessage chats because the people I talk to (probably) do not have ADP enabled (which enables end-to-end encryption for backups).
reply
Personally, I wouldn't want Apple to comply with this EU law and I hope that more companies refuse to release features with onerous requirements. Opening up all access to control the phone to some random app the consumer installed seems super dangerous.
reply
Letting a US company (under jurisdiction of, say, US Cloud Act, but also unknown administration orders that might come) strictly control the phone for a privacy focused EU citizen (or more broadly, non-US citizen) seems super dangerous.

The requirements are not onerous, it is the basic preemption of monopolist behavior.

Qualifying "random apps" is something that is a true challenge, but that holds regardless of the API being offered — the problem is that Apple saves some programming API only for themselves, instead of introducing acceptable & objective market terms to be met (if deemed unsafe, they could require companies to demonstrate compliance with things like CRA to get access to these APIs).

reply
I am perfectly ok with EU having different rules of their own but they also can't be upset when features aren't offered there. That is the trade-off they have chosen and I am ok with it.
reply
People in EU are upset that Apple is saying that EU would not let them build it, not that it's not offered there.
reply
Phrasing it like that that without mentioning the $40B penalty if Apple releases the feature today feels a bit off to me.
reply
Nobody in the EU would have been upset if they said: we cannot offer this in the EU because we want to shut out competitors from providing alternative LLMs and this is not allowed in Europe. Fine. I don't care.

Many Europeans are upset that Apple blames Europe that they cannot implement this because it would sacrifice privacy. (Which is kind of ironic, because the EU has nearly the best privacy protection worldwide.)

Apple doesn't care about privacy. By default (without ADP), your (i)Messages, Drive files, contacts, calendars, backups of data from third-party apps are not end-to-end encrypted [1]. US law enforcement can request it. EU citizens are not protected because the US can use the CLOUD Act to demand the data. If Apple really cared about privacy, they would have closed that hole long ago.

[1] https://support.apple.com/en-us/102651

reply
That's how the EU enforces its laws - a fine that hurts. How else would you like them to it?
reply
> Opening up all access to control the phone to some random app the consumer installed seems super dangerous.

Do you never install software on your desktop computer?

reply
Don’t install the app then. Consumer protection at some level means the consumer needs to be informed. I’d rather have a choice than just chow down on whatever the gatekeepers call food.
reply
deleted
reply
True hacker spirit here.
reply
"Onerous requirements": users have the right to chose, users have the right to privacy.
reply
EU should mandate open alternatives to Siri on Apple
reply
I think there's a reasonable question of whether the Siri stuff is even a feature that customers want. Additionally, money can not solve all problems, 9 people can't make a baby in a month, and if these sorts of regulations are serious at all like they are for medical regulation then you really do need to do the work of assessing risks, etc., and there's a chain of waterfall development to all that.
reply
No amount of people can make any amount babies, it's an unrelated chemical process, never cared for that analogy.
reply
Does a baby build itself? No. Does the mother build the baby alone? No.

I don't think you can call the process unrelated to the mother or the baby, they're both pretty important throughout the whole thing.

reply
Apple has a third of the EU market to itself. It would be just insane for the EU to give an exemption that means the law doesn't apply a third of the time.
reply
The market regulators don't give a fuck if companies screw over their customers privacy wise, as long as it's to the advantage of European companies and European customers.

This can lead to absolute insanity as companies try to satisfy both privacy and market conditions. It's not simple. How many years did google waste with Sandbox?

reply
> It's not as if Apple doesn't have the money to dedicate a team to matching the EU's requirements on a deadline. They just choose not to.

The one legacy in Apple that Steve Jobs left behind is their distaste for taking risks that lose them money (ChatGPT was going to be their AI core... but then they had Altman ousted, so they backed away and partnered with Google instead), and spending money. I think they're still the only company with a kitchen in the valley that still makes employees pay for their own lunch, and the reason is the most BS reason that Steve Jobs pulled out of his rear end. It's so the employees appreciate the lunch, really?

reply
Well, whatever the real reason is, people do appreciate things they have to work for more than things given for free.

I’m not saying I believe that’s the real reason here. But it is broadly true. Ask any company that offers a free tier where most of the complaints and problematic customers come from.

reply
> Well, whatever the real reason is, people do appreciate things they have to work for more than things given for free.

People can also appreciate things they get for free though. I'd appreciate a free lunch, most places I've worked at, actually nowhere I've ever worked, EVER has given me a free lunch. Now if its a difference of paying for a quality lunch at a reasonable price, and not paying for lunch but its mediocre, then yeah, seems like a no-brainer.

I wouldn't be surprised if Steve Jobs implemented was a way to get them back into the green.

Also, TIL:

> Jobs, who notoriously took a salary of only $1 a year, used to "scam" Apple out of free lunches by scanning his badge alongside colleagues and insisting on paying for everyone, knowing the charges would just default back to Apple.

reply
> It's not as if Apple doesn't have the money to dedicate a team to matching the EU's requirements on a deadline. They just choose not to.

That's disingenuous. It's not about money, it's literally about engineering velocity. The amount of planning and engineering required for an entire interoperability layer that also ensures security and privacy is absolutely going to be something like a year-long engineering effort minimum. You can't speed that up by adding more money.

So it's either try to get an exemption to deliver this feature to Europeans while that work gets done, or wait 12-18 months for the work to be done -- work that isn't required to launch in the rest of the world.

Apple just wants consumers to be happy and be able to use their features. But the EU is requiring a ton of additional interop engineering, so consumers will just have to keep waiting and get features 1 or 2 years after the rest of the world, or never.

reply
In the end Apple is a business and the EU is a dwindling market, they have to choose smart.
reply
They should use siri to code it quickly, no?
reply
Nice, a die hard Trump and ICE supporter - law is law.

You cannot accept the concept of consequences. You are entitled to Siri AI? I highly doubt it.

You sound like a totalitarian: a state can come up with any law and everyone has to comply.

I think you should be reminded of the fact that you can go your own way with something state sponsored like the EU Chip Act, AI, Cloud. Let’s add “Siri” to the list.

I love the fact, that EU is getting a lesson, even though people obviously don’t get it.

reply
This has the "do you even know who you're talking to?" air from Apple. Everyone should comply but not us, we're too cool and too damn important.
reply
so you think its just a matter of ppl working through paperwork?

seems a bit simplistic.

reply
[dead]
reply
Reminds me of the old meme: America innovates and EU regulates.
reply
Do the f*n work to make it compliant! Its not like they're some bootstrapped company running out of a van. I can't say I'm always in favor or how compliance works but its a valid requirement.
reply
It sounds like the work on the privacy layer was significant and to give "equal" access to other competing AI systems, they would need to include that "for free" as part of the platform. Or they could try to keep that as the moat for Siri AI, and only offer privacy "entry points" that other agents can tie into, but vendors would have to implement privacy preserving functions themselves.

This is the bit that's likely hard, because generally keeping safety and privacy guarantees as data flows through the system is extremely hard, and Apple would not be able to guarantee it for other products without large review investment.

But ultimately, they probably just do not want to do it until Siri AI gets a decent marketshare first, so competing agents would have to both build new solutions for the platform once open, but also deal with an incumbent dominant player already on people's phones.

reply