What is a WebView app? When a wrapped website works, and when to build native

    A WebView app is your website running inside an iPhone or Android app shell. It is the fastest way to get a web product into the App Store and Google Play, and for some products it is the right one. This guide explains what a WebView app is, what it is good for, where it falls short, what AI changed, and which route fits a non-technical builder in 2026.

    The short answer. A WebView app (also called a wrapper app or a wrapped website) is a small native app whose main screen is a browser view that loads your website. It works well for content, internal tools and quick store tests. It falls short when your users open the app many times a day and need what phones do best: native screens, push notifications, widgets, the camera, health data or offline use.

    Until recently a wrapper was the only affordable route for a small team, because a native app meant two codebases in Swift and Kotlin. AI coding agents changed that: they now write the Swift and Kotlin, and your existing web app works as the specification. For a product that lives on the phone, a native rebuild with AI is now the better default.

    What a WebView app is

    A WebView is a browser engine that an app can place on its own screen. Apple describes its version, WKWebView, as "an object that displays interactive web content". Android's WebView "lets you display web pages as a part of your activity layout."

    A WebView app is a native shell built around that view:

    • The shell is a small iOS or Android app with an icon, a splash screen and a store listing.
    • The content is your website, loaded from its URL or bundled as web files inside the app.
    • The bridge lets the web page call a few phone features through plugins, such as push notifications, the camera or sharing.

    Tools that build these shells include Capacitor, Median (formerly GoNative), Despia, Natively and PWABuilder. They differ in how much you configure yourself and which plugins they include; our Capacitor vs Despia and Median alternatives guides compare them.

    What a wrapper is good for

    A wrapper is the right tool when the app is a door to your website, not a product of its own:

    SituationWhy a wrapper fits
    Content you already publish on the web (news, docs, a catalogue)The website already does the job; the app gives readers an icon and a store listing
    An internal tool for your teamUsage is occasional, the audience is known, and design polish matters less
    A quick test of store demandYou get a listing in days and learn whether people search for and install the app
    A companion to a web product people use at a deskThe phone is for checking something once in a while, not daily work
    One web team and no budget for a second codebaseEvery change ships to the web and the app together

    A wrapper works best when the website already gives users everything they need.

    There is a second advantage: when the shell loads your live website, a change to the site appears in the app without a new store build.

    Where a wrapper falls short

    The limits come from the same design choice: the screens are web pages, not native screens.

    AreaIn a WebView appIn a native app
    Look and feelWeb controls styled to look like an app; scrolling, the keyboard and back gestures behave like a browserSwiftUI on iPhone and Jetpack Compose on Android, with each platform's own controls and gestures
    Phone featuresPush, camera and sharing through plugins; widgets, Live Activities, Apple Watch and Health data need native code added to the shellEvery platform feature is available directly
    SpeedLong lists and animations run in the browser engineLists and animations run on the platform's own rendering
    App Store reviewGuideline 4.2 asks for "features, content, and UI that elevate it beyond a repackaged website"Reviewed as a regular app
    Google PlayNo apps that "provide a webview of a website without permission from the website owner or administrator"Reviewed as a regular app
    UpkeepYour website, the shell and its plugins, kept compatible after each iOS and Android updateOne app per platform, or one shared core with Modaal

    Apple App Review Guidelines (updated 16 October 2026) and Google Play Spam policy, read 16 November 2026.

    Apple also lists "web clippings" among the things an app should not primarily be (guideline 4.2.2), and guideline 4.2.6 says apps "created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content." A wrapper that adds push notifications, offline use and phone features has a better chance in review than a plain website in a shell.

    How Modaal solves what a wrapper can't

    Modaal is a Mac app where your own AI agent rebuilds your web app as two native apps, one for iPhone and one for Android, from one project. The table takes each limit from the section above and shows how it works in Modaal:

    AreaIn Modaal
    Look and feelThe iPhone app is built in SwiftUI and the Android app in Jetpack Compose, so each one uses its platform's own controls, gestures and keyboard behaviour.
    Phone featuresWidgets, Live Activities, Watch apps, Shortcuts and Wallet work from the first build, along with push notifications, the camera and offline use.
    SpeedLists and animations run on the platform's own rendering, not in a browser engine.
    App Store and Google PlayYour app is reviewed as a regular native app and published under your own Apple and Google accounts.
    UpkeepBoth apps share one core. Duet, Modaal's open-source framework, writes each feature's logic once and checks on every build that both apps behave the same. Memory Lane added its Android app with zero logic files changed.

    Modaal features as of November 2026.

    Other benefits for a team that already has a web app:

    • Your web app is the starting point. Paste its URL, and your screens appear on the Screen Map, where you adjust the design for iPhone, iPad, iPhone Duo and Android before any code is written.
    • A plan before code. Modaal writes a migration plan and a spec for each feature, and you approve them before your agent builds anything.
    • Your own AI agent, no credits. Claude Code, Codex, Cursor and 10 more work with Modaal, on the plan you already pay for.
    • Your backend and website stay. The native apps connect to your existing Supabase or Firebase project, so users keep one account, and your web app keeps running.
    • You own the code. Every app is a real Xcode and Android Studio project in Git on your disk, which you can open without Modaal at any time.

    Why wrappers became the default

    For years the choice for a small team looked like this:

    • Native: two apps, one in Swift for iPhone and one in Kotlin for Android, written by two specialists or an agency, plus the web app you already have.
    • Cross-platform (React Native, Flutter): one new codebase, still written by a mobile developer.
    • Wrapper: your existing website in a shell, set up in days by the person who built the website.

    A small team with a working web app picked the wrapper because it was the only route it could afford to build and maintain.

    What changed with AI

    Three things changed in 2025 and 2026:

    1. AI agents write native code. Coding agents such as Claude Code, Codex and Cursor write Swift and Kotlin, and Xcode and Android Studio now include agents of their own. The person who describes the app no longer has to write the code.

    2. Your web app is the specification. The screens, flows, data model and backend already exist. A rebuild starts from a working product, so it is shorter than building the first version, and the design decisions you made on the web carry over, adjusted to mobile.

    3. The backend stays. If your web app uses Supabase or Firebase, the native apps connect to the same project. Users keep one account, and the web app keeps running.

    AI also made web apps easy to build: Lovable, Bolt, Base44 and Replit produce working web apps from a prompt, and many of their builders now want those apps in the stores. That makes the wrapper-or-native decision more common, and the App Store rules above apply to every one of those submissions.

    What is best for non-technical builders now

    Pick the route by what your users do with the product. Our Do you need a mobile app? guide has the full four-step check.

    Your situationBest routeWhy
    Users read content or use the product a few times a monthMobile-friendly website or PWANo store review and no second product to maintain
    You need a store listing this week to test demandWrapper, with a plan to go nativeFast to set up; replace it once people install and use it
    Users open the app daily and need push, camera, widgets or offline useNative rebuild with AIEvery phone feature works, and the app passes review as a regular app
    Users do quick jobs on the phone and long jobs at a deskKeep the web app, add native apps on the same backendOne account and one database for web and mobile

    The rows match the decision table in our "Do you need a mobile app?" guide.

    How to rebuild a web app natively without writing code

    In Modaal the native route starts from what you already have:

    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 for each device before any code is written.
    3. Modaal writes a migration plan with you, and your own AI agent (Claude Code, Codex, Cursor and 10 more) builds the iPhone app in SwiftUI and the Android app in Jetpack Compose from one shared core.
    4. The apps connect to your existing backend, your web app keeps running, and you publish under your own Apple and Google accounts.

    You own the Swift and Kotlin code and can open it in Xcode or Android Studio at any time. See how website import works.

    Frequently asked questions

    Turn your web app into a native 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, and your website keeps running.

    Keep reading