Anything which gets responses of empty platitudes usually means they aren’t listening.
I am a small developer who makes apps and puts them on the App Store and play store (Hacker news client HACK for example). I often get emails from users on how to add a feature or fix a bug etc.
I email them and instead of just saying “thanks for your feedback”, I address the real problem/feature.
Example- few days ago someone asked me to integrate the Orion browser support in my app.
I wasn’t aware of this browser so I googled it, found it that it’s currently in closed beta and I signed up for a beta. I replied back to the user that currently I can’t add it in because I don’t have access to the beta yet, however I have signed up and when I do get access to it, I will test and add it in unless the user can get me a piece of code from the developers of Orion browser which tells me what identifier to use to launch their browser on iOS.
The user contacted the developers of Orion and got me the info I needed. Today I added it in but since I still don’t have access to the beta, I sent the app update and informed the user that for now, I have added the functionality acting blindly and I think it should work but if it doesn’t, then they will have to wait for me to get the beta. User is happy.
Another example- someone recently contacted me for a feature in another one of my apps which I have no intention of adding. I replied back that I will be honest with them and inform them that I don’t intend on adding it in and here’s my reasons. I gave them an alternative app which has that feature in case they want to try. User was happy and gave me a 5 star review.
Basically, even if you have bad news for the customer, tell them the news and they will be just fine. I try to put myself in the customers shoes and think about what I would think of got the typical cookie cutter response “we are listening to your feedback” with no further details on what they intend on doing with what they are hearing.
This doesn’t scale. If your app reaches any level of success, you don’t get one email per night, you get 100. When my app was small I responded individually, but after I hit a threshold I had to use a template response for feature requests just to stay productive.
It can scale, and I'd wager that it will. There is -- or should in future be -- a far larger number of software developers than the number of components that are required to compose the functionality that everyone needs and desires, at high quality and with ever-reducing negative externalities.
That's a good thing: it'll provide more time for review, apprenticeship, mentoring and mastery of individual technical areas, and for mobility and communication between communities.
That's not to say there can't also be pure-enjoyment and hobby software projects; but those won't have the same support demands (or expectations).
Small (or solo) teams maintaining systems with massive inbound demand, significant risk during changes, and limited ability to receive community feedback feels like the less-scalable approach, to me.
That said I'm willing to concede that both approaches appear to work under different circumstances (and may be able to learn from each other).
You have a fair point but I disagree. However I also recognize that I can only be proven right or wrong when I am in those shoes at some very large scale. For now, I do get about 5-10 emails a day for all my apps combined and it’s been easily manageable.
However, the article we are talking about here is about Microsoft, a trillion dollar company treating some basic user feedback with zero value.
Amazon, another trillion dollar company has been outstanding to me whenever I reach out to their customer support chat (I have done that many times over the years). I get to chat to a human within a minute and they help me either resolve the issue or tell me why they can’t resolve the issue. If Amazon can do it, then there’s no reason why Microsoft can’t do it for basic user feedback.
Also are you really being productive if you are sending template response? A robot could do that.
Founder of Orion Browser here. Thanks for adding the support. Please email me (info in profile) if you need to test the integration to skip the waitlist.
Btw I am in the same basket as you - not only reacting on every piece of user feedback, but actively seeking it, like in this case. (using excellent f5bot.com). It may not be infinetely scalable but will do it for as long as I can.
I am a small developer who makes apps and puts them on the App Store and play store (Hacker news client HACK for example). I often get emails from users on how to add a feature or fix a bug etc. I email them and instead of just saying “thanks for your feedback”, I address the real problem/feature.
Example- few days ago someone asked me to integrate the Orion browser support in my app.
I wasn’t aware of this browser so I googled it, found it that it’s currently in closed beta and I signed up for a beta. I replied back to the user that currently I can’t add it in because I don’t have access to the beta yet, however I have signed up and when I do get access to it, I will test and add it in unless the user can get me a piece of code from the developers of Orion browser which tells me what identifier to use to launch their browser on iOS.
The user contacted the developers of Orion and got me the info I needed. Today I added it in but since I still don’t have access to the beta, I sent the app update and informed the user that for now, I have added the functionality acting blindly and I think it should work but if it doesn’t, then they will have to wait for me to get the beta. User is happy.
Another example- someone recently contacted me for a feature in another one of my apps which I have no intention of adding. I replied back that I will be honest with them and inform them that I don’t intend on adding it in and here’s my reasons. I gave them an alternative app which has that feature in case they want to try. User was happy and gave me a 5 star review.
Basically, even if you have bad news for the customer, tell them the news and they will be just fine. I try to put myself in the customers shoes and think about what I would think of got the typical cookie cutter response “we are listening to your feedback” with no further details on what they intend on doing with what they are hearing.