Skip to content
Back To School Sale from $619, until 31st October 2026 Book now
appsubmitter.io
Alternatives & comparisons iOS + Android

Cordova Alternative: Should You Move Your Apache Cordova App – and Where To?

Apache Cordova is not dead: cordova-ios 8, Cordova CLI 13 and cordova-android 15 all shipped between November 2025 and July 2026. Teams look for a Cordova alternative because push, in-app purchases, biometrics and scanning depend on third-party plugins of varying quality, and iOS builds still need a Mac. The right route depends on the app: a real hybrid codebase moves well to Capacitor, an app that is mostly your website fits WebViewGold, and a UI-heavy product may deserve a native rebuild.

By the appsubmitter.io App Specialist Team, updated , 10 min read

Recommended solution: WebViewGold – native iOS and Android apps from your web app, made by our team.

Key takeaways

  • Apache Cordova is actively maintained by the Apache Software Foundation – cordova-android 15 targets SDK 36, which Google Play requires since August 31, 2026.
  • The pain points are the plugin ecosystem, the Mac requirement for iOS and the missing first-party cloud build since PhoneGap Build ended in 2020.
  • For real hybrid codebases, Capacitor is the natural next step: it has an official Cordova migration guide, and many Cordova plugins keep working.
  • If your Cordova app mostly shows your website, you may not need a framework at all – WebViewGold, made by our team, replaces the plugin stack with built-in modules.
  • Keep the identifiers from config.xml and your signing keys, and the new build updates your existing store listings.

Our recommended solution

Looking for a Cordova alternative? Meet WebViewGold

WebViewGold turns your website or web app into native iOS and Android projects for a one-time price – with push notifications, a native offline screen, deep links, a QR scanner, in-app purchases and more. You own the projects and publish in your own developer accounts. Built by our own team.

Do you need a Cordova alternative in 2026?

Not necessarily. Apache Cordova still gets regular releases, so an app that builds, passes review and depends on maintained plugins can stay where it is. A Cordova alternative makes sense when plugin upkeep eats your time, when you want a more modern toolchain – or when the app is really just your website and doesn't need a framework at all.

Cordova calls itself "an open-source mobile development framework" for building cross-platform apps with HTML, CSS and JavaScript. It is an Apache Software Foundation project under the Apache License 2.0. Its roots are PhoneGap, created by Nitobi in 2009; Adobe bought Nitobi in 2011 and contributed the code to the ASF. When Adobe announced the end of PhoneGap in August 2020 – PhoneGap Build shut down on October 1, 2020 – it stated that "Apache Cordova will continue to exist", and it has.

Is Cordova dead? The 2025–2026 release record says no

DateReleaseHighlights
March 26, 2025cordova-android 14.0.0Major Android platform release
November 23, 2025cordova-ios 8.0.0Minimum iOS 13 and Xcode 15, plugins as Swift packages, built-in status bar handling
November 25, 2025Cordova CLI 13.0.0New major version of the command-line tool
March 6, 2026cordova-android 15.0.0Target SDK 36, integrated status bar, opt-in edge-to-edge
July 7, 2026cordova-ios 8.1.1Patch release
July 22, 2026cordova-android 15.1.0Minor release

The Android line matters most right now. Since August 31, 2026, Google Play only accepts new apps and updates that target Android 16 (API level 36), and cordova-android 15 targets SDK 36 – so staying means upgrading the platform. Our target API level guide covers the deadline. Some platforms are gone: cordova-osx was deprecated in 2022 in favor of cordova-electron or Mac Catalyst, and cordova-windows is listed as deprecated.

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.

Why teams still move away from Cordova

  • Plugins. Core plugins cover camera, device info, dialogs, files, geolocation, InAppBrowser, media, network information, status bar, vibration and a few more. Push notifications, in-app purchases, biometrics and barcode scanning come from third-party plugins such as cordova-plugin-purchase, and their maintenance varies widely.
  • Builds. "Apple® tools used for building iOS applications can only operate within the macOS environment," notes Cordova's iOS guide. Since PhoneGap Build, there is no first-party cloud build; third parties such as VoltBuilder and Capawesome Cloud fill the gap.
  • Store changes hit through dependencies. When Apple stopped accepting new apps using UIWebView in April 2020 and updates in December 2020, Cordova apps needed cordova-ios 5.1.1 with the WKWebViewOnly setting, and plugins that still referenced UIWebView had to be updated too. Today's versions of that problem are deprecated or non-public APIs in old plugins (see our Guideline 2.5.1 guide) and SDKs without privacy manifests.

Cordova vs Capacitor vs WebViewGold vs a native rebuild

RouteStay on CordovaCapacitorWebViewGoldNative rebuild
TypeOpen-source framework (Apache-2.0), ASFOpen-source runtime (MIT), Ionic teamReady-made native app templateSwift and Kotlin, React Native or Flutter
PlatformsAndroid, iOS, Electron desktop, browseriOS, Android, webiOS, AndroidiOS, Android
Pricing modelFreeFreeOne-time purchase, free updatesFree tools; the rewrite is the cost
Code ownershipYoursYoursYou own the Xcode and Android Studio projectsYours
Native featuresCore plugins; push, IAP, biometrics and scanning from third partiesAbout 40 official plugins; many Cordova plugins workPush, IAP, Face ID, scanners, NFC, offline screen built inEverything the platform offers
Who publishesYou, in your accountsYou, in your accountsYou, or appsubmitter.io, in your accountsYou, in your accounts
Mac for iOSYes, or third-party cloud buildsYes, or third-party cloud CIYes for Xcode; no with the Cloud BuilderFor local builds; cloud CI possible
If you stop payingNothing to payNothing to payNo subscription to stopNothing to pay
Effort from a Cordova appPlatform and plugin upgradesModerate: migration guide plus plugin auditLow if the app is mostly your websiteHigh: the UI is rebuilt

Which route fits your Cordova app? Four questions

  1. Where does the interface come from? If your www folder mostly forwards users to your live website, you maintain a framework to run a browser. A wrapper like WebViewGold does that job with far less code.
  2. How much logic lives in the app? A bundled single-page app with offline data, local storage and plugin calls is a real hybrid codebase – Capacitor is its natural home.
  3. Which plugins can't you live without? List them and check each against Capacitor's plugins, its Cordova compatibility notes and WebViewGold's modules. Whatever is left needs custom native code.
  4. Must the interface itself be native? Demanding gestures, animation or performance point to Swift and Kotlin, React Native or Flutter – the most expensive route, worth it only if users would notice.

Capacitor's guide "Migrating a Web App Using Cordova to Capacitor" recommends doing the work on a separate branch. Plugins that are incompatible or cause build issues are skipped automatically, and some "may not match functionality entirely", so audit them early. Our Capacitor comparison covers 2026 details, including Capacitor 9 making the Cordova compatibility layer optional.

Review risks that move with your app

A new framework doesn't change App Review's questions. Check these before the first submission of the migrated app:

  • Guideline 4.2. Cordova apps that only show web pages face the same "repackaged website" judgment as any wrapper; native features in the main journey decide it – see WebView apps and 4.2.
  • Guideline 2.5.2. Hybrid apps often update their JavaScript over the air. Apple bans downloaded code that "introduces or changes features or functionality", and the Developer Program License Agreement permits downloaded interpreted code only if it doesn't change what the app is for. Google Play is more relaxed: its rule against apps updating themselves outside Play doesn't cover "JavaScript in a webview or browser". Details in 2.5.2 for WebView apps.
  • Guideline 4.3. Agencies with many white-label Cordova apps from one codebase should consolidate before migrating, not after.
  • Google Play spam rules. Own the site you wrap or have permission, and avoid near-identical apps – our WebView spam guide explains both.

Our recommended alternative

WebViewGold: native iOS and Android apps from your website

Instead of building native features from scratch, start from WebViewGold. You get ready-made Xcode and Android Studio projects for your website, with native modules you switch on in the configuration:

  • Push notificationsOneSignal or Firebase, for real, personal events
  • Native offline screenNo browser error pages when the connection drops
  • Native splash screenApp-like start instead of a loading web page
  • Deep linksLinks open the right screen inside the app
  • QR & barcode scannerDevice features the website alone can't offer
  • In-app purchasesNative purchase flows where the store requires them

No tool guarantees an approval: Apple still judges what your app offers. Use the native features in your main user journey – our App Specialists review your WebViewGold app before it goes to the App Store.

When staying on Cordova is the right call

  • The app works, your plugins are maintained and moving to cordova-android 15 and cordova-ios 8 is manageable.
  • You ship a desktop version through cordova-electron and want a single toolchain.
  • Your team knows Cordova well and the roadmap is stable.
  • A migration would only move the same plugin dependencies somewhere else.

In those cases, invest in an automated build and upgrade routine rather than a rewrite.

When WebViewGold replaces Cordova best

WebViewGold is built by our own team, so read this as an informed but interested view. It fits Cordova apps that are mostly a website: instead of a framework plus a dozen plugins, you start from two finished native projects – Swift code in Xcode and an Android Studio project. You point them at your URL in the configuration (Config.swift on iOS) or bundle your web files locally once their Cordova plugin calls are replaced.

Its modules replace the plugins Cordova leaves to third parties: push via OneSignal, Firebase or Pushwoosh; StoreKit and Google Play Billing purchases (Extended license); Face ID, Touch ID and Android biometrics; QR, barcode and document scanning; NFC; AdMob; deep links and universal links; a native offline screen; a file downloader and AirPrint. You pay once and receive updates free of charge. Teams without a Mac can use the separately purchased Cloud Builder, which configures, builds and uploads from the browser, or let our team handle the setup.

Migrating from Cordova without losing your store listing

  1. Read your identifiers from config.xml. The id of the <widget> element is your app identifier unless android-packageName or ios-CFBundleIdentifier override it. Note version, android-versionCode and ios-CFBundleVersion as well.
  2. Confirm who owns the accounts. If an agency built your Cordova app, check whether the listings sit in its account. Apple's App Transfer moves an app with its bundle ID, ratings and reviews; Google Play has its own transfer process.
  3. Find your Android keys. Locate the keystore your Cordova release builds used. If Play App Signing is active, Google stores the app signing key, and a missing upload key is fixable: the Play Console account owner can ask Google to reset it. Apps outside Play App Signing need the original key for every update.
  4. Map every plugin to a WebViewGold module, a Capacitor plugin or custom code.
  5. Build with the same identifiers and a version code and build number above the last Cordova release.
  6. Test where reviewers look – push, purchases, offline behavior, deep links – through TestFlight and an internal testing track.
  7. Submit it as an update to the existing listings; if push, analytics or purchase SDKs changed, revise your App Privacy answers and Data safety form.

How appsubmitter.io helps Cordova teams

If your Cordova releases have been built on one developer's Mac since PhoneGap Build closed, that Mac is a single point of failure. appsubmitter.io replaces it with a reproducible setup and takes the store work off your plate:

  • Pipeline: fastlane on GitHub Actions, GitLab CI, Bitrise, Codemagic or Xcode Cloud, including certificates, provisioning profiles and Android release builds (AAB).
  • Keys: upload keys and Play App Signing set up so a lost laptop doesn't lock you out of updates.
  • Store work: listings, screenshot guidance, Apple's privacy details and Google's Data safety form.
  • Review: an AI-powered pre-submission check, the submission and every reply to the reviewers – rejections included – from your own developer accounts.

That works for the Cordova app you keep, a Capacitor migration or a new WebViewGold build; code changes are discussed and quoted before any work starts. Book the two-store package or plan the migration in a free consultation call.

Checklist: choosing your website-to-app route

  • You know your cordova-android and cordova-ios versions and have planned the move to 15 and 8 if you stay.
  • Your Android release targets API level 36.
  • Every plugin is listed with its maintenance status and a replacement.
  • The widget id, platform overrides and version codes from config.xml are documented.
  • The release keystore and its passwords are backed up, and Play App Signing status is known.
  • The apps live in Apple and Google accounts you control.
  • Over-the-air JavaScript updates stay within the reviewed purpose of the app.

Frequently asked questions

Is Apache Cordova dead in 2026?
No. The Apache Software Foundation released cordova-ios 8.0.0 in November 2025, Cordova CLI 13 the same month, cordova-android 15.0.0 in March 2026 and further updates for both platforms in July 2026. What ended was Adobe's involvement: PhoneGap was discontinued, and PhoneGap Build shut down on October 1, 2020.
What is the best Cordova alternative?
It depends on the app. A bundled hybrid app with lots of JavaScript logic moves best to Capacitor. An app that mostly shows your website is a better fit for WebViewGold, made by our team, which replaces third-party plugins with built-in modules. A UI-heavy product may justify React Native, Flutter or fully native code.
Can I reuse my Cordova plugins in Capacitor?
Many of them, with caveats: Capacitor's documentation lists known incompatible plugins, and its migration guide skips incompatible ones automatically. Capacitor 9, forecast for the end of November 2026, makes the Cordova compatibility layer optional, so check how your plugins will be handled before you plan the move.
Do I need a Mac to build a Cordova iOS app?
Yes. Cordova's iOS guide says Apple's build tools only run on macOS. Third-party cloud builders such as VoltBuilder or Capawesome Cloud can build for you, and a CI/CD pipeline with fastlane can run on hosted macOS machines. appsubmitter.io sets up such pipelines, so nobody on your team needs to own a Mac.
What replaced PhoneGap Build?
Nothing first-party. Adobe ended PhoneGap Build on October 1, 2020, and Apache Cordova has no hosted build service of its own. Teams moved to third-party cloud builders, to their own Macs or to CI/CD pipelines such as fastlane with GitHub Actions, Bitrise or Codemagic. Ionic's Appflow no longer accepts new customers.
Will my app keep its reviews if I move from Cordova to WebViewGold?
Yes, as long as the WebViewGold build is published as an update: the same bundle ID and package name from your config.xml, the same developer accounts and a higher version number. Your rating history and existing users carry over. On Android, sign with your existing upload key or have the account owner request a reset.
Does Google Play still accept Cordova apps?
Yes. Google Play judges the app, not the framework. The practical hurdle is the target API level: Google Play has demanded API level 36 for new apps and updates since August 31, 2026, and cordova-android 15 meets it. Beyond that, the usual policies apply, including Webviews and Affiliate Spam and the functionality rules.

Recommended solution

Switch with confidence: WebViewGold + appsubmitter.io

  1. 1 Build with WebViewGold Turn your website into native iOS and Android projects.
  2. 2 Add native value Push, offline screen, deep links or scanning in your main flow.
  3. 3 We submit it Our App Specialists submit and talk to the review team.

WebViewGold is made by our team (jocapps GmbH). It is a tool, not a guarantee – approval decisions are made by Apple and Google.

Sources and further reading

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.

Talk to a real App Specialist

Switch tools without starting over

Bring your website or web app – we help you choose the right setup, prepare the store listings and submit your app in your own developer accounts.

Back To School Sale prices until 31st October 2026. Prices in USD, excl. VAT.