Live data from Hacker News

Apple developer boycott of Feedback Assistant

lapcatsoftware.com

71–80 of 130 posts

Re: Apple developer boycott of Feedback Assistant

#71
post #39
post #20

Earlier quoted context omitted.

Almost every time, developer technical support will look at the internal bug and if there is no known workaround will say “sorry that’s our bug and engineering is investigating, we don’t have anything to tell you, please keep an eye on the feedback and we will update you if anything changes - in the meantime here’s your TSI refunded”.

In that process though, you’ve had someone at Apple verify that your issue is legitimate, and that issue has probably shown up in a place they care about (DTS metrics) Two things that simply filing a feedback issue doesn’t seem to reliably do. I’m suspect a concerted effort to get developers using their TSIs for bug reporting would backfire (stop refunding them? remove the program?), but I think it’s an interesting i…

Sure and I don’t mean to minimise the value/effort - I’m sure the “look at” may involve actually investigating the issue themselves by looking at the implementation, speaking with the responsible engineers, etc. I am also sure it is a hard problem to solve - while Apple is massive and well resourced these days their developer community is also humongous and I am sure there is a tremendous amount of noise. But my point is merely - TSIs are not a panacea

Re: Apple developer boycott of Feedback Assistant

#73
post #15

The recent macOS dialog "Allow app to access folder [OK] [Cancel]" supports button cycling by Shift+Tab (previous), but not Tab (next). The Wi-Fi signal strength indication changes when clicking it. So yeah, at least they need to admit things are very bad over there.

these arent the heavy HN apple blinders these threads usually get!

but yea its pretty bad. i cant go 1 day without a blatant ui bug lightly using apple products at work

Re: Apple developer boycott of Feedback Assistant

#74

Earlier quoted context omitted.

Ideally, daily BRBs (kept to an hour) with engineers attending. If it turns out there are too many Radars to keep the BRBs to an hour then there are issues elsewhere. At the same time, I didn't mention it above, engineers need to be allowed time in the product schedule to fix these bugs. As probably everyone knows, when a bug is kicked down the road once (because of scheduling constraints: hey, we gotta ship the soft…

Incentivize screening Radars (and fixing them). There's no engineering glory in keeping your unscreened count at zero... nobody gets promoted for it.

Good point.

Re: Apple developer boycott of Feedback Assistant

#75
post #60

As a developer, I flatly refuse to engage with Apple in any way because of their $100 annual fee. I feel especially vindicated when stuff like this surfaces. Imagine being the richest company in the world and having the audacity to charge people for the privilege of being able to contribute to your platform. It is absolutely insane, and nothing will convince me otherwise.

while i agree with your sentiment, i think Apple would probably argue that they're actually charging for access to their distribution network.

Re: Apple developer boycott of Feedback Assistant

#77
I previously blogged about how Apple treat web developers with negligence when it comes to Safari [1]. This makes it looks like Apple treat other developers with negligence as well, which is unsurprising, frankly.

[1] https://www.construct.net/en/blogs/ashleys-blog-2/safari-rel...

Re: Apple developer boycott of Feedback Assistant

#78

Boycotts/strikes* only work if most or nearly all people participate, because you'll only participate if you're pretty sure nearly everyone else is too. While if this blogpost merely gets 0.1% of developers to strike... Apple couldn't care less. I think this developer strike is a great idea, but launching it as a single person 's call to action (Jeff Johnson's) is not generally going to be effective in changing behav…

Fundamentally, such a strike assumes Apple cares about the free reports they get from their developers. I'm not sure that's true. And even if it is, it's not like they don't have enough other reports or features to work on, so the loss of all outside bug reporting probably wouldn't affect them at all.

Re: Apple developer boycott of Feedback Assistant

#79
post #62

Earlier quoted context omitted.

How are you supposed to find a developer inside Apple to fix your issue?

It is possible to backchannel to them like any other company. It's just much less... publicly evident, if that makes sense? Also (IIRC) if you post on their dev forums and deal with e.g Quinn, they might ask you to file and provide a radar - but it's been a minute since I've interacted over there.

That guy Quinn "The Eskimo" seems to have been almost singlehandedly manning the developer forums at Apple for over a decade. I hope Apple recognises how valuable he is.

Re: Apple developer boycott of Feedback Assistant

#80
post #50

Earlier quoted context omitted.

I never thought I'd wistfully look back on Steve Ballmer yelling DEVELOPERS! DEVELOPERS! DEVELOPERS!!! Apple seem to view external developers as a kind of infestation. The systems and processes they subject them to seem designed to actively discourage them.

I always find it funny to see Apple pushing for tech education when it's well known that Apple despises developers. Please teach your kids computer science so we can treat them like shit and/or exploit them! They used to (or still do?) have coding courses for kids at Apple stores, they have free learn to code resources ( https://developer.apple.com/learn/ ), probably some more programs I'm not familiar with.

[deleted]
Post reply on HN