Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

axios.com

Post reply on HN
Print view View original

161–170 of 259 posts

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

#161

Post by hurflmurfl »

monocasa wrote: post #148
mynegation wrote: post #54

Earlier quoted context omitted.

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.

As a dev with dyslexia, I apologize. I've for sure committed some sins there in places that are nasty to fix.

Well, pasting the enum example into IntelliJ highlighted the spelling mistakes and suggested replacing NINTEY and NINETEY with NINETY. I think this is how my dyslexic colleague works too - copy pasting instead of writing and looking for various wiggly lines in code editor.

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

#162

Post by sfifs »

jsnell wrote: post #44
liquidise wrote: post #39

> Developers can communicate directly with customers about alternative payment options. Customers have to consent and be given the right to opt-out. This is a huge step forward (though it falls well short of the ideal case) for iOS development. Having the ability to tell customers about other, often cheaper, payment methods removes a substantial barrier for some apps that have high-priced subscriptions. Positive as t…

What do you think the step forward is here? The developers are still not allowed to communicate about alternate purchase options in the app, they would need to have some other form of communication with the user. Such advertising via side-channels was never forbidden, it's just that it's impractical for most developers to establish that side-channel. I really have to congratulate whoever wrote that press release. The…

> The developers are still not allowed to communicate about alternate purchase options in the app, they would need to have some other form of communication with the user.

I'm pretty sure this "anti-steering" restriction in-app will go away with the Epic vs. Apple ruling. It's classic "tying" in anti-trust. Nothing else in that case might go Epic's way, but this likely will.

I'm also pretty sure every major player generating in-app revenue already has already developed their cheaper payment alternative to rollout the minute the ruling drops, so Apple will have to hustle to get a stay order.

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

#163

Post by realityking »

alkonaut wrote: post #141
saagarjha wrote: post #135

Earlier quoted context omitted.

They are already allowed to be cheaper. This is just saying you can email people about it outside of the app.

So Spotify still can’t say front and center in the app ”Buy subscription in app: $12/mo or click here to purchase on Spotify dot com for $10”? They have to show only the $12 in the app?

That’s my understanding, yes.

What they can now do is, if you sign-up for a free Spotify account using their app they can send you an email advertising the $10 subscription. In the past they could’ve only sent an email advertising the $12 one.

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

#164

Post by [deleted] »

alkonaut wrote: post #141
saagarjha wrote: post #135

Earlier quoted context omitted.

They are already allowed to be cheaper. This is just saying you can email people about it outside of the app.

So Spotify still can’t say front and center in the app ”Buy subscription in app: $12/mo or click here to purchase on Spotify dot com for $10”? They have to show only the $12 in the app?

[deleted]

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

#165

Post by [deleted] »

mynegation wrote: post #54
jrockway wrote: post #48

> 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.

[deleted]

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

#166

Post by jacquesm »

Meanwhile, as long as you understand that you are allowed to sell your wares to Apples customers - and not yours - you may proceed. This is the key element, that Apple continues to own the customer relationship, rather than that your customers make use of their eco-system and hardware.

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

#167

Post by bumblebritches5 »

gambiting wrote: post #149
mynegation wrote: post #54

Earlier quoted context omitted.

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.

In a triple A game I worked on, the PlayStation button enums were CROSS, SQUARE, TRIANGLE, and...... CRIRCLE. Would drive me absolutely livid. But of course no one was allowed to fix is since it was already in a few different games, countless script files, network-controlled configs etc.....

Dumb, they should've just added a CIRCLE = CRIRCLE option

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

#168

Post by kar1181 »

skybrian wrote: post #30
balozi wrote: post #22

I guess you can look forward to a check for $2.12 in the mail. Feels like Apple's highfalutin way of mocking devs.

From the article, minimum payment is $250.

Hopefully that actually hits someone's bank account unlike the Equifax settlement which only really hit the laywers'

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

#169

Post by hnlmorg »

gambiting wrote: post #149
mynegation wrote: post #54

Earlier quoted context omitted.

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.

In a triple A game I worked on, the PlayStation button enums were CROSS, SQUARE, TRIANGLE, and...... CRIRCLE. Would drive me absolutely livid. But of course no one was allowed to fix is since it was already in a few different games, countless script files, network-controlled configs etc.....

I feel your pain. A company I work for has a weird name that doesn't follow the rules of English spelling correctly (I can't say more without giving away the company name). This was an intentional decision and poses enough of a problem for guests visiting the company. But the absurd thing is this company decides to double down on it's troubles by naming all of it's projects using the same broken rule as the company title. Often these projects will be common English words re-spelt in the style of the company name. So now I'm often finding myself misspelling common words because of this stupid company name. And all of this is intentional too! Drives me nuts.

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

#170

Post by Razengan »

btilly wrote: post #116
dhosek wrote: post #97

Earlier quoted context omitted.

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...

At this point I think it may be question whether the problem lies with English itself. Such an error prone language.
Post reply on HN