Straight answers before the stores.

Not by itself, as of October 31, 2026. Lovable's own docs say publishing always deploys to a web URL and there is no built-in flow that packages and submits a project to the App Store. They point to an installable web app (PWA) or a native shell built outside Lovable, and Lovable does not generate React Native projects. That outside step is the work we do.

Capacitor, for most Lovable apps (October 2026). Lovable's publish docs say it has no built-in native publishing and does not generate React Native projects, so both routes happen outside Lovable, from the code in your GitHub repo. Capacitor wraps that same code, so you keep building in Lovable; React Native (Expo) means rewriting the screens. Capacitor fits forms, lists, dashboards, bookings, anything that still changes every week. A rebuild in React Native (Expo) or Flutter is worth it when people live in the app: long feeds, chat, maps, heavy gestures or video. You can also start with Capacitor and rebuild the busiest screens later, because your Supabase backend works with both.

It depends on who will keep changing the app. As of October 2026 you have three kinds of option: wrapper services that keep your app inside their own builder, doing Capacitor yourself (free, but signing, plugins and store review are on you), or a developer service that hands you the code. If your web app was built with Lovable, that last one is us: a Capacitor app from the same code Lovable edits, native features added for Apple guideline 4.2, store submission done, for a one-time $300, $600 or $1,000 by app size, and the project stays in your GitHub and your store accounts. If people live in the app all day (feeds, chat, maps), we rebuild it in React Native or Flutter at the same prices.

A one-time fixed price by app size, the same for a Capacitor app or a native rebuild: $300 for up to 5 screens, $600 for up to 15 screens (custom transitions, API integration, push notifications) and $1,000 for 25+ screens (complex state management, store submission support, analytics). The stores charge you directly on top: Apple Developer Program $99 a year, Google Play $25 once.

Yes, on the Capacitor path. The store app is built from the same code Lovable edits, so you keep prompting as usual and the next build carries your changes to iOS and Android. Each new version still goes through store review, like any app update. On the native rebuild path the mobile screens are separate code, so changes made in Lovable stay on the web.

No, keep it. Send us the repo and tell us where it is stuck: signing, a plugin, a build error or a rejection. We fix what is there, add the native features review asks for and ship it. Same packages, same prices. If the only thing left is an App Store rejection, that is a $350 flat fix.

It can, if the app is only the website in a frame. Apple's guideline 4.2 (minimum functionality) asks for features, content and UI that go beyond a repackaged website. That is why our Capacitor apps get native parts too, such as push notifications, an offline screen, native sharing and proper sign-in, before the first submission.

A developer account ($25 once) with verified identity. A new personal account also has to run a closed test with at least 12 testers who stay opted in for 14 days in a row before Google allows a production release, so start that test early. You also fill in the data safety form.