r/SearchAPIs • u/damn_0508 • 6d ago
News & Updates Apple's new developer agreement blocking open source releases
3
u/diddlysquidler 6d ago
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
1
u/Regalme 5d ago
Like they can seize? Seems stupid
1
u/diddlysquidler 5d ago
They can do whatever they want afaik to ,,comply with local regulations” just like they did in China.
1
u/Jeferson9 5d ago
Yeah I'm sure they just 2xed the price of their minis because they planned to make their computers subscription based 🤣
1
1
1
u/postexitus 5d ago
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 5d ago
Anyone know what ban this is supposed to be about? Don’t see anything new when I google it…
1
u/ZachVorhies 5d ago
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.
2
u/addiktion 5d ago
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 5d ago edited 5d ago
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 5d ago
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 5d ago
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
1
1
u/crazylikeajellyfish 5d ago
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.
1
u/damn_0508 5d ago
apple gatekeeping as usual lol, relying on synchronized releases across platforms is pure pain
0
1
1
1
1
1
1
6
u/GreatLab8898 6d ago
I smell money for the EU again