Comparison · updated November 2026

Capacitor vs Cordova vs html2app Who keeps your native app up to date?

Capacitor and Apache Cordova wrap your web app in native Android and iOS projects that you keep up to date. html2app wraps it in a Flutter shell that html2app keeps up to date for you. This page compares how each one is built, how plugins work, what upkeep lands on you, and what each one costs.

  • Capacitor: MIT open source
  • Cordova: Apache 2.0
  • html2app: proprietary, Flutter
At a glance

Three tools, three ways to own the native layer

Each tool turns a web app into an Android or iOS binary. The differences start with licensing and who maintains the native project.

Capacitor by Ionic

Open-source runtime you maintain

Wraps your web app in native Android and iOS projects. Those projects are regular files in your repo, and you edit them.

  • MIT license, open source from the start
  • Native code in Java/Kotlin (Android) and Swift/Objective-C (iOS)
  • Official Ionic plugins plus community plugins
Cordova by the Apache Software Foundation

The original hybrid framework

The long-running standard for hybrid apps. Its core is well known, but many of its plugins are older and some are deprecated.

  • Apache 2.0 license
  • Native projects generated into platforms/ by the cordova CLI
  • Several components deprecated, including the status bar and WKWebView engine plugins
html2app cloud build service

Upload the web build, get the store binary

A Flutter shell hosts your web app, and html2app maintains that shell. You never open an Android or iOS project.

  • Proprietary service, not open source
  • Flutter shell, so you write no Java, Kotlin, Swift or Dart
  • You keep your own signing key and app ID
Architecture

How each one is built

All three run your HTML, CSS and JavaScript inside a WebView, and use a bridge to reach the phone. The only real difference is who owns the native host underneath.

Capacitor You maintain the host
Layer 1 Your web app HTML, CSS, JS or TS, any framework
Layer 2 Capacitor bridge JavaScript calls native plugins
Layer 3 Native projects android/ in Java/Kotlin, ios/ in Swift/Obj-C
Output APK, AAB or iOS build

npx cap sync copies your built web assets into the native projects. Those projects are real files you can open in Android Studio and Xcode.

Cordova You maintain the host
Layer 1 Your web app index.html, CSS and JS, any framework
Layer 2 cordova.js bridge exec calls reach plugin code
Layer 3 Platform projects platforms/android in Java, platforms/ios in Obj-C/Swift
Output APK, AAB or iOS build

The CLI rewrites platform code from your web assets on each build, so edits inside platforms/ are overwritten. Keeping them means switching to the platform-centered workflow, and that switch cannot be undone.

html2app html2app maintains the host
Layer 1 Your web app Any HTML5 project, including Phaser and Three.js
Layer 2 js-bridge Typed calls to native plugins
Layer 3 Flutter shell Hosts your app in a WebView, written in Dart
Output Signed APK and AAB

You upload the web build and receive the binary. You never open an Android or iOS project.

The build path, step by step

  1. Capacitor Build web app → npx cap sync → open Android Studio or Xcode → sign and upload
  2. Cordova Build web app → cordova platform add → cordova build → sign and upload
  3. html2app Build web app → zip the output → cloud build → download the signed binary
Plugin ecosystem

How the plugin ecosystem works

Vibration, storage, ads and device info all need native code. Who writes that code, and who keeps it working after each platform update, decides how much work reaches you.

Capacitor

Official plus community packages

Each plugin is an npm package with native code inside. Ionic maintains the official @capacitor/* set. Community plugins cover the rest, and each one targets a Capacitor major version.

Version-matched, community-maintained
Cordova

A large but aging catalogue

Plugins are also npm packages, and Apache maintains a core set. Apache has deprecated several components and archived some plugins, so older plugins need a check before you depend on them.

Core set plus aging third-party plugins
html2app

Plugins ship inside the shell

Install the @yandeu/js-bridge package once, enable a plugin in the html2app dashboard, then call it from your JavaScript. There is no native sync step. The current set covers Vibration, AdMob, Storage and Device Info, and more plugins are on the way.

One maintainer, one update path

The same vibration call, two ways

Capacitor install, sync, call
# 1. add the plugin, then copy it into the native projects
npm install @capacitor/haptics
npx cap sync

// 2. call it from your game or app code
import { Haptics } from '@capacitor/haptics';

await Haptics.vibrate({ duration: 200 });
html2app install, enable, call
# 1. install the bridge once, then enable the plugin in the dashboard
npm install @yandeu/js-bridge

// 2. call it from your game or app code
import { Vibration } from '@yandeu/js-bridge/lib/plugins/vibration.js';

Vibration.vibrate(200, 255);

Both examples vibrate for 200 ms. The html2app call is the same one used on the Phaser.js page.

Momentum

How many developers use each tool

npm downloads let us compare Capacitor and Cordova over the same 30 days. Flutter's usage is measured by developer surveys instead, which count a different thing.

Capacitor

29.7 million npm downloads

The @capacitor/core package in the 30 days from 17 October to 15 November 2026. Downloads count installs and CI runs, so they are not a count of live apps.

Cordova

335,000 npm downloads

The cordova CLI package in the same 30 days. This counts the CLI only, not the plugins.

Flutter

Developer surveys

Flutter packages are published on pub.dev, and its share of developers comes from published surveys. Survey results vary by source and year, so they sit apart from the npm downloads.

Listed on Flutter's official showcase, checked on 15 November 2026. Not a complete list.

Native upkeep

The upkeep you can hand off

Every year, iOS and Android raise their toolchain and store requirements. With Capacitor and Cordova, those changes land in your repo. With html2app, they land in the shell that html2app runs.

  1. Late Nov 2026

    Capacitor 9 is expected

    Ionic plans to ship Capacitor 9 at the end of November. Plugin authors must run its migration tooling, and the iOS code moves from Objective-C to Swift.

  2. Dec 2, 2026

    CocoaPods trunk goes read-only

    No new podspecs or version updates will publish to CocoaPods trunk. Plugins that pull in CocoaPods SDKs, such as Firebase, need to move to Swift Package Manager. Capacitor 8 already uses SPM by default.

  3. Dec 8, 2026

    Capacitor 7 leaves extended support

    Extended support for Capacitor 7 ends. Moving to a newer major means changing native projects and plugins yourself.

  4. Every release

    html2app updates the shell

    The Flutter shell and build tooling update on html2app's side. You upload the same web build and download a new binary.

Who does the upkeep
Upkeep task Capacitor and Cordova html2app
Upgrade to a new framework major version You html2app
Raise minimum Node, Xcode, Android Studio or Gradle versions You html2app
Move plugins off CocoaPods to Swift Package Manager You html2app
Fix plugin breakage after an upgrade You html2app
Keep your signing key and app ID You You
Side by side

The full comparison

Scroll sideways on small screens. Sources for the Capacitor and Cordova facts are listed at the bottom of this page.

Capacitor, Apache Cordova and html2app compared
Topic Capacitor Cordova html2app
License MIT, open source Apache 2.0, open source Proprietary*
Maintained by Ionic Apache Software Foundation html2app
Native code you write Java/Kotlin and Swift/Obj-C Java and Obj-C/Swift None. The shell is Flutter
Native projects in your repo Yes: android/ and ios/ Yes: platforms/ No
Who upgrades the native toolchain You You html2app
Plugin model npm packages with native code npm packages with native code Built-in typed JavaScript bridge
Plugin maintenance Official and community plugins, each tied to a Capacitor major Apache core set, with several components deprecated Maintained by html2app
Plugin setup npm install then npx cap sync cordova plugin add npm install @yandeu/js-bridge, enable in the dashboard, then import
Where you build Android Studio, Xcode or your CI Cordova CLI with the platform SDKs, or your CI Cloud build. Nothing to install
Outputs APK, AAB, iOS build APK, AAB, iOS build Signed APK and AAB. iOS marked coming soon
Signing keys and app ID Yours Yours Yours, brought to html2app
Price Free Free Free tier. Paid plans from $5/month or $36/year
Best fit Teams that need open source and full control of native code Existing Cordova apps whose plugins still work for you Shipping without owning native upkeep

* html2app is proprietary today. Its author, Yannick Deubel (@yandeu), has a long history of publishing his projects as open source, and the html2app app shell may be open-sourced in the future. For now, it is proprietary.

Decision guide

Which one should you pick?

Capacitor

Pick it when open source is required

  • Your licensing rules need an open-source runtime
  • You want to read and change the native code yourself
  • Your team already works in Android Studio and Xcode
Cordova

Pick it to keep an existing app

  • You already ship a Cordova app
  • Every plugin you depend on still works with your target platforms
  • You want to stay close to the Apache project
html2app

Pick it to ship without native upkeep

  • You want a signed store binary without Android Studio or Xcode
  • You want html2app to handle shell and toolchain updates
  • A proprietary build service is acceptable for your project
FAQ

Questions people ask before choosing

Is html2app open source?
No. html2app is a proprietary build service. Capacitor is MIT licensed and Apache Cordova is Apache 2.0 licensed.
Do I need to write Java, Kotlin or Swift with html2app?
No. The html2app shell is built with Flutter. You upload your web build and receive a signed APK or AAB. The plugins cover common device features. If you need a native feature that is not in the plugin list, ask in the html2app discussions.
Why can community Capacitor plugins break after an upgrade?
Capacitor plugins target a specific Capacitor major version. After a major upgrade, a plugin can fail until its author publishes a version for the new major. Capacitor 9 also requires plugin authors to run migration tooling.
Can I move from html2app to Capacitor later?
Yes. Your app is standard HTML, CSS and JavaScript, and you keep your own signing key and app ID. Code that calls html2app plugins would need to be rewritten against the Capacitor plugin API.
Do I need Android Studio with Capacitor?
Android Studio is the usual way to open, run and sign a Capacitor Android project. You can also build the Gradle project in CI, without a local IDE.
What does html2app cost?
There is a free tier. Paid plans start at $5 per month or $36 per year. See the pricing section on the homepage for every plan.

Sources

Capacitor, Cordova and download facts checked on November 15, 2026. Version numbers and dates change, so confirm them on the linked pages before you decide.

Ship your web app without owning the native layer

Upload your web build, get a signed APK or AAB, and keep your own signing key and app ID.