4 ms·
Look, this is just going to fall on deaf ears. Apple isn't listening. Their machine is output only. That's not really true. Apple is active on Twitter and acti
by sillysaurusx 7y ago
Look, this is just going to fall on deaf ears. Apple isn't listening. Their machine is output only.
That's not really true. Apple is active on Twitter and actively reaches out to correct problems.
For example, when I complained that their Xcode beta hangs when you open a large file, an Xcode dev reached out to me and asked for a repro case. https://twitter.com/theshawwn/status/1175197286349119490 https://twitter.com/theshawwn/status/1175197286349119490
(I'm not an Apple fanboy, just a dev.)
- AlexandrB 7y agoIsn't that the exception that proves the rule though? Why is Twitter the most effective way to get developer support from Apple as opposed to their own website?
- 52-6F-62 7y agoYeah. As much as I appreciate their responsiveness on Twitter, it doesn't much help those of us who are not on Twitter. (Tangential rant: I dislike how it seems like the most effective path for anything resembling customer service from many companies is to call them out on Twitter alone. I've written emails to some companies over months to no single response—but to look on their Twitter you'll see an answer within hours, or minutes.)
- dnautics 7y agoThat shouldn't be surprising as Twitter is a public forum, so there's more accountability.
- 52-6F-62 7y agoI'm not surprised. I'm a bit miffed, though. We shouldn't have to shame companies to get a bit of customer service—let alone a response to an email.
- revscat 7y agoI get what you're saying -- that companies should be internally driven to address concerns such as yours -- but I'm starting to shift away from that thinking. We're social apes. We evolved in groups, and respond to group pressures. Responding to public shaming is perhaps a more natural state of things than what we tend to expect. It certainly seems more effective.
- 52-6F-62 7y agoIt's the dirty road, though. In capitalism the market is supposed to correct for bad acting like poor customer service. Instead it's a public haranguing like putting someone in the stocks, except in exponentially less response time.
- sosborn 7y ago> In capitalism the market is supposed to correct for bad acting like poor customer service. That only works when the public knows that the customer service experience is poor. I'm no fan of Twitter, but putting this stuff in the open is incredible effective for this reason.
- Ensorceled 7y agoYes, pretty much every company is this way. I often get a response, support ticket and solution via Twitter before my email/webform request is even processed.
- Rebelgecko 7y agoReminds me of this post from a few days ago: https://news.ycombinator.com/item?id=21324798 https://news.ycombinator.com/item?id=21324798 tl;dr: Recent performance improvements in the Mac version of Firefox are dependent on an undocumented feature of an API that was tweeted out by someone from Apple
- _jal 7y agoTaking bug reports on Twitter is nice, but not comparable to improving documentation. One is a developer reaching out (costs: developer time, management involvement: granting permission). The other is a change in project plans, staffing, workflow and timelines (costs: large, management involvement: massive).
- w0utert 7y ago>> One is a developer reaching out (costs: developer time, management involvement: granting permission). The other is a change in project plans, staffing, workflow and timelines (costs: large, management involvement: massive). I think it's a pretty safe bet to expect, for this reason alone, that the documentation quality of things like SwiftUI will improve over time. It seems pretty obvious they directed all their efforts to releasing SwiftUI within their iOS 13 release window, which likely meant the API only 'stabilized' very late in the process and it would be impossible to spend time and resources documenting it, at least not without postponing the release (not an option). Generally speaking, in my experience all of the 'established' Apple API's have pretty good documentation. SwiftUI seems rushed, and it would probably been better if they waited until iOS 14 and release it along with documentation. I'm not definding Apple here, but I think the article is overstating how bad their documentation is based on one brand-new API that probably wasn't fully cooked for release to begin with.
- mpweiher 7y agoAs far as I can tell, this is individual developers reaching out, possibly at risk violating company policy. They do it anyway, and should be commended, but this isn't Apple per se.