About

Project Overview Hiring a mobile developer to build a production-ready cross-platform app (Android + iOS) that helps consumers capture receipts, track warranty periods, and avoid missing return windows. The app also provides a simple merchant inbox (web) to receive digital claims and reduce back-and-forth. Key User Features: - Receipt capture (OCR): Scan or import receipts; auto-extract store, date, items, totals, and tax. - Deadlines & reminders: Auto-calc warranty duration and return window; countdowns + notifications. - Organize & find: Tags, folders, and fast search by store/category/date range. - Shareable proof: Create a link with purchase details + photos for resale or support. - Backup & privacy: Cloud sync (with local-only option) and easy export/delete of user data. Merchant/Operations (Web Inbox) - Secure web inbox to receive digital receipts/claims, request additional info, and mark resolved. - Basic aggregate insights (e.g., common return reasons, frequent defect items). Scope (Initial Release) - One codebase for Android & iOS (Flutter or React Native). - OCR pipeline (on-device or reputable OCR API) tuned for receipt layouts. - Data model for receipts, line items, warranties/returns, and reminders. - Account system (email/phone login). - Cloud sync (Supabase/Firebase or your recommended equivalent). - Merchant web inbox (simple authenticated dashboard) with claim status. - Privacy controls and secure storage (keychain/keystore). Non-Functional Requirements - Clean, responsive UI with light/dark mode. - Works smoothly on mid-range Android devices; reliable offline behavior with background sync. - Secure handling of tokens/files; minimal PII collected. - Clear documentation and maintainable project structure. Deliverables - Source code (well-structured) + README with setup/build/deploy steps. - Android build (AAB/APK) and iOS TestFlight build. - Hosted preview or deploy steps for the merchant web inbox. - Crash/error reporting and basic analytics wired. - Short handover pack: architecture overview, data model, env/config matrix. Nice-to-Have (call out if you include) - Line-item parsing & auto-categorization. - Email receipt parsing (forward-to-inbox flow). - Multi-language OCR. - Family/shared vaults with permissions. Timeline & Milestones (propose your plan if different) - Foundation & OCR spike (Week 1–2): App shell, auth, OCR proof, receipt object model. - Receipts → Timelines (Week 3–4): Extraction → warranty/return logic → reminders; search/tags. - Merchant inbox & polish (Week 5): Web inbox, claims status, basic insights, QA pass. - Release prep (Week 6): Store assets, CI/CD, TestFlight/internal testing, docs. Tech Preferences (open to your recommendation) - App: Flutter or React Native (Expo acceptable). - Backend: Supabase/Firebase or Node/Express + Postgres. - OCR: On-device (ML Kit/Tesseract) or paid API with strong receipt accuracy. - Web inbox: Next.js or similar with simple auth. What to Include in Your Proposal - Your stack choice (app + OCR + backend) and why. - 2–3 relevant apps you’ve shipped (links or short videos). - How you’ll handle OCR edge cases (faded/curled receipts, long grocery tapes). - Milestone plan, timeline, and pricing (fixed or milestone-based). - Any third-party services you expect to use and their costs. Notes - Keep scope tight and production-oriented; I value pragmatic decisions and clear communication. - All IP/work product transfers upon payment. Post-launch maintenance is possible. - Budget: Enter your best fixed price with milestone breakdown. Start: ASAP (flexible).