[FEAT] Step 3: On-Device OCR Pipeline

Open
#81 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
46/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, react-native, typescript

Research direction

Read the parent epic #4 and inspect the project's existing photo-processing and native-module setup; the issue does not name files or tests. Compare the suggested on-device OCR options and determine how each photo enters the pipeline. Done means extracting raw text from each photo without a cloud dependency.

Written by the indexing model from the issue text.

Description

enhancement sub-issue

Is your feature request related to a problem? Please describe.

This is a sub-issue for [EPIC] Analog-to-Digital Journal

Describe the solution you'd like

Integrate an on-device OCR library (e.g., react-native-mlkit-ocr or Tesseract.js via a native module). Process each photo and extract raw text. No cloud dependency.

Describe alternatives you've considered

N/A

Additional Context

Part of the [EPIC] Analog-to-Digital Journal epic.

Parent Epic: #4

Dominant language
TypeScript
Stars
4
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GiZano/LevelUp

All issues in GiZano/LevelUp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.