When you need a mobile app and a web app is not enough

    Build a mobile app when your users' main jobs happen on the phone, away from a desk, many times a day. This guide gives you a four-step check to decide whether your web app needs a mobile app, which kind, and how to build it.

    Phones carry 59% of web traffic worldwide (StatCounter, September 2026), while people spend less than 6% of their smartphone time in browsers and search engine apps (DataReportal, Digital 2025, from data.ai). Many of your users already open your web app on a phone. Whether they need a mobile app depends on what they do with your product, not on the technology.

    This guide is for people who already have a working web app built in Lovable, Bolt, Replit or a similar tool. It has four steps:

    1. List what your users do with the product (jobs to be done).
    2. Check which of those jobs need what only a mobile app does well.
    3. Decide what to build: web, mobile or both.
    4. Choose how to build it.

    At the end there is a checklist you can tick off.

    Step 1: Start with the jobs your users do

    Write down every job a user does with your product. A job is one thing they come to get done, such as "log today's workout" or "send an invoice". For each job, answer four questions:

    • What does the user want to get done?
    • Where are they when they do it: at a desk, on the street, at the gym, in a shop?
    • How often: once a month, once a week, several times a day?
    • Which device is in their hand at that moment?

    If you have analytics on the web app, check them: the share of visits from phones and the pages people open on a phone tell you which jobs already happen there.

    Example jobs and answers:

    JobWhereHow oftenDevice
    Tick off today's habitAnywhereSeveral times a dayPhone
    Log a workoutGym, outdoorsDailyPhone, watch
    Scan a receiptShop, caféSeveral times a weekPhone
    Find a place nearbyStreetWeeklyPhone
    Review a monthly reportOfficeMonthlyLaptop
    Edit a long documentDeskWeeklyLaptop

    Example jobs. Replace them with the jobs of your own users.

    If most of your important jobs land in the Phone column, your product needs a mobile app. If they land in the Laptop column, your web app is enough.

    Step 2: Check what a mobile app gives those jobs

    Take each phone job from Step 1 and match it to the capabilities below. These are the things a web app cannot do well, even when it is installed on the home screen as a progressive web app (PWA). Our PWA vs native app guide covers the technical side.

    CapabilityWhat it gives the userJobs it fitsLimit on the web
    Push notificationsReminders, daily check-ins, alerts when something changesHabits, tracking, socialOn iPhone, web push works only after the user adds the site to the home screen
    Camera and photosScanning, taking pictures, uploading straight from the phoneReceipts, documents, social postsLive scanning is slow and unreliable in the browser
    LocationMaps, nearby places, tracking while movingDelivery, running, travel, local searchLocation stops when the browser tab closes
    Offline useWorking without internet and syncing laterField work, travel, gyms with bad signalNeeds extra setup; Safari can delete stored data after 7 days without a visit
    Health and sensorsSteps, workouts, Apple Watch dataFitness, sleep, wellbeingNo access to Apple Health or the watch
    Home screen and widgetsOne tap to open, quick info without opening the appHabits, to-dos, daily statsNo widgets

    Web limits as of November 2026, for Safari on iPhone and Chrome on Android.

    Most products that need mobile are B2C: habit, tracking and social apps, or on-the-go tools. People open them many times a day on the phone, not on a laptop.

    A job that matches none of these capabilities can stay on the web, even if people do it on a phone. A mobile-friendly web page is enough to read an article or fill in a form once.

    Step 3: Decide: web, mobile or both

    Sometimes a product needs both for a good experience. Sometimes one is enough. Use the jobs from Step 1 and the capabilities from Step 2:

    BuildChoose it whenExample
    Web onlyJobs happen at a desk, a few times a week, with long text or big tablesAdmin dashboard, reporting tool
    Mobile onlyJobs happen on the go, many times a day, and need at least one capability from Step 2Habit tracker, running app
    BothUsers do quick jobs on the phone and long jobs on a laptopMobile app to log expenses, web app to review and export them

    Pick the row that matches most of your important jobs.

    If you pick Both, keep one backend (for example Supabase or Firebase) so the web app and the mobile app share the same users and data. Users then sign in with the same account on both, and what they log on the phone shows up on the laptop.

    Step 4: Choose how to build it

    There are three ways to turn a web app into a mobile app.

    ApproachHow it worksWhat you getWhat you miss
    Website in an app shell (Capacitor, Despia)Wraps your existing site in an iOS and Android appFast, a store listing, basic pushWeb UI on the phone; Apple can reject apps that are only a website (App Store guideline 4.2)
    Cross-platform rebuild (React Native, Flutter)One new codebase that runs on both platformsCloser-to-native UI, most device featuresA JavaScript or Dart layer between your app and the phone; widgets and watch apps need extra native code
    Native rebuild (Swift for iOS, Kotlin for Android)Two apps built with Apple's and Google's own toolsEvery capability from Step 2, the platform's own look and feelNormally two codebases to keep in sync

    App Store Review Guideline 4.2 asks for "features, content, and UI that elevate it beyond a repackaged website".

    If your jobs need two or more capabilities from Step 2, a native rebuild gives you all of them without workarounds. If you need only a store listing and basic push, an app shell is the fastest start; see What is Capacitor and Native vs cross-platform for the details of each route.

    Building native with Modaal

    Modaal rebuilds a web app as native iOS and Android apps:

    1. Paste your web app's URL. A GitHub repository or a ZIP is optional.
    2. Your screens appear on the Screen Map, where you adjust the design per device before any code is written.
    3. Your own AI agent (Claude Code, Codex, Cursor and ten more) builds the apps in Swift and Kotlin from one shared core, so both apps behave the same.
    4. You build on your own Mac with Xcode and ship through TestFlight and the App Store, and through Google Play for Android.

    You own the code and can export it at any time. Keep your existing backend so the web app and the mobile apps share the same users and data.

    Imported web app screens on the Modaal Screen Map
    Screens from an imported web app on the Screen Map. Our screenshot.

    Checklist

    • List every job users do with your product: what, where, how often, which device.
    • Mark the jobs that happen on the phone.
    • Match each phone job to a capability: push, camera, location, offline, health, widgets.
    • Pick web only, mobile only, or both.
    • Pick how to build: app shell, cross-platform, or native.
    • Keep one backend for web and mobile.

    Frequently asked questions

    Keep reading

    Your jobs land in the Phone column? Build the mobile app.

    Paste your web app's URL into Modaal. Your own AI agent rebuilds it as native iOS and Android apps on the backend you already have.