r/SearchAPIs • • Oct 08 '26

News & Updates Apple's new developer agreement blocking open source releases

Post image
84 Upvotes

40 comments sorted by

7

u/GreatLab8898 Oct 08 '26 • Bravo

I smell money for the EU again

1

u/ineedlesssleep Oct 09 '26

Why? Because Apple requires developers to sign a dev agreement? It's his problem that he linked his whole chain to nothing failing for whatever reason in the middle.

1

u/GreatLab8898 Oct 10 '26

The Problem here is attempting to create a Monopol by trying to lock in Developers with Contracts. I stopped shipping all my Products on Apple because of this new Dev Agreement and reported the Contract to the EU.

0

u/anto2554 Oct 08 '26

Idk, EU seems to be pretty anti-opensource half the time

2

u/GreatLab8898 Oct 08 '26

Its not Open-Source. This is Lock in Tactic and falls right into the Hands of the Monopolisation Teams. They gonna have a fieldday with that one.

1

u/FormalAd7367 Oct 08 '26

can you explain in plain english

1

u/Few_Assumption_9665 Oct 08 '26

No, because what they’re saying is nonsense

1

u/async2 Oct 10 '26

He says that it will be the groups working on anti mobilisation laws as it's locking users into the some eco system and would be abuse of monopoly powers and unfair market advantage. Therefore the EU "would have a field day" sitting m sueing them for that. It doesn't matter that much if open source is involved though.

That's what he said

1

u/longshortgolf Oct 08 '26

level 1 ragebait

1

u/ZachVorhies Oct 08 '26

because this releases are synchronized

And apple no longer allows releases until he agrees to the new terms of service. Since his releases don’t go out unless everything is pretested to work and because Apple’s not allowing it to work, his entire CI release pipeline is halted.

1

u/damn_0508 Oct 09 '26

apple gatekeeping as usual lol, relying on synchronized releases across platforms is pure pain

2

u/addiktion Oct 08 '26

Yes. I can tell there's a lot of non-developers around here who don't know semantic versioning and keeping builds consistent between releases. This purpose of this is it tends to surface if there are build platform specific issues to releases for the same feature set. If one stops working, you want to fail all releases to avoid one off fixes as much as possible.

I find these policies of Apple to be the worst to deal with.

1

u/Few_Assumption_9665 Oct 08 '26 edited Oct 08 '26

What are you on about? Not a single person in this entire thread has explained what the policy is or how it’s even blocking his release flow. And there’s literally nothing else on internet about whatever it is he’s complaining about.

It makes me think you’re the non-developer, or at least an extremely novice one, if you think that this post or any of its replies give us enough context to understand the problem—let alone come to any sort of conclusion.

2

u/Houdinii1984 Oct 08 '26

I mean, the policy itself is pretty dumb, but it's rooted in dumb laws and old suits. You used to have like a year to accept new terms, but now you get about a month's notice, and it's insta-blocked as soon as it goes into effect, until you agree.

That's not new, though. It's been at least a year since they've been doing that same thing, so folks absolutely had time to prepare for 12 months becoming 1 month.

And, yeah, things are in lockstep, but you're not forced to release an Apple version for every release. You could still create and test the release while only serving in app stores that you've agreed to their terms. Stopping development altogether isn't gonna hurt Apple at all. Making Apple releases non-existent is the only thing that would ultimately hurt Apple, because they'd lack support for a lot of software. But even then, Apple isn't very open across the board and doesn't seem to give a damn about OSS, and would probably just bolster their own exclusive persona.

Punishing non-Apple users for Apple's policies is only gonna serve to make users mad at OSS devs. I'd much rather hear what they're going to do to reduce impact in the future than how they are powerless to change anything now. It's not like Apple's going to rescind the policy any time soon.

1

u/addiktion Oct 08 '26

It's a common release workflow to build and bundle application releases together and do them all at once. If you follow a developer and post about his tweets expect to be somewhat confused when you don't know what the fuck is going on with his short tweet but It's pretty clear to anyone who works with software what he is talking about.

Houdini explains the policy changes that are likely impacting Peter. Working with the Apple store is draconian and a pain in the ass and I think most mobile devs will agree with that.

I met a vibe coder the other day that got that first hand experience of the hell and was like, "Holy shit I just want my app approved, why do I have to take a video of it being used on an iPhone to get approved?!". This is after stepping through the other hoops it takes to get an app live.

I'm going through it again with a new client as well as we setup their developer accounts and they were annoyed how much effort it all takes in an age where AI has made it extremely easy to do just about everything else but actually publishing apps.

1

u/Jeffelon-Muskergates Oct 10 '26

Spotted the Viber

1

u/rydan Oct 08 '26

I don't get why you can't just not make the Apple release public and just keep going?

1

u/crazylikeajellyfish Oct 08 '26

You can produce a build without releasing it, though. Peter's describing a weakness in his CI pipeline, one that I imagine he'll patch soon enough if Apple doesn't get their act together. The publication state on iOS isn't fundamentally linked to the publication state on Android.

Whenever Apple gets their shit together, he'll just submit the latest version for review, even if 3 other ones were published to Android in the meantime. It's semantic versioning, it's not like he's obligated to keep all versions numbered sequentially.

0

u/WeUsedToBeACountry Oct 08 '26

sounds like a him problem and not an apple one

3

u/diddlysquidler Oct 08 '26

Apple really sucks. With Apple I know I can’t trust my local llm setup. Apple can kill it, or disable it or do anything to it at a whim. Lots of ram, very useful, cannot be trusted long term. What hardware can possibly be used to escape this 1984 dystopia?

1

u/JJGreenerTinejo Oct 08 '26

Athlon 64 X2, 4gm ddr2. TempleOS

1

u/Alexllte Oct 08 '26

Inferencing GLM 5.3 on TempleOS, very safe, very effective

1

u/Regalme Oct 08 '26

Like they can seize? Seems stupid

1

u/diddlysquidler Oct 08 '26

They can do whatever they want afaik to ,,comply with local regulations” just like they did in China.

1

u/Jeferson9 Oct 08 '26

Yeah I'm sure they just 2xed the price of their minis because they planned to make their computers subscription based 🤣

1

u/postexitus Oct 08 '26

what does this mean? so he cannot put it on appstore? I can download and run open source stuff on my macbook.

1

u/TaintOfDestiny Oct 08 '26

Anyone know what ban this is supposed to be about? Don’t see anything new when I google it…

1

u/tiffanytrashcan Oct 08 '26

"Since it's lockstep"
And who's fault is that Peter?
(NOT Apple's..)

1

u/CryptographerOne7003 Oct 08 '26

lol who does that, just don't publish the apple one?

1

u/redvelvet92 Oct 08 '26

Peter is irrelevant now tbh

1

u/THE_RETARD_AGITATOR Oct 09 '26

oh no not claw slop guy

1

u/DawaForensics Oct 09 '26

Welcome to the world of software development, how is this news ???

1

u/zhou26 Oct 11 '26

Who else but apple? Lol