Learning and careers decision

TreasureScoper

A competent developer can reproduce the core camera+on‑device CV workflow and archive features (using existing CV libraries and CoreML), but the full polished product—tuned proprietary models, curated reference comparisons, and App Store product polish—would be costly to match.

View on the App Store
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off120 h to build

$0/mo5 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All TreasureScoper alternatives, with the arithmetic →

What a replacement has to do

  • User photographs rock markings → run image analysis model → present interpreted symbols with confidence and optional overlay → save analysis with GPS to local archive

What it still won’t have

  • Proprietary tuned models and curated reference comparisons used by the app
  • Polish of a published App Store product (store listing, reviews, distribution)
  • Any premium cloud-hosted services or telemetry built by the vendor

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

TreasureScoper 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

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build an iOS app in Swift/SwiftUI using Vision and CoreML: implement camera capture with GPS, convert a visual-classification model (from PaddleClas or ImageAI-trained model) to CoreML, run symbol detection+classification on-device to produce label + confidence, render interactive overlay markers and probability matrix on photos, implement local persistence (SQLite/CoreData) and a dashboard of saved analyses, add export/share, and include unit/UI tests and error handling. Out of scope: building a curated, proprietary reference database and paid subscription backend. Provide CI for builds and instructions to convert/replace the model.
How we checked3 sources · 3/3 runs agreed · evidence score 64

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 3 cited sources+3
  • 3/3 assessment runs agreed+4
  • Evidence score64

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 · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded