I just got my second review of ChordCalc and it's really bad. It's not just bad in the sense that it takes on weak points that I would agree with. No, it's worse than bad because it misrepresents my app completely and tells people to "stay away from this app!"
This is only the 2nd review I've gotten and I'm wondering if I should respond to it in my app writeup. I've noticed others doing this in their writeups and I always find it a little annoying, but now I understand the feeling behind it.
(Stuff in bold below is where I'm completely wrong, what!!)
I spent many months consulting with musicians and a composer about the chord naming in my app, and I know for a fact that it's 100% accurate, but the reviewer claims it's totally screwed up. He cites an example where he claims a chord with the tones E-G-C is supposed to be named Emb6, but he's actually wrong! (E-G-C is Em+ and E-G-B-C is an Emb6). Unfortunately, people who don't know chord theory are going to assume he knows what he's talking about and that my app is wrong.
He then claims the help section is hard to parse, when in fact I made certain to write it clearly and carefully. He says "the modes are misnamed" because I included a major/minor/diminished designation. He says "the mistakes are legion." He says the palettes only name flats or sharps, but that's not true either! The default setting for "Loose Tone Naming" is ON. It can be turned off to show double-flats and double-sharps for people who need them. He finishes his review by saying "it doesn't do what it says it will do whatsoever."
The first review I received was very positive, but this one is full of damning details - none of which are accurate. What can a poor developer do?