You have a web app. Users keep asking for "the app". Rewriting everything in Swift and Kotlin is out of the question. So you wrap it.
There are two realistic ways to do that in 2026: Capacitor, or a no-code wrapper service. I work at Glideep, which is one of the no-code options, so I'll try to keep this honest and say where Capacitor is the better pick.
Option 1: Capacitor
Capacitor wraps your web app in a native iOS and Android project and gives you plugins for native APIs.
npm install @capacitor/core @capacitor/cli npx cap init npm run build npm install @capacitor/ios @capacitor/android npx cap add ios npx cap add android npx cap sync Then you open the projects in Xcode and Android Studio, set icons, signing and permissions, and build.
Good fit when:
- You need deep native features (HealthKit, Bluetooth, background tasks, custom native screens).
- You want full control and are happy to maintain native projects.
- You're fine handling certificates, provisioning profiles and build machines (or a cloud CI such as Codemagic if you don't have a Mac).
Costs: free, but every OS update, plugin upgrade and store requirement change lands on you.
Option 2: A no-code wrapper
You paste your web app's URL, configure the app (icon, splash, navigation, push), and the service builds signed apps for you. Median, WebViewGold and Glideep work this way.
Good fit when:
- Your app's value lives in the web app, and you mainly need push notifications, in-app purchases, biometric login and a native shell.
- You don't want to own a Mac or maintain native code.
- You want web changes to appear in the app without a store release.
Trade-off: you're limited to the native features the service supports.
Side by side
| Capacitor | No-code wrapper | |
|---|---|---|
| Setup | Hours to days | Minutes |
| Native features | Anything, via plugins or your own code | What the service supports |
| Mac needed | For local iOS builds (or use cloud CI) | No |
| Maintenance | You | The service |
| Cost | Free + your time | Subscription or one-time fee |
The part both options share: App Review
Whichever route you take, Apple's guideline 4.2 (Minimum Functionality) is the main risk. A website in a frame gets rejected. What helps:
- Native navigation (a tab bar) instead of the site's menu.
- Push notifications with a real purpose.
- An offline screen instead of a browser error page.
- Hiding web-only UI (cookie banners, "get our app" prompts) inside the app.
- A demo account in the review notes if there's a login.
And on Android: new personal Google Play accounts (created after 13 Nov 2023) must run a closed test with at least 12 testers for 14 days before production. Plan for it.
My take
If native features are your product, use Capacitor. If your web app is the product and you want it in the stores this week, a no-code wrapper is usually the faster and cheaper path over the first year.
If you want the no-code route, this is how Glideep does it. Happy to answer questions in the comments, including where Glideep isn't the right fit.



