Every build on this site passes the same bench before the download button lights up. This page is the bench, published so you can hold us to it.
Step 1: File checks
We check the package identity and published file size of the build against the figures its home site presents, review the permissions it requests, and scan the file. A build that fails any check is never published.
Step 2: Real phones
We install on five handsets: a Samsung Galaxy A55 on Android 15, a Google Pixel 8 on Android 16, a Xiaomi Redmi Note 13 Pro on Android 14, an Infinix Note 40 Pro on Android 14, and a Samsung Galaxy A13 on Android 12. The A13's job is honesty: it shows us where the floor is for older hardware, and we report the floor rather than hiding it.
Step 3: Connection logging
Connection claims get measured, not vibes. We record the in-game ping readout across full sessions on home Wi-Fi and on mobile data, at quiet hours and at peak evening hours, and compare the build's route against the standard route on the same networks. Stability matters more than a single low number, and our guides report both.
Step 4: Ranked evenings
We play full ranked evenings, solo and in squads, watching specifically for the failures this build promises to fix: lag spikes in fights, rubber-banding in final circles, and auto-back kicks. A verdict here has survived peak hours, which is the only kind worth reading.
About ratings
The rating shown on this site is the figure published in the build's home site data, and we label it as such wherever it appears. What we add is the bench above: measured sessions, in words and numbers we can be held to.