Image and video decision

FabriScan

A competent developer can build a narrow web prototype that reproduces core scanning and history features in about a week, but reproducing the native iOS app, App Store IAP flows, and any proprietary training/data behind classification would be harder and is not covered by available evidence.

View on the App Store
You pay

$1.67/mo

$20/yr

Read off the official pricing page.

You’d pay instead

$100one-off34 h to build

$50/mo3 h/mo upkeep

On cash alone, building overtakes the subscription at 35 seats.

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 FabriScan alternatives, with the arithmetic →

What a replacement has to do

  • User takes or uploads a photo → server/classifier identifies fabric type and returns material details → store scan in user history

What it still won’t have

  • Native iOS app experience and App Store distribution
  • On-device processing or any platform-specific optimizations
  • Built-in App Store in‑app purchase flows and weekly billing option
  • Polish, ratings/reviews and any proprietary training or labeled fabric dataset (not published)

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 35 seats.

Paid seatsseats

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 a minimal web replacement using: React (Next.js) frontend, Node.js/Express backend, Postgres for history, and AWS S3 for image storage. Core features in scope: (1) mobile‑responsive page to capture or upload a photo, (2) backend endpoint to accept images and store them in S3, (3) integration with a third‑party vision/classification API to return fabric label(s) and confidence, (4) a mapping layer that converts labels into readable material descriptions and care instructions, (5) authenticated user accounts and a simple subscription gate (Stripe) that unlocks detailed results, and (6) scan history display. Explicitly out of scope: native iOS App Store submission, training custom ML models, and on‑device inference. Require robust error handling for upload/processing failures, retries for transient API errors, logging, and unit/integration tests covering upload, classification integration, mapping logic, and subscription checks.
How we checked3 sources · 2/3 runs agreed · evidence score 63

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 3 cited sources+3
  • Price verified on pricing page+3
  • Evidence score63

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.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded