Mobile Apps for AI Coders
You built a website. Now you want it on phones. Here are your three options, from easiest to most powerful.
In this chapter
- The three ways to get your website on phones (PWA, Capacitor, React Native)
- Which approach fits your project and skill level
- What users actually experience with each approach
- How to publish to the App Store and what it costs
Do I Actually Need a Mobile App?
Most people think they need a mobile app when a responsive website would do the job. Ask yourself:
A responsive website is enough when:
- Users visit occasionally (not daily)
- You don't need push notifications
- You don't need camera, GPS, or sensors
- You don't need to be in the App Store
- Your content is mostly text, images, and forms
You need a mobile app when:
- Users open it daily (habit-forming product)
- You need push notifications to re-engage users
- You need camera, GPS, contacts, or Bluetooth
- You want to be discoverable in the App Store
- You need offline functionality
Your Three Paths
What you get:
- Home screen icon on phones
- Full-screen mode (no browser bar)
- Offline support with cached pages
- Fast loading with service workers
- Works on both iOS and Android
What you don't get:
- No App Store listing
- Limited push notifications on iOS
- No access to some native APIs
- Users must visit your site first to install
“Convert my Next.js website into a Progressive Web App (PWA). Add a web app manifest with my app name, icons (192x192 and 512x512), theme color, and display: standalone. Set up a service worker for offline caching of static assets. Add a meta tag for mobile web app capable. Make sure the app can be installed on home screens on both iOS and Android.”
What you get:
- Real App Store / Play Store listing
- Push notifications on both platforms
- Access to camera, GPS, file system
- Keep your existing web codebase
- One codebase for web + iOS + Android
What to know:
- Need Xcode (Mac only) for iOS builds
- App Store review process (can take days)
- Performance may not match fully native apps
- Some complex native UIs are harder to build
“Add Capacitor to my existing Next.js project so I can publish it as a native iOS and Android app. Install @capacitor/core and @capacitor/cli, initialize Capacitor with my app name, configure the webDir to point to my build output, and add the iOS and Android platforms. Set up the Capacitor config file. Then show me how to build and open the project in Xcode (iOS) and Android Studio.”
What you get:
- Best possible performance and feel
- Full access to all native APIs
- Native UI components (not web views)
- App Store and Play Store listing
- Large community and ecosystem
What to know:
- Separate codebase from your website
- Steeper learning curve
- Need Xcode and Android Studio for local builds (Expo's cloud builds skip this)
- More complex to deploy and maintain
- AI tools are less mature for native apps
“Create a new React Native app using Expo. Set up the project with TypeScript, Expo Router for tab and stack navigation, and a clean folder structure. Create a home screen with a welcome message, a settings screen with a profile form, and tab navigation between them. Use NativeWind (Tailwind for React Native) for styling. Make sure it runs on both iOS and Android.”
What Each Approach Looks Like
Here's what the user actually experiences with each path, from their perspective, not yours:
- User visits your website in their browser
- Browser prompts 'Add to Home Screen'
- App icon appears on their phone's home screen
- Tapping it opens your site in full-screen mode (no browser bar)
- Works offline if you've cached pages with a service worker
- User finds your app in the App Store or Play Store
- They download and install it like any other app
- Opening it shows a native-looking app, but it's your website running inside a native shell
- Push notifications, camera access, and other native features work through plugins
- Your website is bundled inside the app, so changes need a new app store release (or a live-update service)
- User finds your app in the App Store or Play Store
- They download and install it like any other app
- Opening it shows a fully native app with native navigation, animations, and UI components
- Everything feels fast and smooth: buttons, scrolling, and gestures are all native
- It's a separate codebase from your website
Which Path Should I Pick?
| PWA | Capacitor | React Native | |
|---|---|---|---|
| Difficulty | Easy | Medium | Hard |
| Time to build | Hours | Days | Weeks |
| App Store listing | No | Yes | Yes |
| Push notifications | Limited | Yes | Yes |
| Camera / GPS | Limited | Yes | Yes |
| Offline support | Yes | Yes | Yes |
| Reuse web code | 100% | 90%+ | Some (React) |
| Native feel | Good | Good | Best |
| Cost | Free | $99/yr (Apple) | $99/yr (Apple) |
App Store Basics
- $99/year Apple Developer Program fee
- Need a Mac with Xcode, unless you use Expo's cloud builds
- Most apps are reviewed within 1-2 days
- Apple takes 15-30% of in-app purchases (US apps may link to web checkout instead)
- Strict guidelines: apps can be rejected
- $25 one-time Google Developer fee
- Can build from any OS (Mac, Windows, Linux)
- New personal accounts must first run a closed test with 12 testers for 14 days
- Review process takes hours to a few days
- Google takes 15-30% of in-app purchases
- Less strict than Apple, faster approval
Real World Example: Turn Your Portfolio Into a PWA
You have a portfolio site built with Next.js and deployed on Vercel. You want it to feel like an app on your phone, with a home screen icon, full-screen mode, and offline support. You add a web app manifest, configure a service worker to cache your pages, and add the right meta tags. Now when you visit your site on your phone, the browser offers 'Add to Home Screen' and your portfolio lives right next to Instagram and Twitter.
“Convert my Next.js portfolio site into a Progressive Web App. Add a manifest.json with the app name 'My Portfolio', theme color #5046E5, background color #FFFFFF, display standalone, and icons at 192x192 and 512x512. Set up a service worker that caches all static assets and pages for offline use. Add the required meta tags for iOS (apple-mobile-web-app-capable, apple-mobile-web-app-status-bar-style) and Android. Make sure the 'Add to Home Screen' prompt works on both platforms.”
Frequently Asked Questions
Can I turn my Next.js website into a mobile app?
Yes! The easiest way is to make it a PWA (Progressive Web App): users can install it on their home screen and it works like an app. For a real App Store listing, use Capacitor to wrap your existing site in a native shell.
Do I need a Mac to build iOS apps?
Not always. With Expo (React Native), cloud builds compile and submit your iOS app from any computer, Windows included. You only need a Mac with Xcode if you build the iOS app on your own computer, for example with Capacitor. PWAs need no Mac at all, and Android-only apps work on any computer.
How much does it cost to publish an app?
Apple charges $99/year for their Developer Program. Google charges a one-time $25 fee. The apps themselves are free to build. You only pay for the store listings.
Should I build a website or an app first?
Always build the website first. It's faster, cheaper, and reaches more people. A responsive website works on phones already. Only build a separate mobile app when you have a proven product that needs native features.