What is Cordova used for?

Cordova packages a single HTML, CSS, and JavaScript codebase into a native app for Android and iOS. Native plugins bridge that code to device hardware such as the camera, GPS, and file system, and the project is still maintained: Cordova Android 15.0.0 shipped in March 2026, targeting Android 15 (SDK 36).

What does this mean in practice?

A team writes the app's UI and logic once in web code, and Cordova wraps it in a native shell: WKWebView on iOS, the system WebView on Android. The wrapped app installs from the App Store and Google Play like any other native app, which is the main practical difference from a progressive web app that runs inside a browser tab and can't be listed on Apple's App Store at all.

Where does Cordova fit well?

It suits content-driven or form-heavy apps, internal business tools, and early-stage products where a small team knows web development but not native Swift or Kotlin. Plugins such as cordova-plugin-camera and cordova-plugin-geolocation cover the most requested device features without writing platform-specific code, and many teams pair Cordova with a UI framework like Ionic rather than building screens from scratch.

What's the practical catch?

Cordova apps run through a WebView layer, so animation-heavy or graphics-intensive screens feel less smooth than fully native equivalents or apps built with newer engines. For new projects, Capacitor (also from the Ionic team) has largely taken over this same wrap-a-web-app model with more active plugin maintenance, so Cordova today is more often maintained on existing codebases than chosen fresh.

Updated: August 12, 2026