vgminer Reviews

4/5 rating based on 12 reviews. Read all reviews for vgminer for iPhone.
vgminer is paid iOS app published by VGMINER, LLC

$0.99 robbed.

Joselaugamez

They just steal my money. It's doesn’t work. When I try to find a player, even myself it's says unknown failure, please wait and try again.


App is Trash

Toyboytbfb

Waste of a buck. App loads incredibly slow and API doesn’t always have the most recent data. It’s also June 2018 and there still isn’t an update to resolve these issues. Developers of this app is a scam artist. Stick to trusted API sites for your reviews like VainSocial and VGPro.


Thought it would be a native App

Pat Ambrosio

This appears to be just the site wrapped in an app, not native at all. Might not be worth it if you can tolerate the website on a mobile web browser, same performance.


Awesome!

pgGold4Life

Best vainglory stats app! <3


Love this app

Rock63357

Easiest to use and best looking stats app for VG!


Vg miner

Jelly + fish = jellyfish

Good app but put a back button!!!!!


Big VG fan

xDwest

I've been playing VG since 2015 and this app is really good to check how you are doing with certain heroes. IGN: xDwest


No NA search option

SeoulofAsia

It’s not there on the app for me :(


Needs an update

CNote44

I can no longer search for any players to see stats, etc. Luckily I had already favorited myself, but if you do a search for anyone it comes back as “player not found”. I’ve made sure to enter the players name case sensitive and still same result. Please fix this. I paid for the app, it should work correctly.


Useful information but app is slow

mellow0324

I thoroughly enjoyed this app before the 3.0 update. There were some UI decisions that were made that seem like a backtrack, those I didn't like. Moreover, the app is very inefficient now. I don't know if you're using a new framework that's taking forever to load UITables / UIWindows. Or maybe you tried to retool your requests. But it's taking like 10 seconds to load a player page when your app performed with expected behavior before this update. Can you please take a look into this?