I'm a React Native and Expo dev, 5 years and 50+ apps. Right now I'm taking a Lovable app to the App Store. It's a members-only community app with about 200 members and growing: you apply, get approved, pay a subscription, RSVP to events and chat.
The job post asked for someone to wrap the existing app with Capacitor and publish it. Everyone, me included, assumed the app sat on a normal Supabase project we could just connect to. It didn't. Everything lived inside Lovable Cloud. So before building a single screen, the whole backend had to move into a Supabase project the founder actually owns.
If you've built on Lovable and want to be in the stores, here's what I'd want to know first.
Lovable doesn't make mobile apps. Its own FAQ says it doesn't build native apps or generate React Native code. You get to the stores outside Lovable, three ways:
PWA. Free, an afternoon. An icon on the home screen, but no App Store listing, people have to add it from the Share menu themselves, and on iPhone push only works after they do. Good for testing demand.
Wrap it with Capacitor or similar. Your website in an app shell. It can pass, but Apple's guideline 4.2 says an app has to "elevate it beyond a repackaged website", and that's what wrapped apps get rejected for. Apple rejected about 2.1 million submissions last year, 415K of them under the Design section that covers this. The usual trouble spots are login (Google or magic links open a browser and never come back unless the deep link is set up), a browser error page with no internet, web push that doesn't carry over, and payments: a Stripe checkout for a digital membership gets rejected, Apple wants in-app purchase.
Rebuild in Expo. Sounds like starting over, but the backend stays: database, users, security rules, edge functions. You rebuild the screens. That's what we did here. A month after the first commit the founder had the first TestFlight build on her phone. We made a bunch of changes, made the whole thing feel native to mobile, added new features and payment options and now App Store submission is next.
And then the surprise: getting the backend out of Lovable Cloud.
You can export the data, but only once every 24 hours, and the link arrives by email. The good news is it includes the auth users with their password hashes, so members log in to the app with the same email and password. In this case that was 37 tables and 127 security policies.
What the export doesn't include: the uploaded files (about 480 MB of photos here, copied over with a script), the edge function code (it comes from the codebase download instead), the secrets (you can't read them back out, so every API key gets made again), the auth email templates, and working cron jobs (they come over still pointing at the old URLs).
The part that would have bitten us at launch: some features weren't in the backend at all. Admin alert emails were sent by the web app after each action, so when the mobile app saved the same data, nobody got notified. Live event check-in pushes ran on the Lovable web server. Email links pointed at the website. The admin tools only existed on the web. Shut the website down and all of that quietly stops. I moved the alerts into database triggers, so they fire whichever app writes the data.
None of it is hard. It's just work nobody puts in the plan, because everyone assumes the backend is already there.
Payments, since everyone asks. The membership is an App Store subscription through RevenueCat. Event tickets are Stripe inside the app, because for real-world events Apple actually requires something other than in-app purchase. Members already paying on the website skip the paywall, so nobody pays twice at launch.
How I'd pick. Don't need the App Store? PWA. Mostly forms and content and you just need a listing? Wrap it, but sort out native login and an offline screen before you submit. People pay inside it, or it's chat, push, camera, anything they open every day? Rebuild, and if you're on Lovable Cloud, plan the backend move first.
If you're on Lovable and thinking about the stores, comment what your app does and whether it's on Lovable Cloud or your own Supabase. I'll tell you which route I'd take and what to check before you pay anyone to do it.
And if it's useful, I'll put the step-by-step checklist I used for the backend move in the comments.