Short, dated notes about the games and apps in the MODGRIND catalogue: a new Play Store release, a patch that breaks an existing mod, a build that stops installing on newer Android versions, or a listing that was pulled. Each post says what changed and whether the mod page still works.
Nothing appears here automatically. When a watched title ships an update, we re-test the current mod build on a clean install, note what broke if anything, and only then write the entry. That is why a post sometimes lags the store release by a day — the delay is the testing, not the reporting. Entries are never deleted: a note saying a build stopped working stays visible, because the version history matters more than a tidy homepage.
A game that pushes a server-side patch on Tuesday does not need a new APK; one that changes its client code does, and the mod has to be rebuilt against that exact version before it will install. Signatures must match, the OBB has to correspond to the new asset set, and any anti-cheat change means the previous build is dead on arrival. Rather than publish an untested file the moment a version number changes, the listing keeps the last build that is known to work and the note explains what is pending. If you installed an older version and it now refuses to launch, that is the mechanism — the fix is a rebuild, not a different mirror.
Follow by RSS at /feed.xml. Longer guides live in the blog.
Patch notes, Play Store updates and how mods are affected — curated by MODGRIND.
Six long-requested titles are in the catalogue as of today, each with a verified live APK, a current base version and an honest list of what the mod actually changes.