Health, home and travel decision
Gluten Free Scanner: Is it GF?
A technical user can build a useful barcode/OCR-based gluten scanner in about a week, but reproducing the app’s claimed multi‑million product database, curated safety/recall data, and polished App Store experience is not realistic without substantial ongoing effort or licensing.
View on the App Store↗$2.08/mo
$25/yr
Read off the official pricing page.
$100one-off38 h to build
$30/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 19 seats.
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
- User scans barcode or photographs an ingredient label → app extracts barcode/OCR text → lookup product in a database or classify ingredients → show YES/NO gluten result and ingredient details → optionally allow saving scans.
What it still won’t have
- The vendor’s claimed large proprietary product database (millions of products)
- Commercial polish, frequent bug fixes and stability updates from the App Store release cycle
- In-app subscription handling with trials and App Store purchase flows
- Any curated manufacturer/recall data and editorial safety/community reviews
- Developer support and trust signals (App Store reviews/ratings)
What remains hard
- Proprietary data
Millions of Products Supported – Access a vast database of grocery items, snacks, drinks, and more.
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 19 seats.
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 gluten-check iOS app using Swift (UIKit/SwiftUI) with a small Node.js backend. Core features in scope: (1) camera barcode scanner (AVFoundation) that queries OpenFoodFacts for product metadata, (2) OCR endpoint using Tesseract on the backend to extract ingredient text from photos, (3) ingredient parser (regex + small prompt to an LLM or simple local rule engine) that returns a YES/NO gluten flag and highlights offending ingredients, (4) local scan history (SQLite) and a results UI, (5) StoreKit integration for a single paid subscription tier (no trials). Out of scope: building a proprietary multi-million product database, community reviews, recall feeds, and advanced ML training. Provide error handling for network/OCR failures, unit tests for parsing logic, and end-to-end tests for the scan flow. Include Dockerfile for the backend and deployment instructions for a single small VPS (DigitalOcean/AWS t3.small).
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Hard moats found in the evidence-3
- 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 productGluten Free Scanner: Is It GF? App - App Store
- official productCeliapp: Celiac/Gluten Scanner App - App Store
Integrity checks
What held up, and what did not.
