Every Horizon Launcher build on this site passes the same routine on our own Android phones before the download button goes live. No build is listed from a changelog, a press note or another site summary.
The routine
First, the install: the file is fetched fresh, installed on a clean phone, and the icon, first launch and Play page are checked. Second, preparation: the launcher prepares the game from a real Minecraft Java Edition 26.3 installation, timed, on both a flagship and a mid range phone. Third, play: a fresh world, an older world upgraded from a previous version, and a long session with distant terrain raised.
Fourth, renderers: the same scenes run on Vulkan and on OpenGL ES, and frame behaviour is compared, because that single Settings choice decides how Horizon feels on most phones. Fifth, controls: a full session on touch, then a full session on a controller. Finally, updates: the new build is installed over the old one, never after an uninstall, to confirm worlds, settings and content mods carry across.
What we publish
We publish what we measured: prepare times, the settings that held frames steady, and the problems we hit, with fixes. If a build fails a step, the failure is fixed or the build waits. Scores and store style ratings are never copied from other sites.