How to leave product feedback on macOS? [duplicate]How should I submit bug reports and feature requests?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 to do when eye contact makes your coworker uncomfortable?
What kind of floor tile is this?
Can I cause damage to electrical appliances by unplugging them when they are turned on?
Why do Radio Buttons not fill the entire outer circle?
How much of a Devil Fruit must be consumed to gain the power?
How to convince somebody that he is fit for something else, but not this job?
Delete multiple columns using awk or sed
awk assign to multiple variables at once
The Digit Triangles
Is it necessary to use pronouns with the verb "essere"?
Can you use Vicious Mockery to win an argument or gain favours?
How would you translate "more" for use as an interface button?
What features enable the Su-25 Frogfoot to operate with such a wide variety of fuels?
Is there a RAID 0 Equivalent for RAM?
Why does AES have exactly 10 rounds for a 128-bit key, 12 for 192 bits and 14 for a 256-bit key size?
Giving feedback to someone without sounding prejudiced
PTIJ: Why is Haman obsessed with Bose?
Mimic lecturing on blackboard, facing audience
Why is the "ls" command showing permissions of files in a FAT32 partition?
Microchip documentation does not label CAN buss pins on micro controller pinout diagram
Why should universal income be universal?
Why is the Sun approximated as a black body at ~ 5800 K?
A Trivial Diagnosis
What does "Scientists rise up against statistical significance" mean? (Comment in Nature)
How to leave product feedback on macOS? [duplicate]
How should I submit bug reports and feature requests?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?
This question already has an answer here:
How should I submit bug reports and feature requests?
1 answer
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
marked as duplicate by nohillside♦
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
19 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
How should I submit bug reports and feature requests?
1 answer
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
marked as duplicate by nohillside♦
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
19 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
How should I submit bug reports and feature requests?
1 answer
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
This question already has an answer here:
How should I submit bug reports and feature requests?
1 answer
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?
This question already has an answer here:
How should I submit bug reports and feature requests?
1 answer
macos bug applecare support
macos bug applecare support
edited yesterday


bmike♦
160k46288623
160k46288623
asked yesterday


CrowderCrowder
1,91431233
1,91431233
marked as duplicate by nohillside♦
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
19 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by nohillside♦
StackExchange.ready(function()
if (StackExchange.options.isMobile) return;
$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');
$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();
);
);
);
19 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
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
yesterday
@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
yesterday
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
yesterday
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♦
yesterday
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.
add a comment |
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
yesterday
@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
yesterday
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
yesterday
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♦
yesterday
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
yesterday
@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
yesterday
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
yesterday
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♦
yesterday
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 yesterday
answered yesterday


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
yesterday
@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
yesterday
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
yesterday
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♦
yesterday
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
yesterday
@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
yesterday
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
yesterday
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♦
yesterday
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
yesterday
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
yesterday
@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
yesterday
@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
yesterday
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
yesterday
@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
yesterday
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♦
yesterday
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♦
yesterday
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.
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.
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 yesterday


bmike♦bmike
160k46288623
160k46288623
add a comment |
add a comment |