Step 1: Pin Down the Source
Every review starts by naming the source. For the official game, that is the publisher and its store listing: developer, package name, version, size, and rating are read from the listing itself. For a fan build, the source is the community channel that published it, and if that cannot be named and re-checked, the build fails at step one.
Step 2: Test on Real Devices
Builds are installed and played on real Android phones: a Galaxy A55 on Android 15, a Pixel 8 on Android 16, a Redmi Note 13 Pro on Android 14, an Infinix Note 40 Pro on Android 14, and a Galaxy A13 on Android 12 for the low-end view. Test phones carry no main accounts.
Step 3: Check Claims One by One
Each advertised feature is tested as its own claim. Offline play is tested in airplane mode. Online modes are tested once and reported honestly. Storage is measured at install and after extra downloads. A screenshot in a community post counts as a claim, never as proof.
Step 4: Score the Risk
Permission requests, login screens, redirect chains, and file changes are logged. Anything that asks for an official account password ends the review on the spot. The publisher terms on modified clients are quoted so readers see the account risk in the publisher's own framing.
Step 5: Publish the Verdict, Good or Bad
The review is published with failures included. A download link appears on this site only for a file that passes every step, which is why the Kipas download page can honestly say no file is linked yet.