Guess the Modern Firearm User Reviews

Is Guess the Modern Firearm Safe?

Guess the Modern Firearm appears mostly safe based on user ratings. AppsHunter Safety Score for Guess the Modern Firearm is 83/100.

This assessment is based on 32 user ratings, with an App Store average of 4.6/5.

Safety Analysis

87.5% of ratings point to a safe experience
9.4% of ratings suggest some concerns
3.1% of ratings point to a risky experience

~ Based on 32 App Store ratings for Guess the Modern Firearm.

Is Guess the Modern Firearm Legit?

Guess the Modern Firearm appears to be a legitimate app. AppsHunter Legitimacy Score for Guess the Modern Firearm is 80/100.

Based on 80 of 100 points across 7 verification signals from App Store and developer data.

Top reviews

Kinda boring

I wish it would give you hints like who made it or what country it’s from and the pictures shouldn’t show people holding them with a bunch of trash attached to the gun I like that it’s add free

Response from developer

Thank you for the feedback!

What I 19 pack 1?

I don’t know what it is help

Response from developer

Thank you! The order of the levels is randomly generated.

But

It’s pretty fun but what is 15 in pack 1?

Response from developer

Thank you! The order of the levels is randomly generated.

A little explanation

A little explanation of distinguishing features on the gun or where it got its name. Maybe what manufacturer made the gun or in what capacity it was used. Maybe a way to select specific eras? I’m starting working at a gun store and was hoping this might help me know what I’m talking about a little more.
Show more

Response from developer

Thank you for the suggestions!

It’s a great game

Very useful to those who are trying to get in to the gun industry or military. Very accurate and is good about providing help if needed

Response from developer

Thank you!

Inaccurate pictures and titles

For question 19 of the first pack the answer is Makarov but it has a picture of the APS Stechkin that seems like a huge oversight

Response from developer

The issue was corrected in the latest update. Thank you!