APP Dev — Turn Our Web App into iOS & Android Apps (Lovable + Supabase), While I Keep Editing Live

About the project I have a working web app (a nutrition / wellness app) and I'm looking for a long-term technical partner to take it to mobile and keep improving it with me over time. Current stack: Frontend: React 19 / TanStack Start Backend: Supabase (Auth, Postgres, Row-Level-Security, server functions) Built & maintained via Lovable (an AI low-/no-code editor) Already in place: integrations with external food databases (Open Food Facts, USDA) and an AI-powered photo/text meal scan. The goal — and the one non-negotiable constraint I want the app published as real iOS and Android apps (Apple App Store + Google Play). But I must not lose my current workflow — this is the hard requirement: I need to keep making changes in Lovable that go live directly (content, UI, logic), without depending on someone for every small change and without waiting days for an app-store review each time. I stay in control: make changes, turn things on/off, ship instantly. In practice this means wrapping the existing web app in a native shell (e.g. Capacitor) and connecting an over-the-air (OTA) live-update pipeline, so that web changes I publish from Lovable land automatically in the installed app. No React Native rewrite. That would make Lovable editing impossible and is therefore off the table. If you can't guarantee the "edit in Lovable → live in the app" flow, this isn't the right project for you. I understand that pure web/JS changes can ship live, while genuine native changes (new permissions, new plugins, SDK updates) still require a store review. Setting up and documenting exactly that boundary is part of the job. Scope of work I want all of the below handled. Because I'd like to move fast, I expect it delivered in milestones — ship first, then keep improving. Milestone 1 — Get it live, safely (priority) Convert the existing web app into native iOS/Android apps (Capacitor or equivalent): app icons, splash screen, permissions. Set up the OTA / live-update mechanism so my Lovable web changes go live without a new store review. Must be usable by me and documented. Wire up the native features the app needs — above all camera barcode scanning for food; ideally push notifications. Security fix (important): access control is currently enforced only on the client. Content must be gated at the database layer (Supabase RLS) based on active access, and the access check must fail closed, not open, on errors. Store setup & first release on Apple App Store and Google Play (signing, store listings, submission). I provide the Apple Developer and Play Console accounts. Milestone 2 — Data & API wiring Make sure the integrations to the external food data sources (Open Food Facts, USDA FoodData Central) are solid and correctly wired. Hook the Open Food Facts import into the meal scan, so scanned/entered foods pull real nutrition values and the local database fills itself automatically — instead of relying on AI estimates alone. Move the runtime AI off the Lovable gateway onto my own provider API key. The photo/text meal scan currently runs through Lovable's AI gateway (consuming my Lovable credits). Rewire it so it calls my own provider (Google / Anthropic / OpenAI) with my API key stored as a secret, so end-user AI usage is billed directly to me and decoupled from my Lovable build credits. Keep the model easily swappable. Wire the "ingredient → temperament" logic so it reads the database first, then falls back to the heuristic. Milestone 3 — Correctness & data quality Calculation engine: fix two known correctness bugs (missing normalization on incomplete data; double time-decay). The existing automated tests must stay green. Data basis: progressively populate the food temperament values (a curated core plus clearly labeled derived values), using the provenance columns that already exist. Ongoing Code hygiene and future features as we go (e.g. centralizing auth logic, explicit DB columns instead of select("*"), keeping secrets out of the repo, plus new functionality over time). Hard requirements (non-negotiable) My Lovable workflow stays intact, and my changes go live. The Supabase migration history is never rewritten (new migrations only — the codebase has rules for this in an AGENTS.md). I keep full control of the project: all accounts, repos, and keys stay in my name. Required skills Capacitor (or equivalent) + native iOS/Android builds, signing, and store submission — demonstrable. Supabase: RLS/policies, Postgres migrations, server/edge functions. Solid React (TanStack Start / React 19 a plus). REST / API integrations (Open Food Facts, USDA). Reliable communication and availability for ongoing work. Nice to have Experience with OTA services (e.g. Capacitor Live Updates / Appflow or similar). Experience with health / nutrition apps. Familiarity with Lovable or other generated codebases and their quirks. Please include in your application Your architecture in 3–5 sentences: how do you guarantee "I edit in Lovable → it goes live in the app"? Which tools, what's the flow, and where's the line (what ships live vs. what needs a store review)? Links to 2 published apps (iOS and/or Android) you've built. A rough milestone plan for how you'd sequence Milestones 1–3. Confirmation that you will not propose a React Native rewrite and that you'll respect the Supabase migration history. How we'll work I provide repo access, the Supabase project, store accounts, and API keys. Since this is an ongoing collaboration, I value clear communication and a short handover doc covering how I (a) keep working in Lovable and ship live, and (b) trigger new store builds when needed.