Native / Expo Developer to Finish & Polish Studygram Mobile App (Supabase Backend)

Studygram is an AI-powered study platform for students — turn lecture notes and PDFs into summaries, quizzes, flashcards, and more. The web app is live with 3,000+ users. We have a React Native / Expo mobile app that shares the same Supabase backend as the web app, and we need an experienced mobile developer to finish, stabilize, and polish it for release. The mobile app is functional but pre-production. Core flows work (auth, viewing courses/materials that sync from the web); several features need bug fixes, and the app needs a focused v1 release plus a phased rollout of remaining features. This is a repair-and-polish role, not a greenfield rebuild. You'll be working in an existing, established codebase — preserving its architecture, not redesigning it. Tech stack Mobile: React Native + Expo (managed workflow), TypeScript, Expo Router (file-based routing), Zustand (state), React Query (data fetching/caching), Reanimated (animations) Backend (shared with web, do not modify without coordination): Supabase — Postgres, Row-Level Security, Auth (email + Google + Apple Sign-In), Storage (private buckets), Edge Functions (Deno) Auth: Supabase GoTrue, Google & Apple OAuth Build/release: EAS Build, Android (APK/AAB), iOS Web app (context only, separate codebase): React + Vite, same Supabase project What we need done (in priority order) Finish the core "Upload & Study" flow — upload notes/PDFs into courses, reliable file storage (private Supabase buckets with signed URLs), processing states, and clean success/error handling. This is the flagship feature for our v1 mobile release. Fix known bugs — we have a detailed QA report we'll share. Includes navigation stack issues, schema-mismatch errors in queries, upload edge cases, and error-handling gaps. Ship a focused v1 — lead with one polished feature; cleanly hide (feature-flag, not delete) features that aren't ready, so they can be re-enabled later. Phased rollout of remaining features — AI Lecturer, Smart Quizzes, Assignment Solver, Study Groups, etc. Some need bug fixes; some need UI/UX rework. We'll tackle these one at a time after v1. Premium/subscription entitlement — ensure paid users get correct access (RevenueCat or equivalent + Supabase profile sync). Polish — premium, modern, Apple-quality UI/UX: consistent design system, loading skeletons, empty states, smooth navigation, reduced-motion support, accessibility. Required skills Strong, demonstrable React Native + Expo experience (please link real apps you've shipped, ideally in stores) TypeScript proficiency Supabase experience — Postgres queries, RLS, Auth, Storage, Edge Functions — or equivalent (Firebase-heavy backgrounds welcome if you can show you learn fast) Comfortable working in and improving an existing codebase rather than rewriting it Git discipline — clean commits, feature branches, no force-pushing over shared work EAS Build experience; can produce and debug Android/iOS release builds Strong eye for mobile UI/UX — you've built things that feel polished, not just functional Nice to have Expo Router, Zustand, React Query, Reanimated specifically Experience with AI-feature integration (calling backend AI/LLM edge functions) App Store / Play Store submission experience RevenueCat or in-app-purchase entitlement experience How we work Small team, direct communication, fast feedback loops. We work in scoped, phased tasks with clear acceptance criteria — not vague "fix everything" dumps. You'll get a specific brief per phase. We value honest assessment over optimism — if something's broken or a fix won't work, tell us early. Test on real devices/emulators before marking work done. To apply, please include: Links to React Native apps you've shipped (store links strongly preferred). Screenshots or repos if not in stores. One sentence on your Supabase experience (or closest equivalent). A short note on how you approach finishing/debugging an existing app you didn't build —what's your first step when you inherit a codebase? Your availability (hours/week) and rate. Applications that just say "I can do this, let's chat" without the above will be skipped. We read every one that includes real work samples.