Lolz Fortnite is a thing of the past.
How would this be objectively determined? What does "likely" even mean? Is 60% odds of success good enough? 50%? 10%?
I liked unreal tournament but I don’t like the direction of Epic these days. I do think 30% is too high a cut and have thought that from the beginning. But I do think they should get some cut. 20% seems fair especially since they are handling payment systems and the various tax laws, etc.
To me developer fee is just a capital expenditure and the Apple cut is an operating cost.
The App Store monopoly will eventually come tumbling down.
The App Store monopoly will eventually come tumbling down.
Whatever the judge says is good enoughHow would this be objectively determined? What does "likely" even mean? Is 60% odds of success good enough? 50%? 10%?
I think it’s telling that the only “testimonials” we have heard so far are from developers with an axe to grind against Apple.I think that this could be a triable issue, something that can be overcome with evidence of a monoplist exercising control. The purpose of marketing isn't "honest", but to draw attention to an issue or product or service. A hotfix could be shown to demonstrate the monoplist's power, a david and goliath scenario, such as how regardless of the merits of a hotfix Apple has discretion to later on revoke that power. All Epic needs to do is call "experts" aka other app developers to testify how Apple changed the terms later on. Who watches the watchmen?
That’s it in a nutshell right there!
...
The court says that in regard to Fortnite, preliminary injunctive relief is "rarely granted," with the ruling pointing out that an order for injunctive relief would require Epic to establish that it is likely to succeed in the legal battle, it is likely to suffer irreparable harm without relief, the balance of equities tips in its favor, and that an injunction is in the public interest, none of which Epic Games was able to do.
...
Your arrogance thinking you know better than the judge is astonishing. The whole reason for this “hotfix” was to give one version to apple’s review team, and then have a totally different version in the hands of the users, with a feature that Epic knew was in breach of their contract with Apple, and which Epic knew would never have passed an app review.The judge's adamant refusal to understand how flag-guarded features work or the difference between a hot patch (uploading new executable code to run on the device itself, which is almost completely infeasible in iOS) and changing server-side or server-gated client-side behavior is not only baffling, but undermines her credibility with the industry.
Because it goes to court around May. Can’t be thrown out any earlier than that.I wondered about this part too. If Epic hasn’t been able to prove it at the very least has a strong case, why hasn’t this just been thrown out as breach of contract, end of.
I think you missed the point of the footnote. The import of it was not whether it is rarely done or not. Her point is that Epic claimed that Apple was fully aware of the nature of the change when they submitted the hotfix, which is clearly ludicrous. Epic keeps making the straw man argument “there’s nothing wrong with hotfixes!”
And her point is that ”yep, that’s true. the issue isn’t that you made a hot fix. It’s that you hid the functionality enabled by that hot fix, and you know that’s the real issue Epic.”
Umm.. no. Gating new features behind flags so that they can be turned on after an app has been shipped to the user has been standard industry practice in the mobile space for a very long time — pretty much since the dawn of iOS development. I don't know any company out there that doesn't do that, precisely because fully testing a new feature perfectly is hard. So instead, they test it to the maximum extent possible, then turn it on for some subset of users, then eventually turn it on for all users.
The judge's adamant refusal to understand how flag-guarded features work or the difference between a hot patch (uploading new executable code to run on the device itself, which is almost completely infeasible in iOS) and changing server-side or server-gated client-side behavior is not only baffling, but undermines her credibility with the industry.
Apple hasn’t changed any terms later on. Epic tricked Apple’s app reviewers into accepting their app into the AppStore by hiding how it would behave. Not only is it obvious that the app would be removed, but intentionally misleading Apple is a breach of their contract.A hotfix could be shown to demonstrate the monoplist's power, a david and goliath scenario, such as how regardless of the merits of a hotfix Apple has discretion to later on revoke that power. All Epic needs to do is call "experts" aka other app developers to testify how Apple changed the terms later on. Who watches the watchmen?
I think you missed the point of the footnote. The import of it was not whether it is rarely done or not. Her point is that Epic claimed that Apple was fully aware of the nature of the change when they submitted the hotfix, which is clearly ludicrous. Epic keeps making the straw man argument “there’s nothing wrong with hotfixes!”
And her point is that ”yep, that’s true. the issue isn’t that you made a hot fix. It’s that you hid the functionality enabled by that hot fix, and you know that’s the real issue Epic.”
Now you have the Apple and Epic court date set for May 3, 2021, I look forward to no EPIC news related to this for awhile.