How to leave product feedback on macOS?Reasons to Stay with Safari BrowserFinding CodeBlocks that works or fixing bugs?How do I disable/configure macOS Sierra's auto throttling of the CPU for processor intensive tasksHow can I provide useful feedback to Mac Photos software designers?macOS Sierra language switch HUDWhat does it mean for consumers that Apple has released MacOS kernel as open source?macOS: What is this mysterious white window?MacBook Pro Touch Bar 2016 Haptic feedback not workingUse F1, F2 etc. keys to control built-in Mac features when using an external USB keyboardHow to open macOS news article in browser?
What does "tick" mean in this sentence?
How to Disable and Drop all Temporal Tables from a database
Why does a 97 / 92 key piano exist by Bösendorfer?
Should I warn a new PhD Student?
Anime with legendary swords made from talismans and a man who could change them with a shattered body
If the only attacker is removed from combat, is a creature still counted as having attacked this turn?
Identifying "long and narrow" polygons in with Postgis
How to make money from a browser who sees 5 seconds into the future of any web page?
How to write Quadratic equation with negative coefficient
Limit max CPU usage SQL SERVER with WSRM
How can I, as DM, avoid the Conga Line of Death occurring when implementing some form of flanking rule?
How much do grades matter for a future academia position?
What does the word 'upstream' mean in the context?
Would a primitive species be able to learn English from reading books alone?
Why is the sun approximated as a black body at ~ 5800 K?
Giving feedback to someone without sounding prejudiced
Pre-Employment Background Check With Consent For Future Checks
Why the "ls" command is showing the permissions of files in a FAT32 partition?
Why didn't Voldemort know what Grindelwald looked like?
What is the meaning of "You've never met a graph you didn't like?"
Determining multivariate least squares with constraint
Showing mass murder in a kid's book
Why do Radio Buttons not fill the entire outer circle?
SOQL query causes internal Salesforce error
How to leave product feedback on macOS?
Reasons to Stay with Safari BrowserFinding CodeBlocks that works or fixing bugs?How do I disable/configure macOS Sierra's auto throttling of the CPU for processor intensive tasksHow can I provide useful feedback to Mac Photos software designers?macOS Sierra language switch HUDWhat does it mean for consumers that Apple has released MacOS kernel as open source?macOS: What is this mysterious white window?MacBook Pro Touch Bar 2016 Haptic feedback not workingUse F1, F2 etc. keys to control built-in Mac features when using an external USB keyboardHow to open macOS news article in browser?
I love how Microsoft products have built-in customer feedback (click the smiley face) and wish I could do the same with Apple products, especially macOS.
What is the fastest way to provide feedback on macOS features and bugs?
macos bug applecare support
add a comment |
I love how Microsoft products have built-in customer feedback (click the smiley face) and wish I could do the same with Apple products, especially macOS.
What is the fastest way to provide feedback on macOS features and bugs?
macos bug applecare support
add a comment |
I love how Microsoft products have built-in customer feedback (click the smiley face) and wish I could do the same with Apple products, especially macOS.
What is the fastest way to provide feedback on macOS features and bugs?
macos bug applecare support
I love how Microsoft products have built-in customer feedback (click the smiley face) and wish I could do the same with Apple products, especially macOS.
What is the fastest way to provide feedback on macOS features and bugs?
macos bug applecare support
macos bug applecare support
edited 11 mins ago
bmike♦
160k46287622
160k46287622
asked 1 hour ago
CrowderCrowder
1,89931233
1,89931233
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Apple hosts a dedicated webpage on its website to share product feedback:
- Product Feedback - Apple
Use the above link to share general product feedback with Apple regarding various hardware and software products.
If that doesn't suffice your need, and you'd like to either report bug(s) or request new feature(s), you can do so via dedicated bug reporter here:
- Apple Bug Reporter
You'll need to log in with an Apple ID to do so.
Bug Reporter is preferred, as the concern will be directed to the relevant product team, and you'll most likely get a feedback regarding the status from them.
Also, a new feature request or a bug fix is most likely to happen, contingent to the number of unique bug reports filed. So, Bug Reporter is preferred over Product feedback page.
Filing a bug report is termed as filing a Radar in Apple.
P.S.: There's an official webpage outlining recommended best practises when sharing product feedback and bug reports with Apple. The same can be accessed here:
- Bug Reporting - Apple Developer
Thanks. This form is really dated. I have to tell them what my OS is. Definitely prefer Microsoft's contextual feedback model—I assume they're able to pull that information from my Mac without needing to ask me.
– Crowder
1 hour ago
@Crowder I have included the link to and some description about Radar, Apple's bug reporter used both internally and externally. That should better address your concern.
– Nimesh Neema
1 hour ago
1
@Crowder It's not realistic to assume Apple would pull any info from your mac. When reporting problems best to provide everything needed for someone to reproduce it without any knowledge about who it came from.
– Tom Gewecke
56 mins ago
1
I wouldn’t start with any of these. 8 to 10 years ago these were the only way, support is far better now remotely (and far worse in store via Genius Bar)
– bmike♦
12 mins ago
add a comment |
The fastest way is on twitter and the support webpage and iOS app. The old bug reporter and feedback mechanisms are there too, but the analogous fast and human interaction method of support is to ping Apple’s customer support and relations staff directly.
I find asking for guidance and training works better than ranting about how awful a bug is, but I’ve seen both get really professional guidance and started using that over the traditional Genius Bar and Apple support pages. Also, often I just didn’t realize how to do something and they’ve been forthcoming when what I face is legitimately a design decision where I need to offer feedback on my use case and why their design decision wasn’t optimal for me. Same with bugs, support can and will escalate to engineering if you don’t have another support path in place as a developer or business partner.
If it’s a bug, you’ll want to bring reproducible steps or ask how to collect the logs they need to analyze the failure. They will steer you to the appropriate avenue whether it’s understnading the feature or asking for traditional feedback or working with AppleCare support to isolate the issue.
I always start with support, then go where they direct:
- https://support.apple.com/
- https://twitter.com/AppleSupport
- https://itunes.apple.com/us/app/apple-support/id1130498044
Some of those links are in the support pane of About this Mac as well if you prefer to click something from apple directly. The iOS support app is really nice as well, in my experience. It integrates with iMessage and call back quite effortlessly.
+1 for noting the faster methods.
– Nimesh Neema
11 mins ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "118"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f354360%2fhow-to-leave-product-feedback-on-macos%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Apple hosts a dedicated webpage on its website to share product feedback:
- Product Feedback - Apple
Use the above link to share general product feedback with Apple regarding various hardware and software products.
If that doesn't suffice your need, and you'd like to either report bug(s) or request new feature(s), you can do so via dedicated bug reporter here:
- Apple Bug Reporter
You'll need to log in with an Apple ID to do so.
Bug Reporter is preferred, as the concern will be directed to the relevant product team, and you'll most likely get a feedback regarding the status from them.
Also, a new feature request or a bug fix is most likely to happen, contingent to the number of unique bug reports filed. So, Bug Reporter is preferred over Product feedback page.
Filing a bug report is termed as filing a Radar in Apple.
P.S.: There's an official webpage outlining recommended best practises when sharing product feedback and bug reports with Apple. The same can be accessed here:
- Bug Reporting - Apple Developer
Thanks. This form is really dated. I have to tell them what my OS is. Definitely prefer Microsoft's contextual feedback model—I assume they're able to pull that information from my Mac without needing to ask me.
– Crowder
1 hour ago
@Crowder I have included the link to and some description about Radar, Apple's bug reporter used both internally and externally. That should better address your concern.
– Nimesh Neema
1 hour ago
1
@Crowder It's not realistic to assume Apple would pull any info from your mac. When reporting problems best to provide everything needed for someone to reproduce it without any knowledge about who it came from.
– Tom Gewecke
56 mins ago
1
I wouldn’t start with any of these. 8 to 10 years ago these were the only way, support is far better now remotely (and far worse in store via Genius Bar)
– bmike♦
12 mins ago
add a comment |
Apple hosts a dedicated webpage on its website to share product feedback:
- Product Feedback - Apple
Use the above link to share general product feedback with Apple regarding various hardware and software products.
If that doesn't suffice your need, and you'd like to either report bug(s) or request new feature(s), you can do so via dedicated bug reporter here:
- Apple Bug Reporter
You'll need to log in with an Apple ID to do so.
Bug Reporter is preferred, as the concern will be directed to the relevant product team, and you'll most likely get a feedback regarding the status from them.
Also, a new feature request or a bug fix is most likely to happen, contingent to the number of unique bug reports filed. So, Bug Reporter is preferred over Product feedback page.
Filing a bug report is termed as filing a Radar in Apple.
P.S.: There's an official webpage outlining recommended best practises when sharing product feedback and bug reports with Apple. The same can be accessed here:
- Bug Reporting - Apple Developer
Thanks. This form is really dated. I have to tell them what my OS is. Definitely prefer Microsoft's contextual feedback model—I assume they're able to pull that information from my Mac without needing to ask me.
– Crowder
1 hour ago
@Crowder I have included the link to and some description about Radar, Apple's bug reporter used both internally and externally. That should better address your concern.
– Nimesh Neema
1 hour ago
1
@Crowder It's not realistic to assume Apple would pull any info from your mac. When reporting problems best to provide everything needed for someone to reproduce it without any knowledge about who it came from.
– Tom Gewecke
56 mins ago
1
I wouldn’t start with any of these. 8 to 10 years ago these were the only way, support is far better now remotely (and far worse in store via Genius Bar)
– bmike♦
12 mins ago
add a comment |
Apple hosts a dedicated webpage on its website to share product feedback:
- Product Feedback - Apple
Use the above link to share general product feedback with Apple regarding various hardware and software products.
If that doesn't suffice your need, and you'd like to either report bug(s) or request new feature(s), you can do so via dedicated bug reporter here:
- Apple Bug Reporter
You'll need to log in with an Apple ID to do so.
Bug Reporter is preferred, as the concern will be directed to the relevant product team, and you'll most likely get a feedback regarding the status from them.
Also, a new feature request or a bug fix is most likely to happen, contingent to the number of unique bug reports filed. So, Bug Reporter is preferred over Product feedback page.
Filing a bug report is termed as filing a Radar in Apple.
P.S.: There's an official webpage outlining recommended best practises when sharing product feedback and bug reports with Apple. The same can be accessed here:
- Bug Reporting - Apple Developer
Apple hosts a dedicated webpage on its website to share product feedback:
- Product Feedback - Apple
Use the above link to share general product feedback with Apple regarding various hardware and software products.
If that doesn't suffice your need, and you'd like to either report bug(s) or request new feature(s), you can do so via dedicated bug reporter here:
- Apple Bug Reporter
You'll need to log in with an Apple ID to do so.
Bug Reporter is preferred, as the concern will be directed to the relevant product team, and you'll most likely get a feedback regarding the status from them.
Also, a new feature request or a bug fix is most likely to happen, contingent to the number of unique bug reports filed. So, Bug Reporter is preferred over Product feedback page.
Filing a bug report is termed as filing a Radar in Apple.
P.S.: There's an official webpage outlining recommended best practises when sharing product feedback and bug reports with Apple. The same can be accessed here:
- Bug Reporting - Apple Developer
edited 26 mins ago
answered 1 hour ago
Nimesh NeemaNimesh Neema
15.6k74377
15.6k74377
Thanks. This form is really dated. I have to tell them what my OS is. Definitely prefer Microsoft's contextual feedback model—I assume they're able to pull that information from my Mac without needing to ask me.
– Crowder
1 hour ago
@Crowder I have included the link to and some description about Radar, Apple's bug reporter used both internally and externally. That should better address your concern.
– Nimesh Neema
1 hour ago
1
@Crowder It's not realistic to assume Apple would pull any info from your mac. When reporting problems best to provide everything needed for someone to reproduce it without any knowledge about who it came from.
– Tom Gewecke
56 mins ago
1
I wouldn’t start with any of these. 8 to 10 years ago these were the only way, support is far better now remotely (and far worse in store via Genius Bar)
– bmike♦
12 mins ago
add a comment |
Thanks. This form is really dated. I have to tell them what my OS is. Definitely prefer Microsoft's contextual feedback model—I assume they're able to pull that information from my Mac without needing to ask me.
– Crowder
1 hour ago
@Crowder I have included the link to and some description about Radar, Apple's bug reporter used both internally and externally. That should better address your concern.
– Nimesh Neema
1 hour ago
1
@Crowder It's not realistic to assume Apple would pull any info from your mac. When reporting problems best to provide everything needed for someone to reproduce it without any knowledge about who it came from.
– Tom Gewecke
56 mins ago
1
I wouldn’t start with any of these. 8 to 10 years ago these were the only way, support is far better now remotely (and far worse in store via Genius Bar)
– bmike♦
12 mins ago
Thanks. This form is really dated. I have to tell them what my OS is. Definitely prefer Microsoft's contextual feedback model—I assume they're able to pull that information from my Mac without needing to ask me.
– Crowder
1 hour ago
Thanks. This form is really dated. I have to tell them what my OS is. Definitely prefer Microsoft's contextual feedback model—I assume they're able to pull that information from my Mac without needing to ask me.
– Crowder
1 hour ago
@Crowder I have included the link to and some description about Radar, Apple's bug reporter used both internally and externally. That should better address your concern.
– Nimesh Neema
1 hour ago
@Crowder I have included the link to and some description about Radar, Apple's bug reporter used both internally and externally. That should better address your concern.
– Nimesh Neema
1 hour ago
1
1
@Crowder It's not realistic to assume Apple would pull any info from your mac. When reporting problems best to provide everything needed for someone to reproduce it without any knowledge about who it came from.
– Tom Gewecke
56 mins ago
@Crowder It's not realistic to assume Apple would pull any info from your mac. When reporting problems best to provide everything needed for someone to reproduce it without any knowledge about who it came from.
– Tom Gewecke
56 mins ago
1
1
I wouldn’t start with any of these. 8 to 10 years ago these were the only way, support is far better now remotely (and far worse in store via Genius Bar)
– bmike♦
12 mins ago
I wouldn’t start with any of these. 8 to 10 years ago these were the only way, support is far better now remotely (and far worse in store via Genius Bar)
– bmike♦
12 mins ago
add a comment |
The fastest way is on twitter and the support webpage and iOS app. The old bug reporter and feedback mechanisms are there too, but the analogous fast and human interaction method of support is to ping Apple’s customer support and relations staff directly.
I find asking for guidance and training works better than ranting about how awful a bug is, but I’ve seen both get really professional guidance and started using that over the traditional Genius Bar and Apple support pages. Also, often I just didn’t realize how to do something and they’ve been forthcoming when what I face is legitimately a design decision where I need to offer feedback on my use case and why their design decision wasn’t optimal for me. Same with bugs, support can and will escalate to engineering if you don’t have another support path in place as a developer or business partner.
If it’s a bug, you’ll want to bring reproducible steps or ask how to collect the logs they need to analyze the failure. They will steer you to the appropriate avenue whether it’s understnading the feature or asking for traditional feedback or working with AppleCare support to isolate the issue.
I always start with support, then go where they direct:
- https://support.apple.com/
- https://twitter.com/AppleSupport
- https://itunes.apple.com/us/app/apple-support/id1130498044
Some of those links are in the support pane of About this Mac as well if you prefer to click something from apple directly. The iOS support app is really nice as well, in my experience. It integrates with iMessage and call back quite effortlessly.
+1 for noting the faster methods.
– Nimesh Neema
11 mins ago
add a comment |
The fastest way is on twitter and the support webpage and iOS app. The old bug reporter and feedback mechanisms are there too, but the analogous fast and human interaction method of support is to ping Apple’s customer support and relations staff directly.
I find asking for guidance and training works better than ranting about how awful a bug is, but I’ve seen both get really professional guidance and started using that over the traditional Genius Bar and Apple support pages. Also, often I just didn’t realize how to do something and they’ve been forthcoming when what I face is legitimately a design decision where I need to offer feedback on my use case and why their design decision wasn’t optimal for me. Same with bugs, support can and will escalate to engineering if you don’t have another support path in place as a developer or business partner.
If it’s a bug, you’ll want to bring reproducible steps or ask how to collect the logs they need to analyze the failure. They will steer you to the appropriate avenue whether it’s understnading the feature or asking for traditional feedback or working with AppleCare support to isolate the issue.
I always start with support, then go where they direct:
- https://support.apple.com/
- https://twitter.com/AppleSupport
- https://itunes.apple.com/us/app/apple-support/id1130498044
Some of those links are in the support pane of About this Mac as well if you prefer to click something from apple directly. The iOS support app is really nice as well, in my experience. It integrates with iMessage and call back quite effortlessly.
+1 for noting the faster methods.
– Nimesh Neema
11 mins ago
add a comment |
The fastest way is on twitter and the support webpage and iOS app. The old bug reporter and feedback mechanisms are there too, but the analogous fast and human interaction method of support is to ping Apple’s customer support and relations staff directly.
I find asking for guidance and training works better than ranting about how awful a bug is, but I’ve seen both get really professional guidance and started using that over the traditional Genius Bar and Apple support pages. Also, often I just didn’t realize how to do something and they’ve been forthcoming when what I face is legitimately a design decision where I need to offer feedback on my use case and why their design decision wasn’t optimal for me. Same with bugs, support can and will escalate to engineering if you don’t have another support path in place as a developer or business partner.
If it’s a bug, you’ll want to bring reproducible steps or ask how to collect the logs they need to analyze the failure. They will steer you to the appropriate avenue whether it’s understnading the feature or asking for traditional feedback or working with AppleCare support to isolate the issue.
I always start with support, then go where they direct:
- https://support.apple.com/
- https://twitter.com/AppleSupport
- https://itunes.apple.com/us/app/apple-support/id1130498044
Some of those links are in the support pane of About this Mac as well if you prefer to click something from apple directly. The iOS support app is really nice as well, in my experience. It integrates with iMessage and call back quite effortlessly.
The fastest way is on twitter and the support webpage and iOS app. The old bug reporter and feedback mechanisms are there too, but the analogous fast and human interaction method of support is to ping Apple’s customer support and relations staff directly.
I find asking for guidance and training works better than ranting about how awful a bug is, but I’ve seen both get really professional guidance and started using that over the traditional Genius Bar and Apple support pages. Also, often I just didn’t realize how to do something and they’ve been forthcoming when what I face is legitimately a design decision where I need to offer feedback on my use case and why their design decision wasn’t optimal for me. Same with bugs, support can and will escalate to engineering if you don’t have another support path in place as a developer or business partner.
If it’s a bug, you’ll want to bring reproducible steps or ask how to collect the logs they need to analyze the failure. They will steer you to the appropriate avenue whether it’s understnading the feature or asking for traditional feedback or working with AppleCare support to isolate the issue.
I always start with support, then go where they direct:
- https://support.apple.com/
- https://twitter.com/AppleSupport
- https://itunes.apple.com/us/app/apple-support/id1130498044
Some of those links are in the support pane of About this Mac as well if you prefer to click something from apple directly. The iOS support app is really nice as well, in my experience. It integrates with iMessage and call back quite effortlessly.
answered 13 mins ago
bmike♦bmike
160k46287622
160k46287622
+1 for noting the faster methods.
– Nimesh Neema
11 mins ago
add a comment |
+1 for noting the faster methods.
– Nimesh Neema
11 mins ago
+1 for noting the faster methods.
– Nimesh Neema
11 mins ago
+1 for noting the faster methods.
– Nimesh Neema
11 mins ago
add a comment |
Thanks for contributing an answer to Ask Different!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f354360%2fhow-to-leave-product-feedback-on-macos%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown