Games and entertainment decision
Decision Game
A competent developer can implement a useful self-hosted replacement in about a week; the product has no evident durable moats and open-source habit trackers cover similar use cases.
Visit website↗Built by Marc Lou, who ships 32 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off26 h to build
$0/mo1 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Present a short decision with two choices and a countdown; register the user's choice; persist simple progress/habit state; display immediate gamified feedback (save Kitty, score, streaks).
What it still won’t have
- Cloud-hosted multi-device sync and user accounts
- Analytics and usage dashboards out of the box
- Any proprietary branding, ratings, or marketplace visibility
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Decision Game does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a single-page React (or Svelte) app deployed as a static site (Vite build, Netlify/Vercel). Core features in scope: decision prompt screen with two choice buttons and a configurable countdown timer; local persistence of user state (choices, scores, streaks) using localStorage; simple animated gamified feedback (save Kitty graphic, score increment, streak badges); build and deploy pipeline and optional privacy-first analytics using a small events endpoint or self-hosted Matomo (optional). Out of scope: multi-device account sync, paid subscription billing, complex backend. Include error handling for storage failures, accessibility for controls and timer, unit and integration tests for UI and persistence, and a README with deployment steps.
How we checked
How the score was reached
- Build verdict base78
- 3/3 assessment runs agreed+4
- Evidence score82
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 1
Every page the run actually retrieved.
- official productDecision Game — official product page
Integrity checks
What held up, and what did not.
