undefined | Better HN

0 pointsBoorishBears6y ago0 comments

How is it going to make customers unhappy if your app isn't using the features?

Apple is within their rights here, but please, let's not pretend this is about user experience.

It's about the Apple machine doing what it wants, and rolling over who it wants, because it can.

That would explain why Apple developer relations (read: humans) had previously backpedalled after the same rejection in the past:

https://github.com/electron/electron/issues/20027

Most likely these rejections were not intentionally resumed, but because the machine that is app stores these days is completely non-deterministic, this could still be a big problem.

This time the wrong developer could reach out to the wrong channel and trip some sort of trap that turns this into a "known issue: won't fix + always send automated reply", instead of someone with the right connections getting to the right person and having them go and flip a switch that fixes everything with their pinky finger.

0 comments

2 comments · 1 top-level

philwelch6y ago· 1 in thread

It’s more of a general point that if your application is buggy, the customer isn’t going to give a damn whether the bug is in your code or in somebody else’s code.

BoorishBearsOP6y ago

And? That's exactly why internal APIs should be allowed.

The problem isn't the usage of an internal API, the problem is the breaking of an internal API.

Which is already covered by App Store testing and guidelines which already require your app isn't a broken mess.

j / k navigate · click thread line to collapse