HOSHCARE CLIENT - Frontend Vault
1. the problem
HOSHCARE stores medical documents - prescriptions, lab reports, discharge summaries - and turns them into structured, searchable records. A photo of a prescription becomes doctor, date, diagnosis and medications: fields a user reviews before anything saves. Once saved, a record locks permanently. Health records that can be silently edited after the fact aren't records.
ROLE: Camera capture pipeline with native auto-cropping, uncompressed memory buffer allocation, and secure sandboxed disk cache.
2. what i built
Roughly 19 screens, plus full dark mode and a shared design system carried over from the marketing site:
3. problems i had to crack
Click card to view root cause & code diffAfter a dependency update, sign-in failed with no error. The library had moved idToken one level deeper, to response.data.idToken. The old path returned undefined, the auth call accepted it, and the server rejected it. Found by logging the raw response instead of the field I expected.
After an Expo upgrade, uploads failed silently. Expo 52+ ships a WinterCG-compliant fetch polyfill that handles React Native FormData differently, so requests left with an empty body. Fix: a dedicated apiUpload() on XMLHttpRequest, which skips the polyfill and reports real upload progress as a bonus.
A local dev build failed with nothing to read. npx expo config --json showed expo-secure-store declared as a config plugin but never installed. Plugin resolution failed before it could print a useful error.
The overlap kept coming back because each screen was patched on its own. Fix: audit every screen with useSafeAreaInsets() at once instead of patching one at a time.
PRIVATE REPO. Happy to walk through the code and architecture in an interview.
| PROJECT | HOSHCARE CLIENT (FRONTEND) |
| DRAWN BY | BIDYA B. NANDA |
| STATUS | ACTIVE, PRE-PILOT |