What’s a decent way of responding?

Thank them for the report. Reassure them you are listening to their feedback.

What should I keep in mind?

That you can’t please everyone and that some people don’t seem capable of not being rude.

What mindset should I have?

You don’t have to follow through on all the points that were brought up. It is your app and you decide where it goes. You will not be able to please everyone – so don’t try. Make sure the group of people your app is for is catered for, but not everyone that uses it.

Remember, we are software professionals. The best way to deal with rude or angry customers (even if they are not paying customers) is to respond politely and professionally.

There are two very important points to keep in mind:

1. Reputation is critical in any business. Do you want to be known as “that guy” who is rude to customers? That is a good way to lose business, both current and future.

2. Responding in any other way than completely polite and respectful will escalate the situation. It will devolve into very nonconstructive behavior: see my first point.

Sometimes you need to swallow your pride and tell people what they want to hear, not what you want to say.

Here is the mindset that I have asked my developers to follow:

1) Imagine you are the doctor in the emergency room treating the obstinate patient. The doctor is professional in every way and helps the patient even if the patient is yelling to not help.

2) Imagine that the person who is rude just had something terrible happen to them and they are terribly upset about it. Then the urge to reply negatively turns into pity and it is mentally much easier to reply professionally. This helps overcome the problem of keeping the bad situation on your mind.

The existing answers cover the ground of being professional quite well. There’s nothing wrong with being polite and professional in response. I’m instead going to cover being magnanimous.

I think a magnanimous response can make it unambiguous that the user has been rude–and you will help them anyways. There was even a now semi-famous example just this week.

Reasons to follow this strategy:

1. Generously calling out etiquette errors (especially in public) performs a useful social function by both modeling and helping to clearly define appropriate behavior. ex: From time to time I will ask a server (reasonably politely) if we could get this or that–but will forget to say please. My girlfriend
   will add the please to our interaction. While this is embarrassing and sometimes I stick my tongue out at her when the server leaves, she has made an effective intervention in my behavior.

2. Being able to respond to the offense will be far more mentally and emotionally healthy for you and your ability to continue to interact with your users than swallowing each offense and slowly growing bitter about the ingrates you have to suffer.

3. Keeping your response magnanimous will help clear your conscience when the inevitable user still takes offense at being called out politely and rants back at you.

4. If your bug tracker is public, sane users will recognize the fairness of your responses and respect both your dedication to your work and your ability to handle jerks deftly and without being a doormat. We all have interactions with nasty people in our lives, and we all have to make decisions about where to fall on the response scale. Because this is a shared experience we tend to empathize by:

   • Feeling shame or embarrassment when we watch someone else swallow these indignities. We may step in on your behalf, or try to comfort you after the episode is over.
   • Feeling catharsis when someone’s nasty behavior is paid back to them.
   • Respecting those who are as noble and composed as we wish we could be, by taking the middle path and both refusing to be walked on while resisting the impulse to be rude.

What’s a decent way of responding? What should I keep in mind? What mindset should I have?

You could keep in mind the Fundamental Attribution Error, which observes that humans tend to see our own mistakes and problems with the viewpoint “I’m fundamentally a good person, but on this occasion I did something wrong”, but see other people’s mistakes and problems from the view “they are fundamentally a bad person, they always to things wrong”.

The complainer is probably not fundamentally evil, nasty and hateful. They are probably a normal human who likes and cares about very similar things that you like. They are a programmer, they found your app, they are interested in whatever your app does, they used it enough to find the bug, they cared enough to report the bug report instead of giving up; but they were angry and lashed out at you.

You are overlap a lot with this person, you have more in common than if they were a 50 year old conspiracy theorist who doesn’t know what Android is or what your App does, and sent you a rude email about how you are doing everything wrong by using evil computers.

You wouldn’t be bothered by that person at all, would you? It wouldn’t strike a nerve, you might even laugh at it.

I care a lot about our users and want to maintain a good relationship and a good rating of our app. On the other I’d feel like a complete sell out if I would reply overly polite.

If you care more about App ratings than about keeping yourself feel good, you are a kind of sell out. If you care more about your users getting a good experience than yourself feeling righteous, you are a kind of sell out.

This is good, not bad. In the context of making your app the best possible app, it’s not about you the author, at all. A cathedral builder will have to overcome a lot more problems than hearing some rude words to build a cathedral. A cathedral will stand for hundreds of years and countless people will wonder at it, what does a rude word to the builder in the first moments of it’s construction count for? 0.00% of anything. The builders have better things to do than spend effort fighting back, more important things than putdowns.

Is the point to make something as good as you can, or be self-righteous, bitter and nitpicky over small details and individual user accounts?

1. Is the bug genuine, and can you fix it?

2. Do you want a world where people respond to anger with anger, or a world where people respond to anger with kindness?

3. Ideally you would only get polite bug reports. That’s not the real world. So would you prefer some rude feedback about bugs, or to not hear about those bugs at all?

4. If you were rightly or wrongly feeling disappointed and let down by a piece of software and were extremely blunt about it, what kind of reply would you feel good about getting?

5. Is it really as strong an attack on your App as it feels like? Are you about to lose funding, lose users, fail at your goals completely, have your department shut down, if you don’t fight back?

I agree with the “don’t take it personally”, “be magnanimous” and “fix the bug, ignore the rudeness” people, I just wanted to write more than would fit in a comment about why and how you can frame your thinking to make it completely ‘OK’ to do that.

— Edit; actually I want to write more than that —

There’s nothing to actually stop you being rude right back. You exist in a post-God world where you don’t believe being rude will send you to hell (I assume, otherwise you would have immediately thought about all your religious teachings on how to behave towards others), you are writing a free app so there’s no business pressure on you to be unfailingly polite, and you are involved in programming – a pretty relentless technical meritocracy culture with prominent examples of leaders have a rude attitude under the guise of being ‘no nonsense’, and a culture of flame wars and anger.

In short, there’s no higher pressure on you to arm-twist you into a polite reply and you are absolutely free to reply in kind with:

• I wrote this for me, if you don’t like it, tough.

• I wrote this and gave it away for free, how dare think you have any grounds to complain, do you know how much passion I’ve put into this, I’m so offended right now.

• It’s open source. Why don’t you improve it and submit a patch? Hope this helps. /smug 🙂

• You are an idiot, here’s a rant about everything wrong with you and your mother as well.

• That was rude so I ignored it, lol. 🙂

And so on, and there will be no short term immediate consequences whatsoever. Short term, you will feel better. Justified, happy, correct, superior.

So why should you take a personal hit, and feel hurt, feel undervalued, and reply politely in the face of pressure not to?

Because without any higher guiding principle the only thing you can do is step back and ask yourself what kind of a world you want to build. Everything you do is a contribution to the world of the future. Do you want to contribute to a ragey, firey, inhuman, uncaring, technical meritocracy? Or do you want to be a calming, humanising influence, a relatable developer?

I’m leading it towards an obvious conclusion here, but it’s not anymore a question of absolute, externally imposed right and wrongness, so maybe you will genuinely land on the other side from where I’m biasing it.

Torvalds swears at incompetent people. Knuth offers money as rewards for correct bug reports. Both are respected and successful.

Its already the highest voted comment but I think it deserves an answer

Like this bug report: [PYTHON-532] User-triggerable NULL pointer dereference due to utter plebbery

When a user responds in this way its always out of frustration. By dealing with their issue quickly and politely you can often turn an angry customer into a fan. My favourite comment from that bug report:

Person who raised the bug:
Apologies to anyone offended by this report. Thanks for your effort!

In summary:

1. Be polite and thank them for the bug report
2. Deal with the issue as quickly as you can

I like to ask myself a few questions.

Is the bug legitimate? Can I relate to their frustration? Are they misusing/misunderstanding the product?

In my experience we have to attempt to relate with customers/users. Sure, often they are stupid, but they do see things differently, and often this can be an indication of where improvements (in either documentation or user experience) could be made.

If they are misinformed, tell them you understand that it may have been confusing/frustrating and try to point them in the right direction and thank them for bringing it to attention.

If the bug is legitimate, then again, tell them you see their frustration, and thank them.

Sometimes using software can be very frustrating for non-tech, I know this, so I don’t take it personally.

Don’t take it personally!

Because it is not:
The author was angry – but pretty sure not about you or a colleague in person.

The bug report text expresses negative human emotions – against some abstract, vague opponent, representing the software, and the organisation creating the software.

If you see that very clear, you can just ignore the negative part – it’s just noise.
A bug report with bad text layout, hard to read, nothing more.

The Fog Creek blog suggests LATTE (for dealing with angry people, but I think it’s also applicable here):

• Listen: more of a phone step, they suggest prompting the client with the last thing the client said
• Acknowledge: make the person feel heard
• Tell: people want to see that they are in a process, they want to see evidence of movement
• Take Action: “I’m going to do something about that”
• Explain: your immediate first response will be to explain, it is the worse possible thing that you can do (i.e. leave this till last)

my own experience can verify this list (and the acronym reminds you to get your Starbucks on)

Your app is free, your time and pain are not. Ignore the report, and don’t feed the trolls.

It sounds like you really try to please your users and care about your software, which is good!

Some people just don’t know how to express themselves in a healthy manner, I’m sure the user felt much better after releasing that anger – though it sucks to be the unwarranted target.

You can’t change other people, and likely the person knows that they responded unprofessionally. Take it for what it really is at the core, just a bug report. I get the feeling you also want to express that they don’t need to be rude, because you care about your product and you appreciate helpful feedback. If you’d like to respond to the user in some way, I would focus on that, and not their rude behavior.

You should be able to recognize that your user is trying to help, in his own way – so whether what he says is true or not, the best thing to do going forward is to continue doing your best and recognize that some users will always think there are better ways to do it, and may never be happy with your hard work.

You say that you are giving your app away free of charge. From personal experience, I’d be annoyed if an app is worth a lot less than I paid for it. The conclusion is that the person complaining thinks your app is worth a lot less than nothing.

What do you think caused that person to write a very rude bug report? Do you think it is because that person is naturally rude, or is there a possibility that a bug in your app caused them so much aggravation that they were absolutely annoyed? For example, a free app providing a bus time table that gives the wrong times and I miss an important appointment because of that bug would be very, very annoying.

If your app has bugs that bring out the worst in people, then maybe you have a bigger problem than rude bug reporters. If your free app can really annoy people, then it can create a negative backslash against your company, so you better figure out what is going wrong there.