I don’t think it’s too much to expect Apple to communicate more openly about when they get increased levels of complaints and their devs are working on a fix. No need to hold back.īut IMHO that does not exclude being more upfront about ongoing issues. People who actually read those can be expected to be interested and somewhat savvy. I agree with Adam that release notes should be improved. Some updates are fairly well described, but many others are just “general performance and stability improvements.” In the end, I’d settle for better release notes when the updates come out. I suspect that it’s not seen as being all that helpful, particularly if they believe the percentage of affected users is quite small. You can report bugs to Apple, and occasionally you’ll get a response that will indicate they know about the bug or are even working on it, but that’s not a great channel either-it would be an insane amount of work to track what’s happening in development and notify everyone who had reported a particular problem.Īnd arguably, the development teams could publish this information, but they’d need to set up and manage an entirely new communication channel to do this. If there is a known fix coming, they’ll tell you that when you call in. The question here is, exactly who is “Apple” and how would they communicate this information? Often, when you talk to a support rep, they’ll tell you if they’re hearing from a lot of customers about the problem, but they can’t know what the development team is working on and the schedule for any fixes, since the company is just far too big. I wish I knew why Apple won’t just acknowledge issues with an OS version (in this case, the charging issue with the XS models, the WiFi issue with the XS models) and say that they are working on and testing an update that they hope to deliver soon rather than ignoring the issue.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |