No cloud. No account.
Just your receipts.
Receipt Scanner turns paper receipts into structured, searchable records — merchant, date, items, tax, total — using on-device OCR. The camera, the parsing, and the storage never leave your phone.
From paper to data, with a confidence score on every field.
Illustrative sample — every field a real scan produces gets this same Detected / Needs review treatment before you save it.
Confirmed, and not yet confirmed.
Confirmed on a real Android device
- Settings screen
- History empty state
- Camera-permission screen
All render correctly, matching the built design exactly.
Not yet end-to-end confirmed
- A full capture → OCR → parse → save round trip on an actual receipt
Each piece is checked independently — the parser against realistic sample OCR text, the storage layer's SQL against a real SQLite engine, a clean Metro bundle for both platforms — but that's not the same as scanning a real receipt end to end.
No live receipt edge detection yet — capture is manual: position, then tap.
Parsing is heuristic and keyword-based. Unusual layouts — handwritten, extremely faded, non-tabular — will likely need the parser extended.
The scanner frame's size is computed once at mount, not reactive to window changes like Android split-screen.
Five calls made without a device attached.
On-device OCR, not a cloud API
Privacy is the whole premise here, not a feature bullet point. A cloud OCR call was never on the table, regardless of any accuracy tradeoff.
Manual capture, not live edge detection
Real-time document detection needs frame-by-frame computer vision — a large native surface that's hard to get right without a device to test against. Position-and-tap is simpler, and how most receipt apps actually work.
React Native's Animated, not Reanimated
Reanimated needs its own native build step and worklet config. Animated ships with core React Native — the safer choice to build without a device attached to verify the config against.
The parser returns null, never a guess
An invented total or date is worse than an empty field — a wrong-but-confident-looking number is the error a user won't think to double-check. The review screen is where a human confirms it.
One dark theme, not an unfinished light one
The dark navy and violet look isn't a color scheme bolted on — it's the whole visual identity, down to the scanner glow. A half-built light mode would dilute that, not extend it.
Best tried on an actual phone.
Clone and install
git clone https://github.com/mirconegri/receipt-scanner.git
npm install
Build a dev client (needs a real device)
npx expo prebuild, then npx expo run:android — or run:ios with a Mac and Xcode.
Verify without a device
npm run verify-parser, npm run verify-sql, npm run typecheck, npm run lint
Or build for testing on Expo's servers
npx eas-cli@latest build --profile preview --platform android — no local Xcode or Android Studio needed.
Built in the open, verified where it could be.
Look at the code, run the verifiers, or open an issue.