Live data from Hacker News

Apple agrees to settle potential class action suit by U.S. developers

axios.com

111–120 of 259 posts

Re: Apple agrees to settle potential class action suit by U.S. developers

#111

I don't understand why the App Store, this small "side business" in the grand scheme of things, is something Apple is worth fighting and dying over. It's literally, a small fraction of their revenue, and yet it grabs 80% of the bad PR and is now under investigation and proposed legislation in the US, UK, EU, Korea, and I think Australia. If I'm Apple, shouldn't it be obvious at this point that losing the App Store mo…

At this point, I don't think it's an economic calculation anymore, if it ever was. I think it's moreso that Apple genuinely believes that third parties shouldn't have access to their platforms without prior review. Everything else has an explanation from that:

- We need to monopolize control over who can publish software for our platforms, so we can enforce our security guidelines.

(This includes banning third-party app stores, emulators, virtualization, alternative browser engines, and all the other fun things Android users chuckle at iPhone users about.)

- Hiring reviewers to check all the apps we ship for problems costs money, so we need to get paid for that review.

- However, we can't just charge developers money for review, as it would be prohibitively expensive and encourage developers to not fix broken software.

(At this point we need to review what Apple's competition was in this space at the time of the App Store launch. That is, game consoles, which have been universally locked down and monopolized since 1985. The companies that owned those platforms generally charged per software build submitted for review. The cost per submission was somewhere in the 5 figure range and could take up to a month to approve. Nintendo was extra spiteful, and would actually refuse to pay you after you updated your game, until you sold another 1000 units. Steam didn't really bother reviewing software submissions, not because it was a free-for-all, but because partnering with them used to be a legitimate challenge involving bugging several different Valve employees.)

- Therefore, we need to bundle how we get paid for reviewing software into the cost structure of apps. That way, we get paid when developers get paid.

- Thus, we can't have third-party billing, because that would let developers evade payment for our software review.

Re: Apple agrees to settle potential class action suit by U.S. developers

#112
post #101

Earlier quoted context omitted.

That's a good one. Since legacy code is less likely to change than the English language, I just call it a "referer" in writing unrelated to HTTP. That way, I'm never confused. (Everyone else? Good luck.)

I used to do technical writing and for some software that I wrote the manual and help system for, one of the menu items was misspelled. I spelled the word correctly in the text describing its functionality, but whenever I referred (so to speak) to it directly as the menu item to be selected, I kept the misspelling (this was the early 90s, the days of people saying non-ironically that they couldn't find the "any" key…

Pretty sure people still can't find the any key, we just stopped asking them to!

Re: Apple agrees to settle potential class action suit by U.S. developers

#113

> Apple will offer more price points for apps. Today there are less than 100, but the company is committing to increase that to more than 500 options. I really hope they implemented this as an enum, so someone has to wade through: enum PricePoint { UNKNOWN = 0; NINTEY_NINE_CENTS = 1; ONE_DOLLAR = 2; TWENTY_DOLLARS = 3; NINETEY_EIGHT_CENTS = 4; DEPRECATED_NINETY_SEVEN_CENTS = 5; TEN_DOLLARS_PER_MONTH = 6; PORTUGAL_NAT…

Lol, few things trigger my OCD more than misspelled words in identifiers. I legit missed important use case while amending legacy system just because someone decided to have “priveleges” in the variable name. I hope all those ways to spell number 90 are part of the joke.

And everyone saying "backslash" is on the inside of an awesome joke too.

Re: Apple agrees to settle potential class action suit by U.S. developers

#114
post #37

Earlier quoted context omitted.

Well, what else are they going to do, not release a statement? If you release a statement about a legal ruling you lost, it's obviously going to be spun from whoever published it.

This is something of a nitpick but: Apple did not lose a legal ruling. Some companies initiated a lawsuit against them, and Apple and those parties mutually agreed to resolve their dispute, presumably with concessions from both sides. The agreement needs to be approved by a judge, but the parties in the case are saying that they are no longer in dispute under the proposed terms. Companies that get sued agree to settl…

> Apple and those parties mutually agreed to resolve their dispute

Indeed, but only after those parties took legal action. It's not that Apple at the first sign of disagreement said: "oh well, you were right all along".

Like somebody else said: Apple should just sh*t up about this. Don't spin it.

Re: Apple agrees to settle potential class action suit by U.S. developers

#116
post #97

Earlier quoted context omitted.

The key is to write out the enums to long-term storage as the names instead of the numbers, that way nobody can ever fix your spelling mistakes.

There are lots of ways for spelling errors to get reified. They can also end up in a data interchange XML schema (I bumped into that one at a previous job where it seemed like an obvious and trivial fix to correct the spelling of a class name and discovered that it had ended up in a company-wide data interchange schema which could not be practically fixed).

The most important example of that class of error is REFERER. It should have been spelled REFERRER. But nobody caught it, and you really can't change something that is part of the HTTP standard...

Re: Apple agrees to settle potential class action suit by U.S. developers

#117
A more suitable headline for the original article would have been: "US developers' lawyers agree to settle potential class action suit". I wish they didn't. There are important and rather easy wins to be attained (e.g. I don't see how the Apple Payment requirement could survive a trial).

Developers could still object to the settlement[0]. That way, Apple will still be bound by its concessions, while the suit goes forward.

[0] https://news.ycombinator.com/item?id=28323992

Re: Apple agrees to settle potential class action suit by U.S. developers

#119

I don't understand why the App Store, this small "side business" in the grand scheme of things, is something Apple is worth fighting and dying over. It's literally, a small fraction of their revenue, and yet it grabs 80% of the bad PR and is now under investigation and proposed legislation in the US, UK, EU, Korea, and I think Australia. If I'm Apple, shouldn't it be obvious at this point that losing the App Store mo…

At this point, I don't think it's an economic calculation anymore, if it ever was. I think it's moreso that Apple genuinely believes that third parties shouldn't have access to their platforms without prior review. Everything else has an explanation from that: - We need to monopolize control over who can publish software for our platforms, so we can enforce our security guidelines. (This includes banning third-party…

>- Thus, we can't have third-party billing, because that would let developers evade payment for our software review.

Except for having to buy a Mac to do development in the first place. And the developer registration yearly fee.

Re: Apple agrees to settle potential class action suit by U.S. developers

#120
post #60

Earlier quoted context omitted.

I can feel your frustration, but it also strikes me as tone-deaf to those very same customers. The most common kind of email I send these days—by orders of magnitude—is “unsubscribe”. I don’t want your emails unless I actively asked for them. (And, no, passively being opted in or being forced to opt in by a user agreement or whatever doesn’t count.) I would happily pay middle men a lot extra to get fewer unwanted ema…

> I would happily pay middle men a lot extra to get fewer unwanted emails, phone calls, or just generally more privacy. My life has changed significantly for the better ever since I signed up for this: http://33mail.com/AQwZJR3 The real trick is using a custom domain so A) They’re very unlikely to add it to their disposable email list (and thus block it) B) If this service ever goes under you can still get the emails…

On the flip side for Apple users we get up 100 Hide My Emails in iOS 15 with the same functionality.
Post reply on HN