Games and entertainment decision
CatchCat
A competent technical user can implement a useful, smaller CatchCat: camera detection, album, and a basic community map are buildable, but the full polished mobile product with live multiplayer, moderation at scale, rewarded-ads, and Web3 integrations is larger and operationally heavier than a one-person short project.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off100 h to build
$40/mo6 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
- Walk, open the app camera, detect/verify a real cat, spend a snack to capture a sighting, sync to a personal album, and view community map pins.
What it still won’t have
- Polished mobile UX and store-quality production polish (animation, polish, cross-platform edge cases)
- Ranked multiplayer and matchmaking (Alley Clash) and its live-ops needs
- Moderation, safety workflows, and scale-ready content-moderation tooling
- Rewarded-ads, IAP tuning, and any Web3 integrations mentioned on the site
- Large active community effects, charts/leaderboards, and retention-driven analytics
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
CatchCat 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 minimal CatchCat replacement as a cross-platform mobile app (React Native), with a Node.js + Express backend and PostgreSQL for storage. In scope: (1) camera capture screen with framing overlay and torch, (2) integrate an on-device cat detection model via TensorFlow Lite / Core ML for live detection and a 'throw snack' verification flow, (3) client-side duplicate-fingerprint checks and block gallery-imports, (4) backend accounts, sighting storage (images as object storage), community map pins with simple proximity check, (5) album UI that generates a name, serial, rarity, and stores the photo, and (6) a browser API to preview a pinned sighting. Out of scope: ranked multiplayer battle system, rewarded-ads, Web3 features, advanced moderation workflows, and app-store submission polish. Include error handling, input validation, server and client tests (unit + basic integration), and scripts to deploy to a small VPS and S3-compatible storage.
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 productCatchCat – Spot Real Cats & Collect Unique Cat Cards
- official productCollectible Cat Cards & Album · CatchCat
Integrity checks
What held up, and what did not.
