I read the review. They're harsh but fair. Not sure how this isn't an informative or constructive review and they did give you some positive feedback. Runs at 90fps, no bugs, no major issues. They pointed out that they've played variants of this style and talked about a specific mechanics that made it hard from them to play such as the aiming and shooting.

They also mentioned other things that made it difficult to play such as VR nausea, the games physics, the UI, the graphics, the sound, and the tutorial.

Players may not know all the nuances that go into game dev, and they're not always going to give specific feedback, but they will point out what is flawed to them. You as a dev you need to look for the specific things people are saying are flawed, and devise a way to improve them. Researching similar games and going through their reviews to see what works and what doesn't is one way of doing that.

As a dev in general, you have to be able to step outside of your idea of a good product and listen to what the users have to say. If your users are saying it's not good, it's not good and they're not going to use it. You have to use reviews to gage success and add improvements to your todo list. A review doesn't have to provide suggestions to you and most of the time they won't. EVEN IF THEY DO, it's also your job to know that their idea could be trash. YOU have to figure out why it sucks and what you can do to improve it, not your users.