Capacitor and Cordova are frameworks that wrap web code in a native project you build and maintain with the Android SDK, and they give JavaScript access to native plugins. HTML to App is a no-code builder that produces the same kind of WebView app in the cloud, with splash, tabs and push built in but no plugin system. Use Capacitor if you need native SDKs or iOS; use HTML to App if your HTML already does everything and you want an APK in minutes.
At a glance
| Capacitor | Cordova | HTML to App | |
|---|---|---|---|
| Setup | Node, CLI, Android Studio | Node, CLI, Android SDK, Gradle | Install one app |
| Native project | Yours, committed to git | Generated, regenerated | Managed for you |
| Native plugins | Large, modern | Large, ageing | None (built-in features only) |
| iOS | Yes (needs a Mac) | Yes (needs a Mac) | Android only |
| Splash / tabs / push | Plugins + config | Plugins + config | Toggles in the builder |
| Yearly upkeep | SDK + plugin upgrades | SDK + plugin upgrades | Rebuild |
| Time to first APK | An afternoon | An afternoon | Minutes |
| Cost | Free (open source) + your time | Free (open source) + your time | Free APK · $5/mo Pro |
The deciding question
Does your app need to call native code you cannot get from the web platform? In-app purchases through Google Play Billing, an ads SDK, Bluetooth, background location, widgets, Health Connect — if yes, you need a plugin system: Capacitor. If no — your HTML, game or tool already works in mobile Chrome — a framework adds a toolchain to maintain and gives you nothing your app uses.
Capacitor in brief
Ionic's modern successor to Cordova. You add Capacitor to your web project, run npx cap add android, and get an Android Studio project you own. Plugins are npm packages with TypeScript APIs. Excellent for teams with a web codebase who need native features and both stores. The cost is a native toolchain and yearly upgrades as Android's target API rises.
Cordova in brief
The original web-to-native framework (Apache Cordova). Still works and has the largest legacy plugin library, but many plugins are unmaintained and new projects generally start on Capacitor.
HTML to App in brief
Upload HTML, a ZIP or a URL; a cloud build produces a signed APK (free) or AAB (Pro). App-level features — splash, onboarding, bottom tabs, push, loaders, offline screen, permissions — are switches, not plugins. No toolchain, no native project to maintain. All features.
Questions people ask
Is Capacitor better than a no-code HTML to APK builder?
It is more capable — it has native plugins and iOS support — and more work. For a self-contained HTML app, a builder produces the same WebView result with no toolchain.
Can I start with HTML to App and move to Capacitor later?
Yes. Your web code is unchanged in both. Keep the same package name and signing key, and a Capacitor build can update the same Play listing.
Is Cordova dead?
Not dead, but most new projects choose Capacitor, and many Cordova plugins are no longer maintained.