Senior Mobile App Developer Needed for App Store & Google Play Launch + Ongoing Support

Lovable/Supabase Developer — App Store & Google Play Launch + Ongoing Support (Hitch Fit System) Job Title (for the Upwork listing field) Lovable/Supabase Developer — Launch Our Fitness App on iOS & Android + Ongoing Maintenance Summary Hitch Fit System is a mobile-first web app built for oil sands and remote-camp rotational shift workers (FIFO, BIBO, DIDO schedules) — a 90-day body recomposition tracker, sleep recovery system, and coaching companion that adapts based on whether the user is on-site or at home, with dedicated guided flows for the two hardest transitions in rotational work. The app is built entirely in Lovable (AI-assisted full-stack builder) on a Supabase backend (Postgres, Auth, Storage, Row-Level Security, Edge Functions). The full build specification — every table, every screen, every logic rule — already exists as a detailed, versioned build document and has been used to build the app to its current state in Lovable. I'm non-technical and need one developer to own three connected things, ideally as a continuing relationship rather than a one-off job: Get the app onto the Apple App Store and Google Play, from developer account setup through approval. Fine-tune and extend the app inside Lovable — implementing new sections from the build spec as I add them, fixing issues, tightening the UI. Be available on an ongoing basis for maintenance and troubleshooting after launch — bug fixes, platform updates, resubmitting builds as the app evolves. If you're comfortable working inside Lovable specifically (not just React in a normal IDE) and have taken at least one app through both app stores end to end, I'd like to hear from you. What's Already Built The app currently ships with these major systems, all live in the Lovable project: Supabase schema & auth — relational data model with Row-Level Security, Email/Password + Google OAuth sign-in. Progressive onboarding — a two-tier flow (fast-start essentials, then a fuller profile), including a "Find Your Sleep Killer" diagnostic quiz. Shift-Adaptive State Engine — a four-state system (At Site / At Home / Camp Switch / Home Switch) that auto-detects which mode to show from the user's rotation calendar. Dual-mode nutrition engine — camp buffet plate-building vs. home macro tracking, shift-synced meal timing, a caffeine cutoff timer, and a weekly adaptive-target adjuster. Job-adaptive, equipment-tiered workout system — filtered by camp gym access, job type, and daily readiness, with auto-progression based on logged performance. The Sleep Reset Engine (flagship module) — light-exposure protocol, guided wind-down flow, a multi-day "Double Switch" wizard for the two hardest hitch transitions, an emergency fatigue protocol, a nap logger, a 14-day guided onboarding curriculum, and more. Low-T awareness & tracking module — educational bloodwork tracking and symptom check-ins, gender-conditional visibility, medical disclaimers throughout. My Products & Media Library — an in-app eBook reader and audiobook player, with purchases synced automatically from GoHighLevel sales pages via webhook. Baseline & Progress Engine — a unified "Then vs. Now" reporting system with composite scores. Circadian Load Map — a 30-day forward shift-pattern planner and visualizer. Full accessibility, performance, and platform-compliance standards — already written into the spec (WCAG AA contrast, screen reader support, offline-first logging, account deletion, data consent). The complete build specification (40+ pages, every table and screen documented) will be shared directly with whoever takes this on, along with a plain-language feature guide. Compliance Areas Worth Knowing About Upfront I'd rather you scope this accurately than hit a surprise resubmission cycle: HealthKit (iOS) / Health Connect (Android) integration — the app syncs sleep data from Apple Watch and Android wearables (Fitbit, Garmin, Samsung, Pixel Watch). Needs correct permission-usage strings and careful handling given Apple/Google's scrutiny of health data apps. Health-adjacent educational content — the Low-T module discusses hormone health with a bloodwork tracker. Strictly educational, disclaimer on every screen, but this may affect age rating or require extra review documentation. In-app purchases — the eBook/audiobook library currently sells through GoHighLevel/Stripe on the web. Apple and Google require their own in-app purchase systems (StoreKit / Google Play Billing) for digital content inside a native app — this integration still needs to be built for the store versions. Push notifications — used extensively for shift-based reminders and fatigue alerts; needs proper permission handling on both platforms. Account deletion & data export — already specified in the build (Apple requires in-app account deletion for any app with account creation), but needs to actually ship correctly. Data safety disclosures — the app collects health metrics; needs an accurate Google Play Data Safety form and Apple privacy nutrition label reflecting exactly what's collected, not a generic template. What You'll Be Doing Phase 1 — Launch (the initial, most clearly scoped chunk of work): Set up the Apple Developer Program and Google Play Console accounts under my ownership (not a shared or agency login). Generate store-ready builds from the Lovable app (native-wrapped via Capacitor or a comparable service) with correct signing, provisioning, and target API levels for both platforms. Build the in-app purchase integration (StoreKit + Google Play Billing) for the digital products module. Handle full submission and review management on both platforms through to approval, including responding to reviewer feedback and resubmissions. Make sure privacy policy, terms of use, and data safety/nutrition-label disclosures accurately reflect what the app actually collects. Phase 2 — Fine-Tuning (runs alongside and after launch): Work inside Lovable to implement remaining sections of the build spec as I finalize them, fix bugs, and tighten up UI/UX against the spec's accessibility and design-system standards. Flag anything in the spec that doesn't translate cleanly into a real build, and propose fixes. Phase 3 — Ongoing Maintenance (the continuing relationship): Be available as needed for troubleshooting, bug fixes, OS/platform update compatibility, and resubmitting updated builds as I keep adding features in Lovable. This is the part I most want a long-term fit for — someone I can keep coming back to, not a one-and-done submission job. What You'll Be Working With Builder: Lovable Backend: Supabase (Postgres, Auth, Storage, Row-Level Security, Edge Functions) Native wrapping: Capacitor or equivalent (your call, tell me why) Payments/content source: GoHighLevel (webhooks into a Supabase Edge Function), Stripe on the web version Wearable integrations: Apple HealthKit, Android Health Connect Requirements Hands-on experience with Lovable specifically, not just React/Next.js in a standard IDE. Solid Supabase experience — schema design, RLS policies, Edge Functions. At least one app you've personally taken through both the Apple App Store and Google Play review process, start to finish. Tell me which apps, and what platform-specific snags you hit. Experience implementing StoreKit / Google Play Billing for in-app purchases. Comfortable working from a detailed written spec and flagging gaps or conflicts rather than guessing. Clear, proactive communicator — I'm non-technical, so I need things explained in plain language, not just delivered. Nice to Have Experience with HealthKit or Health Connect integrations. Experience with GoHighLevel webhooks or similar CRM-to-app purchase sync. Familiarity with accessibility standards (WCAG AA) and shipping apps that pass them. Past work in fitness, health, or wellness apps. Engagement Type & Budget Structure: Fixed price for Phase 1 (App Store + Google Play submission through approval), then ongoing hourly for Phases 2 and 3. Budget: [add your target range for Phase 1, and your target hourly rate for ongoing work] Timeline: [add target launch date, or "ASAP once accounts are live"] Estimated ongoing commitment: [add rough expectation, e.g. "a few hours a week" or "as-needed, responsive within X days"] How to Apply Please include, so I can actually compare applicants instead of guessing: One or two apps you've personally submitted to both app stores — links if public, plus what went wrong (something always does) and how you handled it. Your experience level with Lovable specifically, and how many Lovable projects you've shipped. A one-paragraph plan for how you'd approach going from "working Lovable app" to "live on both stores" for an app like this. Your usual turnaround time for a bug fix or small feature request once we're in an ongoing relationship. I'll share the full build specification and a feature guide with serious applicants before we talk further.