# Can Lovable Make Mobile Apps? — Decision Guide

The short answer is **no — but easily converted**. Lovable builds web applications, not native mobile apps. The good news is that every project it generates is already a responsive web app that works on phones. You have three levels of "mobile app" you can choose from:

1. **Mobile-friendly website** — works in any browser, no extra setup.
2. **Home-screen app** — users add it to their home screen; looks and feels like an app.
3. **App Store app** — published to the App Store or Google Play via a wrapper tool.

---

## Quick Decision: Which One Do You Need?

| If you need... | Choose | Publishing effort |
|---|---|---|
| Share a link and have it work on phones | Mobile website | None |
| Home-screen icon, full-screen feel, offline-ish | PWA | Add manifest + icons |
| Push notifications, camera, GPS, App Store badge | Native app | Capacitor + Xcode/Android Studio |

**Rule of thumb:** Start with a PWA. Go native only when you need a phone feature the browser cannot provide.

---

## Option 1: PWA (Progressive Web App)

A PWA is just a website with extra metadata that lets the browser offer "Add to Home Screen." It is the fastest way to get an app-like experience.

### What you need

1. A `manifest.json` file with app name, short name, icons, theme color, and start URL.
2. An `apple-touch-icon` for iOS home-screen icons.
3. A responsive layout that already works well on mobile (Lovable does this by default).

### Pros

- No app store approval.
- Same Lovable project, no extra framework.
- Free to host and share via URL.
- Works on iPhone and Android.

### Trade-offs

- iOS limits push notifications for PWAs.
- No direct access to the camera, contacts, or some sensors.
- Offline mode only works if you specifically add a service worker.

---

## Option 2: Native App with Capacitor

Capacitor wraps your web app into a native iOS/Android shell. Lovable's React output drops into Capacitor with minimal changes.

### What you need

1. Export or sync your Lovable build to a local project.
2. Install Capacitor (`npm install @capacitor/core @capacitor/cli`).
3. Add iOS and/or Android platforms.
4. Build and open the project in Xcode (Mac) or Android Studio.
5. Submit to the App Store or Google Play.

### Pros

- Full phone access: camera, push notifications, GPS, sensors, biometrics.
- Published in the App Store / Google Play.
- More professional feel for users who expect a store download.

### Trade-offs

- Requires developer tooling (Xcode for iOS, Android Studio for Android).
- App store review process and ongoing compliance.
- Publishing is harder to reverse if you change your mind.

---

## Recommended Workflow

1. **Build in Lovable first.** Make it mobile-responsive. Test on your actual phone.
2. **Add a PWA manifest.** Let users install it from the browser.
3. **Run it as a PWA for a month.** If you hit a hard limit (like needing reliable push notifications on iOS), then consider Capacitor.
4. **Only go native when the business value justifies the extra work.**

---

## Common Questions

**Can Lovable export a mobile app?**
Not directly. Lovable exports a web app. You can use it as-is, turn it into a PWA, or wrap it with Capacitor for native stores.

**Does a PWA work on iPhone?**
Yes, but with limitations. You can install it to the home screen, but iOS restricts background sync and push notifications.

**Do I need to write native code?**
For a PWA, no. For a native app, you will need to run Capacitor commands and use Xcode/Android Studio to build and publish.

**Can I add offline support?**
Yes, but only if you set it up explicitly. A basic PWA works online. Offline mode requires a service worker, which is an advanced step.

**Should I use Lovable's PWA skill or do it manually?**
Use the PWA skill if available in your workspace. It handles the manifest and icons automatically. Otherwise, add the manifest and icons manually.

---

## Next Step

Open your Lovable project, preview it on your phone, and decide whether a PWA is enough. For most ideas, it is.