1. Ok. A single link may be too restrictive. But I can see it as a way to ensure apps don’t present incessant nags (pop ups or ad-like messages) to push payments elsewhere.I’m siding with Epic on this one.
Apple is following orders as written, but I have doubts this is what the judge’s intent was.
The judge will most likely reword and reissue their order to be more clear, and Apple will be forced to:
1. Allow devs to put in as many links, and types of links, to outside payment that they want.
2. Can’t punish developers for pushing people to outside payment systems.
With this and the EU stuff, Apple’s interpretation of the laws is going to piss off a lot of judges and people with power, and they are playing with fire in my opinion.
2. Apple is punishing how? By charging fees based on the current structure less the cost of CC processing? By presenting a clear disclaimer the user is leaving the Apple ecosystem for the purpose of payment processing? The first is allowed and reasonable. The latter is legally advisable if not flat out required. Liability shifts to the developer for all payment issues. Most people will still expect Apple to deal with issues and refunds - probably even after reading and agreeing to the notice.