This is what it does
Try it
The Anti-App offers a few ordinary offline quests and asks you to prove one with a capture — the demo simulates it, because this site asks for no camera. Complete one quest to start.
Runs in your browser — nothing to install
- What it does: tracks a few ordinary real-world quests, asks you to capture one as proof, and feeds a streak with a one-day grace and no feed or ranking to fall into.
- What to try: complete a quest and watch the XP and streak move, then see the grace rule the tests pin so a missed evening never erases a month.
- What it does not do yet: no verification backend is reachable from this page, so the capture is simulated locally and every verdict is labelled DEMO — and the demo asks for no camera, because this site asks for none.
Status
What is built, and what is not
- The state machine is tested — 17 checks, all passing. They cover the rules the product rests on: the one-day grace, migration of older saved days, the four-hundred-day history trim, the per-quest DEMO tag, and local-date arithmetic across month, year and leap-day boundaries.
- The tests are falsified. Six deliberate defects are applied to the real application file one at a time and the suite is run against each: 6 mutants, 6 killed, 0 survived, and the file is restored byte-for-byte afterwards. That says the checks can fail, not that there are six features.
- It is a prototype, and the DEMO label is the honest limit. There is no app to install and no phone build, the verdict is a local simulation rather than a camera check against a backend, and a result is never presented as a verified one.
Under the hood
What it is built on
- Stack
- Three static files — one HTML shell, one stylesheet and one JavaScript file. No build step, no dependency and no server of its own.
- Runs where
- A browser is the only requirement. What the app records stays in that browser’s local storage under a documented schema with a migration path.
- Tested by
- 17 checks over the state machine plus a falsifier that applies six defects to the real application file, kills all six, and restores the file byte-for-byte.
Tell us what broke
Whether the capture step is worth the friction, why a habit tracker should not have a feed, or anything the demo got wrong — the feedback form is the way in.