Games and entertainment decision
Scory
A capable developer can build a useful offline scorekeeper (core workflows) in about a week, but reproducing the full polished, multi-game app and store presence is more work and not proven by supplied pages.
Visit website↗Built by Romain, who ships 3 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.
$100one-off40 h to build
$0/mo2 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
- Create a game configuration, add players, enter per-round scores via a scoring screen, apply game-specific rules/validation, and compute/display winners and history — all stored locally for offline use.
What it still won’t have
- Polish and animations of a shipped mobile app (App Store/Play Store UX)
- Existing pre-built specialized screens and edge-case handling for many niche games
- Brand, user base, reviews, and cross-platform build/CI pipeline
- Push updates and App Store submission/maintenance workflows
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Scory 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 cross-platform mobile scorekeeper app using React Native, TypeScript, and SQLite (via WatermelonDB or react-native-sqlite-storage). Core features in scope: (1) create/edit game templates with settings (target score, max rounds, auto-winner, auto-dealer, hide scores), (2) add unlimited players, (3) a generic scoring screen that records per-round inputs and applies validation rules, (4) specialized scoring screens for Yahtzee, Darts, and Skyjo with input helpers, (5) local persistence, export/import (JSON/CSV), and offline-first behavior. Out of scope: App Store/Play Store submission pipelines, analytics/telemetry, multi-device sync. Include error handling, input validation, unit tests for the rule engine, and basic UI tests for score entry flows.
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- 3/3 assessment runs agreed+4
- Evidence score57
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 · 2
Every page the run actually retrieved.
- official productScory - Score Keeper App for Board Games & Card Games
- official productScory - Score Keeper App for Board Games & Card Games
Integrity checks
What held up, and what did not.
