I've found in most (all?) aspects of my life, trying to tell other people how to deliver feedback is usually the wrong approach. The better thing is to take the

I've found in most (all?) aspects of my life, trying to tell other people how to deliver feedback is usually the wrong approach. The better thing is to take the feedback regardless of how it's delivered and learn to interpret. Things are implied. Feedback on A, may actually be point at a problem with Z. Sometimes the correct way to interpret is to discard. The source of feedback is not going to connect those dots for you. That said, I see your point but I will try to defend mine. Your language of business sentence is basically implied by the pure existence of my complaint right? Should I have to type every implication out in order to provide any feedback? And this being a tech place for tech people I wanted to emphasize how simple it would be to correct (I don't really even know if the creator/app owner is reading, so it's more of a general feedback for other people who build products.) Highly subjective either way. Hell, the app owner could argue they don't care about people that don't manually type in the info because they're not really potential customers. I don't know if I'd fully agree, but it could be a form of lead qualification in which your business language feedback would not hold weight. It's at least somewhat true, because I was just curiously kicking the tires. I have no use for this product.