Capacitor Alternative: When You Need a Framework – and When Your Website Just Needs to Become an App

Do you need a Capacitor alternative at all?

Maybe not. A Capacitor alternative makes sense when your goal is to publish an existing website or web app with native features and nobody on your team wants to maintain native projects. If you are developers building a hybrid app from one web codebase, Capacitor is one of the best tools available, and switching would cost more than it saves.

Capacitor calls itself "a cross-platform native runtime that makes it easy to build performant mobile applications that run natively on iOS, Android, and more using modern web tooling". The Ionic team maintains it – Ionic has been part of OutSystems since 2022 – and it has been MIT-licensed since version 1 in May 2019. You get real Xcode and Android Studio projects; npx cap sync copies your built web assets into them, and plugins expose native APIs to JavaScript.

That design assumes you ship your web app inside the binary and keep developing it as an app. If your situation is "we have a website and want it in the stores", read on.

Capacitor in 2026: releases, support windows and Ionic's commercial exit

The open-source project is active. What changed is the commercial layer around it:

• Capacitor 8 arrived on December 8, 2025, with minimums of iOS 15, Android 7 (API 24) and Xcode 26, Swift Package Manager as the default for new iOS projects and a SystemBars plugin for edge-to-edge layouts.
• Capacitor 7 stays in extended support until December 8, 2026.
• Capacitor 9 is "forecasted to launch at the end of November", says Ionic's August 2026 roadmap post: the Cordova compatibility layer becomes optional, XCFramework distribution ends and official Contacts, Calendar and Health & Fitness plugins arrive.
• Ionic's commercial products – Appflow, Identity Vault, Auth Connect, Secure Storage, Portals – stopped taking new customers on February 11, 2025. Existing Appflow users keep access until December 31, 2027, and Ionic says Capacitor "will remain free and open source".

In practice, expect a major upgrade about once a year. Android makes it concrete: Capacitor 8 targets API level 36, which Google Play has required for new apps and updates since August 31, 2026 (see our target API level guide). For newcomers, cloud builds and live updates come from third parties such as Capawesome Cloud, Capgo or VoltBuilder.

Not sure which tool fits your app? Ask an App Specialist – for free.

In a free consultation call we look at your website or web app and tell you honestly which route fits – WebViewGold, a framework or a native build – and what it takes to get through review. Prefer to hand it off? We set up signing and CI/CD and submit the app for you.

Free consultation call Book our service →

Where Capacitor is more than a website-to-app project needs

Picture a common request: a company website or a web app built with Bubble, WordPress or Lovable, live on its own domain and updated every week. The owner wants it in both stores with push, Face ID and a proper offline screen. With Capacitor, someone has to:

• choose between bundling a build in webDir – not an option when a hosted builder doesn't export your code – and loading the live site through server.url, which Capacitor's configuration reference describes as "intended for use with live-reload servers" and "not intended for use in production";
• wire the Push Notifications plugin to Firebase and APNs, with JavaScript for registration and taps;
• pick third-party plugins for biometrics and in-app purchases, which aren't official – for example RevenueCat's @revenuecat/purchases-capacitor or cordova-plugin-purchase;
• build an offline fallback, external-link handling and deep links;
• keep a Mac for iOS – "To build iOS apps, you will need macOS" – and follow every major upgrade.

None of this is hard for a mobile developer. It is a lot for a team whose product is the website. Our article on WebView apps rejected under Guideline 4.2 explains why a thin server.url shell also invites a "repackaged website" rejection.

Capacitor vs WebViewGold vs PWA vs a native rebuild

A PWA skips App Review but also App Store discovery. A rebuild in React Native, Expo or Flutter makes sense when the interface itself must feel native and you can maintain a second codebase next to your website.

Which tool fits which project?

Review risks: thin shells, live updates and remote switches

The toolkit rarely decides an App Review outcome – what the app does decides it. Three risks apply whichever route you take:

• Thin shells and Guideline 4.2. On the Ionic Forum in 2019, a developer shared Apple's rejection of an app that only showed web pages; Apple wrote that push notifications alone "do not provide a robust enough experience". Our Guideline 4.2 guide covers what does.
• Live updates and Guideline 2.5.2. Apps may not "download, install, or execute code which introduces or changes features or functionality of the app", and section 3.3.1(B) of Apple's Developer Program License Agreement only allows downloaded interpreted code that doesn't change the app's primary purpose. Capacitor's docs note that "Apple and Google explicitly allow web content updates to apps"; native code can't be updated over the air anyway. Keep OTA releases to fixes and content – see 2.5.2 for WebView apps.
• Remote switches and Guideline 5.6. Features turned on after approval look hidden to Apple. That applies equally to a WebViewGold app loading your live site: ship new features with a build and describe them in the review notes.

On Google Play, the Device and Network Abuse policy bans self-updating outside Play but exempts "JavaScript in a webview or browser". The spam policy still requires that you own the wrapped site or have permission – see our Google Play WebView spam guide.

When Capacitor is the better choice

• Web developers will maintain the app for years and want full control over native code.
• The app should work offline with bundled assets and local data, not just show a fallback screen.
• You need a custom native plugin, or one from Capacitor's ecosystem that no wrapper offers.
• You already run an Ionic or Capacitor app – upgrading beats any rewrite.
• You want web, iOS and Android from one repository and one pipeline.

If that describes your project, stay with Capacitor. It is free, MIT-licensed and actively developed.

When WebViewGold is the better choice

WebViewGold is our own team's website-to-app product, so we're biased – here are the facts to judge by. It isn't a framework but a finished app – Swift source in an Xcode project for iOS, plus a matching Android Studio project. You enter your URL, or a local HTML folder, in the configuration – Config.swift on iOS – and switch on native modules.

Its modules replace the plugin shopping list a Capacitor team would draw up. Notifications run through OneSignal, Firebase or Pushwoosh, biometrics through Face ID and Touch ID, scanning through QR, barcode and VisionKit document scanners. Add NFC tag reading, in-app purchases with StoreKit and Google Play Billing (Extended license), AdMob, App Tracking Transparency support, a native rating dialog, an offline fallback and universal links – plus widgets, an App Clip and Siri on iOS and Health Connect on Android.

You pay once, updates are free, and both projects belong to you; publishing happens in your own accounts. No Mac in the office? WebViewGold's Cloud Builder, sold separately, handles configuration, build and upload from a browser tab, and our team also offers to set the app up for you. The trade-off: no custom native screens in a JavaScript workflow – WebViewGold is for apps whose heart is the website.

Switching from Capacitor to WebViewGold without a new listing

1. Read the app's identity from capacitor.config. Its appId is your bundle ID on iOS and application ID on Android. Note the current version and build numbers.
2. Check who owns the accounts. Agency-built apps sometimes live in the agency's Apple or Google account. Move them to accounts you control with Apple's App Transfer or Google's app transfer before you switch.
3. Locate your Android keys. In a Capacitor project the keystore usually sits with your team. When Play App Signing is on, Google keeps the actual app signing key, so even a lost upload key can be replaced: the Play Console account owner asks Google for a reset.
4. Map plugins to modules. Push Notifications to the OneSignal, Firebase or Pushwoosh module, Barcode Scanner to the QR and barcode scanner, Share to the native share dialog, RevenueCat or cordova-plugin-purchase to StoreKit and Google Play Billing – keeping your product IDs.
5. Choose the content source: your production URL, or your existing web build as a local HTML folder.
6. Build, test, update. Keep the identifiers, raise version code and build number, test via TestFlight and an internal track, then publish as an update of the current listings – with refreshed privacy answers in both stores if your SDK list changed.

How appsubmitter.io helps – whichever tool you keep

If Appflow's wind-down is what made you look around, the missing piece may be the build pipeline rather than the framework. appsubmitter.io builds that pipeline – fastlane on GitHub Actions, GitLab CI, Bitrise, Codemagic or Xcode Cloud – and looks after certificates, provisioning profiles, Play App Signing and release builds, whether the app runs on Capacitor or WebViewGold. On the store side, our App Specialists write the listings, complete the privacy questionnaires of both stores, check the build against the guidelines with AI support and handle rejections and reviewer questions, all inside your own developer accounts. Code work isn't part of the package; we price it upfront if you need it.

Book both platforms or use a free consultation call to decide between Capacitor and WebViewGold first.

Checklist: choosing your website-to-app route

• You know whether you need an app built around a web codebase or your existing website as an app.
• If you stay on Capacitor, the upgrade to Capacitor 8 happens before Capacitor 7 support ends on December 8, 2026.
• Your Android build targets API level 36, as Google Play requires since August 31, 2026.
• No production build loads your live site through server.url.
• Live updates change web content only, within the purpose App Review approved.
• Appflow's jobs – cloud builds, live updates – have a new home if you used it.
• Bundle ID, application ID, keystore and developer accounts are under your control.

Frequently asked questions

Sources and further reading

• Capacitor Docs – Introduction
• Capacitor Docs – Support policy (versions and minimum requirements)
• Capacitor Docs – Configuration reference (server.url, appId, webDir)
• Ionic Blog – The future of Ionic's commercial products (February 2025)
• Ionic Blog – The Road to Capacitor 9 (August 28, 2026)
• Capacitor Docs – Deploying updates
• Apple – App Store Review Guidelines, 2.5.2 Software Requirements
• Google Play Policy Center – Device and Network Abuse

Store policies and third-party products change regularly – always check the current versions. This article is independent advice and not affiliated with or endorsed by Apple, Google or any other company or product mentioned; all trademarks belong to their owners. WebViewGold and appsubmitter.io are made by our team at jocapps GmbH.