←back to thread

Apple vs the Law

(formularsumo.co.uk)
377 points tempodox | 3 comments | | HN request time: 0.925s | source
Show context
EMIRELADERO ◴[] No.44529425[source]
The greatest gem is found in the footnote, IMO

> "They managed to convince the courts that iPadOS is a separate operating system to iOS (it's not), which delayed iPadOS being designated as a gatekeeper for almost a year. They are currently challenging all of the rest: the iOS, Safari, and App Store designations, and successfully managed to avoid iMessage being designated at all. They have taken the DMA law to court for an apparently ambiguous comma in article 5(4) - the payment one, and for somehow infringing on human rights law in article 6(7) - the interoperability one."

Looking at the actual filing[1], Apple says:

> "First plea in law, alleging that Article 6(7) of Regulation (EU) 2022/1925 is inconsistent with the requirements of the European Charter of Fundamental Rights and the principle of proportionality, and that Article 2(b) of the European Commission Decision of 5 September 2023 is unlawful insofar as it imposes the obligations under Article 6(7) of Regulation (EU) 2022/1925 on Apple in relation to iOS."

For context, here are the full contents of Article 6(7):

"The gatekeeper shall allow business users and alternative providers of services provided together with, or in support of, core platform services, free of charge, effective interoperability with, and access for the purposes of interoperability to, the same operating system, hardware or software features, regardless of whether those features are part of the operating system, as are available to, or used by, that gatekeeper when providing such services."

[1] https://curia.europa.eu/juris/document/document.jsf;jsession...

replies(4): >>44529447 #>>44529557 #>>44530403 #>>44530746 #
jb1991 ◴[] No.44529447[source]
I am certainly not surprised that Apple is employing a lot of legal tricky to work around judgments. But what does surprise me is that there’s a very common attitude in forums that somehow Apple is the only company doing this, or they’re doing it worse than any other company.
replies(6): >>44529534 #>>44529561 #>>44529748 #>>44530069 #>>44531200 #>>44538526 #
vladms ◴[] No.44529561[source]
For me personally they seem to be more expensive than competitors and have a more aggressive stance on openness (ex: compare PWA support on Android vs iOS, not to mention the multiple other things like no multiple stores, the browser engine discussion, etc). So, I am not amazed that people think "on top of all the other things that you annoy us with you also try to avoid the law?!".
replies(2): >>44529621 #>>44533184 #
jeroenhd ◴[] No.44529621[source]
While I hate Apple's anti-consumer practices as much as anyone, the PWA platform is a system set up by Google first and foremost. Take-up has been limited outside of Google Chrome. I wouldn't say Apple's PWA approach is necessarily an example of Apple's fuckery.

This wouldn't be much of an issue, of course, if Chrome would just run on iOS like it does on any other OS, so Google can implement PWAs themselves.

replies(2): >>44529633 #>>44530192 #
lmm ◴[] No.44529633[source]
> This wouldn't be much of an issue, of course, if Chrome would just run on iOS like it does on any other OS, so Google can implement PWAs themselves.

You do understand that the reason it doesn't is because Apple won't let it, not that Google don't want to?

replies(2): >>44529716 #>>44532705 #
shuckles ◴[] No.44529716[source]
This is a fantasy. No customer wants PWAs. They exist to make developers' lives easier, not consumers' lives.
replies(3): >>44529814 #>>44530211 #>>44530426 #
1. rickdeckard ◴[] No.44530211[source]
The consumer doesn't care which method is used to serve an application. PWAs could easily be presented to the end user like a native App.

The problem is rather that PWAs would prove a viable path for universal cross-platform applications, taking away the gatekeeper role the OS-vendors have.

Paradoxically PWA-support is also part of the "we're no gatekeeper" narrative, so it's in the OS-vendor interest to keep it maintained as a hampered alternative to native apps.

replies(1): >>44533546 #
2. shuckles ◴[] No.44533546[source]
> The consumer doesn't care which method is used to serve an application. PWAs could easily be presented to the end user like a native App.

No it can't. The web will never support what's necessary for parity with native apps. Imagine trying to implement Liquid Glass in CSS.

replies(1): >>44535995 #
3. rickdeckard ◴[] No.44535995[source]
First, you're mixing up capabilities of PWA vs native apps (no one stated they're equal) and how an OS presents Apps differently from PWAs (which was my point).

Second (even though it's completely beside the point), especially Liquid Glass could be implemented in PWA, because it's a rendering effect the OS could put on top of appropriately tagged elements of the application. And voila, the same webapp could render in Liquid Glass in IOS26 and in less-gaudy Liquid Glass in IOS28, and meanwhile in no Liquid Glass at all on devices that don't have it...