Lovable to iOS: Prepare Your Product for iPhone and the App Store

Want your Lovable product on an iPhone? There are two different destinations: a website saved to the home screen and an iOS app distributed through Apple's tools. The first is a web installation; the second requires an iOS project, Apple signing and a distribution process. This guide focuses on the second path.

Make the experience feel right on iPhone

Open your published product in Safari on an actual iPhone. Check whether the keyboard covers important buttons, whether screens respect the safe areas around the camera and home indicator, and whether long forms scroll properly. Test file selection, camera access and external links if your product uses them.

Do not assume a successful desktop login means mobile login will work. A packaged app may use a separate browser context, and some identity providers restrict embedded sign-in. Verify the authentication method, callback addresses and session behaviour in the installed app.

Prepare the iOS project

Your Lovable website needs a supported mobile project before it can be compiled into an IPA. A framework such as Capacitor can help create the native shell, but the generated configuration and platform files still need checking. Exporting a ZIP of an unchanged web project is not the same as preparing iOS build source.

If your product relies on server rendering or server functions, keep those features on the hosted backend. Select a compatible hosted configuration or create a separate client-only frontend. Simply pointing a native build at server output will not make that code run on an iPhone.

Collect the Apple signing files

• An Apple Developer account appropriate for your distribution plans.
• A registered bundle identifier that matches the iOS project.
• An Apple Distribution certificate exported as a .p12 file with its private key.
• The certificate password and a matching App Store .mobileprovision profile.
• Matching capabilities and entitlements for any services the app uses.

These files establish who can distribute the app. Keep them private, avoid committing them to a public repository and monitor their expiry dates. A profile for the wrong bundle identifier or certificate can prevent signing even when compilation succeeds.

Create your IPA in PWAtoApp

Sign in to the build dashboard, start a new build and select iOS. Upload the prepared source ZIP, then supply the Apple Distribution certificate, certificate password and App Store provisioning profile. An available Mac worker is required to perform the iOS build.

Enable Apple push notifications only when your project and Apple account are configured for them. The optional Firebase configuration file is relevant if the app actually uses Firebase. Checking a box alone does not implement notification permissions, device registration or message delivery.

Use TestFlight before requesting review

For App Store distribution, use Apple's supported upload tools to send the signed build to App Store Connect. Allow for processing and any required compliance questions, then test through TestFlight. An App Store-signed IPA is not a file that every iPhone owner can install directly.

PWAtoApp's €49.99 one-time package includes unlimited iOS and Android builds with release signing. Apple membership, your signing files and store approval remain separate requirements.